Your debug log shows that your Pi-Hole is working. This section of the debug log tests DNS resolution several different ways, and all were successful:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ads233.hpg.ig.com.br is 0.0.0.0 via localhost (127.0.0.1)
[✓] ads233.hpg.ig.com.br is 0.0.0.0 via Pi-hole (192.168.1.10)
[✓] doubleclick.com is 216.58.208.142 via a remote, public DNS server (8.8.8.8)
The problem is likely in your router setup. A good first step to test the Pi-Hole from a client is to assign the Pi-Hole IP as DNS on that specific client (not going through the router DNS assignment to get to the Pi-Hole)
Here is a good guide to get your clients onto Pi-Hole: