Not sure if this ever got solved, but I’m running Pihole on my network and eero for gateway, routing, Wi-Fi, and dhcp functions. The gateway address (i.e. 192.168.0.1) is the only one that shows up in the pihole logs.
I have DNS Caching off on my eero configuration, and I’ve got conditional forwarding on on the pihole config.
Anything else I can do to have the individual IPs actually make requests to the pihole without being intercepted by the eero?
Ok—that is an excellent sanity check. Thanks for confirming.
The only difference for my setup is that I have enabled HomeKit support in the eero. Never thought twice about it, but looks like it works in part by forcing dns onto the gateway router. I’ll be turning it off now.
https://community.eero.com/t/y4ht25q/separate-dns-settings-for-non-homekit-devices
https://talk.macpowerusers.com/t/for-eero-users-did-you-bother-setting-up-the-homekit/20629/2
Ok—that is an excellent sanity check. Thanks for confirming.
The only difference for my setup is that I have enabled HomeKit support in the eero. Never thought twice about it, but looks like it works in part by forcing dns onto the gateway router. I’ll be turning it off now.
https://community.eero.com/t/y4ht25q/separate-dns-settings-for-non-homekit-devices
https://talk.macpowerusers.com/t/for-eero-users-did-you-bother-setting-up-the-homekit/20629/2
Did that do anything for you? I’m looking at that guide and the only difference I see (besides the Homekit Router support which it doesn’t mention) is that rather than give my piholes IP reservations in the eero app, I gave them static IPs outside of the DHCP lease range on the eero.