Lots of queries but very little adblocking

Help
6

From that Windows PC, try asking it to resolve a known blocked domain and see if it is using Pi-hole.

nslookup flurry.com

Next try asking it to explicitly use Pi-hole (just in case it didn't).

nslookup flurry.com 192.168.0.2

Now see if you can reach external DNS without anything on the computer interfering, for example some anti-virus suites like AVG can do this. You should get the text response "ATLAS".

nslookup -class=chaos -type=txt version.bind 198.41.0.4

Your debug log shows things are working, your router is the DHCP server and is telling clients on your network to only use your Pi-hole, so the Windows computer above, and your other devices, should all be using Pi-hole, and you should see their queries in your Pi-hole Query Log.

Note that you don't appear to be able to reach your Pi-hole upstream servers using IPv6. I'd recommend going into your Pi-hole's Settings > DNS where you have the four boxes ticked for Quad9, and unticking the last two Quad9 IPv6 checkboxes, leaving just the first two IPv4 ones ticked, and Saving those changes.

Now, you've indicated the numbers are low and very little adblocking. Some other things that can circumvent Pi-hole, even when the DHCP is telling them to use Pi-hole...

  • I mentioned AVG above. That has happened before.
  • Browsers can ignore the OS DNS settings and send it over a 'tunnel' to their own DNS servers. So things work as normal when testing but the browser still doesn't seem to use Pi-hole. Look for settings like Secure DNS or DNS-over-HTTPS or DoH in your browser's settings.
  • Apple devices can do similar with a feature called iCloud Private Relay, which is part of a paid subscription I believe.
  • Your debug log indicates you have a One Plus phone. If that is not using Pi-hole, it may be that it is just silently also using Google's public DNS. This appears to be something that OPPO, and possibly One Plus, are doing. A friend of mine had this and we couldn't find a way around it on the device. It would have needed firewall rules at the router to "redirect" the unwanted Google requests back to the internal Pi-hole.
3 Likes