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 instead of
lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
All clients dynamically pull down the local pi-hole IP, and all traffic requests resolve through pi-hole.
I have been researching for the last few days and have read through a number variations of this issue. I have pihole running on an rpi4 at 192.168.1.108 and I have several clients manually set to resolve through it. DHCP addresses are pulled down from the eero router, then the clients resolve via pihole. Works flawlessly.
After a few days of testing at the client level, I decided to try pihole network wide. I set a single ipv4 dns entry at the router via the eero app and nothing resolves for any client, including those that still have the manual DNS server assignment. My set up:
router: eero pro @ 192.168.1.1, primary dns set to 192.168.1.108, no secondary dns set, ipv6 off
pihole: rpi4 running a light version of raspbian @ 192.168.1.108, v5.0 across the board. OOB blocklists, gravity is up to date, ipv6 is off for eth0
rpi's resolv.conf: 127.0.0.1 only
I have tried all sorts of things like bouncing services, adding and removing dns entries on the rpi via nmcli. Several times, I have tried pihole -r, but my outcome remains the same.
Finally, I generated the debug tokens after resetting the DNS at the router to the known good configuration, so certain things appear resolving in the logs, like the following. I suspect this is because the debug log was generated after, not during the issue, though the issue is likely present just minutes before in the log. If there is a better way to run this action, happy to do it, just let me know how. Thanks!
Any help or advice would be appreciated!