Pi-hole DHCP Server lose connection every 24 hour.

Help
1

Hello! I recently purchased a Raspberry Pi Zero 2 Wireless for the sake of installing Pi-hole in it, in order to use it as a DNS Blocker. For the past two weeks, I've been having issues with the DHCP Server of Pi-Hole in which it stop functioning after 24 hours. This is apparently a common problem for some people with different solutions based on the underlying error. For context:

  • Operating System (Family and Version):
    • PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
      NAME="Debian GNU/Linux"
      VERSION_ID="13"
      VERSION="13 (trixie)"
      VERSION_CODENAME=trixie
      DEBIAN_VERSION_FULL=13.4
  • Hardware: Raspberry Pi Zero 2 W Rev 1.0

Today, I tried to turn off the DHCP Server in my Fios Quantum Gateway (G1100) router, and set the range of the DHCP server in Pi-hole to not include the static IP Address of my Raspberry Pi. However, the same error occurs in the log.

Debug Token:

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

2

Usually this problem happens when the user forgets to assign a static IP for the Pi-hole machine before disabling the router DHCP server.

The debug log shows Pi-hole is using 192.168.1.55, but it also shows this IP was set by a DHCP server (dynamic):

   2: wlan0:  mtu 1500 qdisc fq_codel state UP group default qlen 1000
       inet 192.168.1.55/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

Where/How did you configure the static IP for Pi-hole?

If you did this on the router, this DHCP lease won't be renewed when you disable the router DHCP.

You need to configure the static IP directly on the OS network settings.

3

I'm back! I replied to your post through email, but in case you missed it, I mention that I did set up a static IP Address for Raspberry Pi using nmtui. Here is the screenshot for proof that the IP Address is still set.

image
image620×429 27.2 KB

I don't know why the log is showing it as dynamic. Heck, when I use the command ip -4 addr show, it shows dynamic as well.

4

So I realize that I made a silly mistake. The screenshot that I show above higlights me setting a manual IP address in the ethernet connection. However, since I am using the Wi-Fi connection, this does nothing for me. I went ahead to fix this mistake. Hopefully, by tomorrow, it will be working!

5

Just remember to undo the changes you made to the Ethernet interface, to avoid conflicts with wlan0, since you used the same IP for both interfaces.