Pi-hole functioning differently after TP-Link Deco install

I was previously using my Pi-hole with an ATT router being my DHCP. I recently installed the TP-Link Deco Mesh system (Now my DHCP) and turned off Wifi on the ATT router and turned on Passthrough. I also re-installed Pihole using the same method as before (DHCP is off). I'm confused by the pi-holes behavior now.

Previously- Clients would only use Pihole if I manually changed them to Static and added the Pihole's IP in the DNS1 slot. I preferred this so that only the families Cell phones were accessing pihole. My reasoning is if i'm not home and pihole bugs out, the house would still have internet access. My family is not tech inclined. They are always on their phones.

After Deco Mesh install- All clients are using the Pihole. This was unexpected. One day I rebooted the Pi and instantly all the TV's lost internet (we stream everything) and the complaints from the family rolled in. This is what I want to avoid in case any issues happen when I am not home.

Question: Was my first install of Pi-hole a fluke and is the way pi-hole is functioning now the intended function? Can I get it to function the way it previously was using the ATT router?

Something is telling your devices that Pihole isn't the DNS server. Since the Deco Mesh is the recent change, it's probable something in the Deco Mesh configuration is handing out Pihole as the DNS provider.
Providing the devs a Debug Token would probably help narrow that down further.

You were correct, I had the Deco Mesh configuration wrong. Thanks!

1 Like