Pi-Hole blocking is enabled but not working

Help
1

Expected Behaviour:

When running 'pihole status' it shows as enabled, and while navigating on a browser, the ads are blocked as per the default config.
Using Ubuntu 22.04 on an Asus laptop

Actual Behaviour:

'pihole status' confirms blocking is enabled but when using a browser the ads persist, when trying Bucking Horn's suggestion on Effective ways to test PiHole? - #2 by Bucking_Horn it does returns the site's address:

$ nslookup pi.hole
Server:		192.168.0.1
Address:	192.168.0.1#53

** server can't find pi.hole: NXDOMAIN

$ nslookup flurry.com 192.168.0.1
Server:		192.168.0.1
Address:	192.168.0.1#53

Non-authoritative answer:
Name:	flurry.com
Address: 74.6.136.150
Name:	flurry.com
Address: 212.82.100.150
Name:	flurry.com
Address: 98.136.103.23

Debug Token:

https://tricorder.pi-hole.net/aROhGcc5/

2

The DNS server in use is the router, not Pi-hole. Pi-hole is at IP 192.168.0.113

Your DHCP server (the router) is passing its own IP for DNS, not the IP of Pi-hole:

** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 548 bytes from wlp1s0:192.168.0.1
     Offered IP address: 192.168.0.113
     Server IP address: N/A
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.0.1
      lease-time: 7117 ( 1h 58m 37s )
      netmask: 255.255.255.0
      router: 192.168.0.1
      dns-server: 192.168.0.1
      --- end of options ---
    
   DHCP packets received on interface wlp1s0: 1
   DHCP packets received on interface lo: 0

What is the output of the following command from the same client on which you ran the previous nslookup commands?

nslookup flurry.com 192.168.0.113

3

It returns:

$ nslookup flurry.com 192.168.0.113
Server:		192.168.0.113
Address:	192.168.0.113#53

Name:	flurry.com
Address: 0.0.0.0
Name:	flurry.com
Address: ::

So that's causing it, is this the change I must do in the DHCP portion of the installation or is it something different?

4

The clients are net being assigned Pi-hole as their DHCP server.

Change the settings on your router. Assigne Pi-hole as the only DNS server in your DHCP settings. If there are two available spots to enter DNS servers, put Pi-hole IP in both. Then renew the DHCP leases on all network clients.

5

I made the change on both DNS spots and left the rest as it was (sorry about the language, I was unable to change it):

image

Saved changes and tried nslookup again:

$ nslookup flurry.com
Server:		192.168.0.1
Address:	192.168.0.1#53

Non-authoritative answer:
Name:	flurry.com
Address: 212.82.100.150
Name:	flurry.com
Address: 98.136.103.23
Name:	flurry.com
Address: 74.6.136.150

$ nslookup flurry.com 192.168.0.113
Server:		192.168.0.113
Address:	192.168.0.113#53

Name:	flurry.com
Address: 0.0.0.0
Name:	flurry.com
Address: ::

I'm not sure if I should change something else on the DHCP config.

As a side note, since I'm almost sure it's related and fixing one should fix the other, Iforgot to mention I'm also having an issue with the admin page, "This site can’t be reached" error, on both http://192.168.0.113/admin/ and http://pi.hole/admin.

6

Did you renew the DHCP leases on all clients after you made this DHCP change?

7

So I tried to do that change and then restarted the router, when it came back on it worked on the terminal but it wasn't loading any pages either, they had a DNS error.

I tried disabling and enabling pihole, and then when trying the nslookup:

$ nslookup flurry.com
;; connection timed out; no servers could be reached

Reverting the changes and disabling pihole makes it work as usual.

9

As your configuration changed, please provide a new debug token.

10

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