Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
Attempt to use PiHole DHCP rather than router.
Expected to enable DHCP in PiHole, then disable DHCP in router. Upon reboot/DHCP renewal each device is assigned an IP address via PiHole DHCP automatically, with length and additional settings available via PiHole dashboard
- Operating System (Family and Version)
Raspberry Pi OS Lite - 64bit, 6.12 (bookworm)
Core: 6.1.4, FTL: 6.2.3, WebInt: 6.2.1 - Hardware
Pi 4 B 4GB RAM
TP-Link AX55 Router (stock)
Actual Behaviour:
Enable Pihole DHCP, disable router DHCP then reboot router/devices. Each device is unable to connect to either the inside, or outside networks via ping or hostname, and are assigned a 169 address. Setting IP and DNS manually within Windows does restore connectivity for that device, some devices on network are unable to do this.
Re-enabling DHCP in router seems to restore connectivity across the network, regardless of PiHoles DHCP server being enabled or disabled.
Extra
Having some trouble with PiHole grabbing hostnames via conditional forwarding, having PiHole as the DHCP server does replace the IP with the hostname, this also manages to track network usage for a full-tunnel VPN running on a server within the network, which doesn't seem possible if PiHole is responsible for DNS only. Having both the router and Pihole enabled as DHCP does seem to register some devices as assigned by PiHole with a static IP, I'm certain having x2 DHCP servers, even with static IP addresses is a bad idea?
TLDR: How to monitor a full tunnel VPN via PiHole, with hostname rather than IP?