Pihole not working at all

Expected Behaviour:

[Pihole should be blocking ads. Netgear AX3000 with an Arris SB8200 modem, pihole running on RaspPi Zero W 2. I have enabled DHCP on the Pi (disabled on router), and set my DNS as the Pi’s static IP.]

Actual Behaviour:

[Ads are not blocked whatsoever.]

Debug Token:

[Debug token is here: https://tricorder.pi-hole.net/Eg8BXKbw]

Your debug log shows that domains are being blocked by Pi-hole (data from the past 24 hours or when you installed Pi-hole, whichever is a shorter time interval):

   [2023-08-20 08:57:41.674 1044M]  -> Total DNS queries: 22528
   [2023-08-20 08:57:41.674 1044M]  -> Cached DNS queries: 1901
   [2023-08-20 08:57:41.674 1044M]  -> Forwarded DNS queries: 18868
   [2023-08-20 08:57:41.674 1044M]  -> Blocked DNS queries: 1568
   [2023-08-20 08:57:41.674 1044M]  -> Unknown DNS queries: 0
   [2023-08-20 08:57:41.674 1044M]  -> Unique domains: 2102
   [2023-08-20 08:57:41.674 1044M]  -> Unique clients: 3
   [2023-08-20 08:57:41.674 1044M]  -> Known forward destinations: 2

From a client that you believe should be connected to the Pi-Hole for DNS (and where you are seeing ads), from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

nslookup flurry.com

nslookup flurry.com 192.168.1.19

OK, heard.

Output of [nslookup pi.hole] =

Server:		192.168.1.1
Address:	192.168.1.1#53

Name:	pi.hole
Address: 192.168.1.19

Output of [nslookup flurry.com] =

Server:		192.168.1.1
Address:	192.168.1.1#53

Name:	flurry.com
Address: 0.0.0.0

Output of [nslookup 192.168.1.19] =

Server:		192.168.1.1
Address:	192.168.1.1#53

19.1.168.192.in-addr.arpa	name = pi.hole.

This means it's working. It looked up flurry.com and pointed it to the black hole that is 0.0.0.0.

I'd imagine that the devices seeing adverts either haven't renewed their DHCP lease yet (i.e. they're still looking at your original DNS which doesn't block adverts) or they have a static DNS set (same result). You can give them a kick in the right direction by rebooting them and confirming in their network settings that they're using 192.168.1.19 (your Pihole) as their DNS.

Also it's possible that your Pihole isn't set to (i.e. the advert domain isn't listed in the block list), or can't (e.g. YouTube adverts), block the specific advert you're seeing.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.