no worries just trying to help the deco units do appear work well

Would be amazing to have this, I would like my IoT and guest networks on different IP address ranges

I'm facing the same problem. It would be nice if I can set a different DNS server for Guest Network.

I am facing the same problem. It would be nice if I could set a different DNS server for my Guest Network.

Just want to +1 this, I've recently set up adguard on my network and can't avail of it without breaking the guest network.

 

I have set my DNS to adguard as primary and 1.1.1.1 secondary, and yet I find I'm using 1.1.1.1 and thus getting ads quite often.

 

If I remove 1.1.1.1 the guest network can't work as it doesn't have access to adguard.

Had an AXE300 from Frontier, downgraded service and bought a BE550... Very happy with it thus far EXCEPT for this DNS server issue.

 

It's April 2024, is there still really no workaround for this? Shocked to see such a large thread for this feature request continue with no solution from TP-Link...

Would love to use the guest network on my device without giving up my Pi-Hole.

Really need this, without it guest wifi is useless for me.

My guest network can't connect to the internet.

  @pennypacker 

 

Yeah, I've said it before but for anyone else in this boat who's just waiting to buy their next non-tplink router, in the meantime probably your cheapest and quickest way to get pi-hole working on the guest and main networks is just to run 2 instances of pi-hole. For me that means 2 pi zeros, but if you have a server you could probably just set it up in a docker container on each network. The router let's you set a primary and secondary DNS server. Set the primary to your main pi-hole's ip and the secondary to the guest pi-hole's ip. This way your clients will all always be using pi-hole, just the instance that they can access. Your guests will probably try and fail to reach your main instance but they will have access to the secondary pi-hole.