Pi-hole stopped working

Help
1

Expected Behavior:

One of my clients should be using the pi-hole to block ad's. Pi is directly connected to my modem/wireless router. Client is connected via wireless. DHCP is controlled by modem/router. I changed the DNS on the client manually to the IP of the pi-hole but that did not help. My nslookup's all time-out, as expected. Pi-hole shows 2 clients but they are def not the one I am trying to set-up.
I restart the devices after every change I made as well. Hit a brick wall now.

Pi-hole v5.1.2
Web Intf v5.1.1
FTL v5.2
Raspberry Pi3 w/ static IP. client has static IP

Actual Behavior:

Client still using ISP's DNS's

Debug Token:

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

thank you

2

This Pi has some connectivity problems:

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the wlan0 interface.

[✗] No IPv6 address(es) found on the wlan0 interface.

[i] Default IPv4 gateway: 192.168.0.2
   * Pinging 192.168.0.2...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

[i] Default IPv6 gateway: fe80::c2ff:d4ff:fee2:9a7a
   * Pinging fe80::c2ff:d4ff:fee2:9a7a...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
3

Your Pi-hole may have been connected via wlan0 when you first installed it, but now you've switched to eth0, or vice versa.

You could try to run

pihole -r

and choose Reconfigure to make your Pi-hole aware of your changed network settings.

4

I saw these errors as well but they do not make much sense to me. My network is very basic. IPv4 is my gateway/modem/router and I can ping and access it no problems. I haven't ever touched the IPv6 stuff. It seems like when I set pi-hole to use my GW as the upstream DNS, it defaults to the IPv6 address. When I look at my network info from the client, specifically the DNS servers, it will show the pi-hole address for IPv4 but, is always superseded by my ISP's IPv6 address. (xxxx:xxx:feed: :1).

5

I typically reboot the pie and any device after making changes too them. I will give this a try though.
thanks

6

Rebooting won't change Pi-hole's configuration. You'd have to use the above command to achieve that.

7

After making my post I realized it was most likely not a reboot you were recommending. Thank you for the suggestion as well. I think this may have helped solve my problem. After the re-config the IP address for pi-hole now matches what my router shows and I believe the eth interface has changed. I am seeing my client and more activity on the dashboard too.

I also did an nslookup on a site using my client and it came back with
Addresses: ::
0.0.0.0
Which I read in another FAQ is a good sign the pi is blocking requests.

Stuck old configuration I guess

1 Like
8

That reads like a working configuration now. :wink:

You could also check whether connectivity is good now in your debug log yourself, or post a new token for us to have another look.

9

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