I have the Pi-Hole acting as the DHCP server and DNS server too and this works fine for 23 hours and then it flops and I don’t understand why.

Basically after 24 hours, all devices just disconnect from the router and when I try and reconnect them, they say they’re unable to get an IP address.

But before they drop connection, they all report the DNS server as the Pi-Hole.

If I change my DHCP to static and connect to my router, I see that the Pi-Hole is still connected with its static IP just fine.

If I factory reset the router and then add the same SSID and password, the Pi-Hole automatically reconnects and then all devices can reconnect again, so I’m unsure what the issue is.

Can someone break this down. I feel stupid for not understanding what’s happening here.

  • @sabreW4K3OP
    1•1 month ago

    if you can see pi-hole from the router, can you connect to it over SSH and see what pings and what it thinks the network looks like?

    When it goes tomorrow around 11 o’clock, I’ll SSH in and report back.

    Also did the VM router just turn DHCP back on with the wrong settings?

    Nope, when I log into the VM router admin page, DHCP is still off.

    Is pi-hole over WiFi? if it is that could your issue, DHCP/DNS should be over cable as they are required for stable networking

    Yep, the Pi-Hole is hosted on a Pi-Hole Zero 2 W, so it’s WiFi only. I thought setting the DHCP lease time on the Pi-Hole to a year would solve the issue, but nope, after 24 hours, everything disconnects and the only way to get them to reconnect is to factory reset the router.

    • Matt The HorwoodEnglish
      2•1 month ago

      I would read up on static ip on the pi zero, not via DHCP. That might sort your issue