Pi-hole takes out the network daily

Expected Behaviour: function as it had prior to upgrading to v6

  • Operating System: Raspbian GNU/Linux 12 (bookworm)
  • Hardware: Raspberry Pi Zero W Rev 1.1, 512 MB
  • Router: Verizon G3100

Actual Behaviour:

Approximately once a day, the entire network (wired and wireless) goes down. By that, I mean that no machine on the wireless network can connect to the WiFi access point or even see that it exists. No machine on the wired network can make any internal or external connection. This has only happened since upgrading to v6.

The only way to bring the network back up is to hard reset the router using the recessed button on the back. After it is reset, I can connect to the router, set up the network (changing SSID and password from the default), and then connect to Pi-hole. Everything works as expected for 24 hours, then it repeats.

The router settings I am using are as follows:

  • Disable IPv6
  • Assign static IP to Pi-hole
  • Set DNS to the above static IP
  • Set DHCP IPv4 address distribution to only allow the single IP for the Pi-hole

Then on the Pi-hole:

  • Select IPv4 DNS as Cloudflare
  • Enable DHCP server to serve addresses outside of the single IP for the Pi-hole
  • (Note that when I first view the DCHP server page via the web interface, it is unchecked and address ranges are blank. When I refresh the page, I see what I expect to.)

Debug Token:

https://tricorder.pi-hole.net/zVd7f2kK/ (This is taken from immediately after resetting the router after such an event. I did not change the settings on the router from the default at this point except for the SSID & password.) The network went out at approximately 7:23 PM local time (EDT).

Thanks for any help you can provide. I have tried following similar threads and none of the solutions have apparently worked for me. It is frustrating because I need to wait a day each time to see if the setting change I implemented worked.

update
Using the router for DCHP as opposed to the Pi-hole has resulted in the network staying up since my previous post, a period exceeding 24 hours. So it seems to be DHCP-related.

These symptoms are usually related to the lack of a static IP.

I see you are using the router DHCP to assign a single IP to the Pi, but apparently this is failing.

Did you try to configure a static IP directly on the Pi OS?

I am now trying that and following this guide. I am at Step 6 and am unsure of what to put as the DNS server. Should this be public (e.g., 1.1.1.1), the router (192.168.1.1), or the static IP I assigned to the pi itself (192.168.1.2)?

Your Pi-hole and router should have an external DNS server, whichever DNS you like (I use OpenDNS).

Your DHCP server, whether it’s your Pi-hole, router, or another device, its settings for DNS should be your Pi-hole’s IP address. When a DHCP client requests to connect, it’ll receive the Pi-hole’s IP address for DNS.

Any client on your internal network, whether static or on DHCP, their DNS should be set to your Pi-hole’s IP address.

Any static client you wish for it to bypass Pi-hole, just enter the IP address of the external DNS server of your choice into that client’s DNS field. I do this once in a while with my iPad mini for certain web sites that I need for it to work.

So now that I truly have a static IP, should my next steps be turn off DHCP on the router and turn on DHCP on the Pi-hole? Then set DNS on the router to the static IP of the Pi-hole?

I'm trying to avoid configuring each individual client to use the Pi-hole.

This seems to have worked!

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