@TP_LINK Add me to the list of people requesting this feature

@TP-Link i'm another one

@TP-Link 

I think we've clearly demonstrated the use case for this request. 

Personally, I have an ad/tracking blocking DNS for main network (NextDNS, others have Pi-Hole), and want a seperate DNS for the guest network. 

That's all the request is. The ability to change DNS settings for the Guest Network. For the Pi-Hole usecase, but as someone else said, the work devices on a seperate network usecase.

Please push this up the stack and get this implemented. Seems really silly to switch mesh providers for such a simple request that many users have asked for!

@TP-Link does the guest network use the secondary DNS server?

TP-Link wrote

@jaydinho 

Hi, could you please do me a favor that there is a workaround for this issue:

Under the DHCP server, set Pi-hole as the primary DNS and 8.8.8.8 as the secondary DNS.

Could you please help me test whether it could fix this issue?

Thank you very much.

@TP-Link This would work but wouldn't this cause additional latency for each request from the Guest network wherein devices would first try to hit the primary DNS server, fail, and then call the secondary? Doesn't seem optimal.

TP-Link wrote

@jaydinho 

Hi, could you please do me a favor that there is a workaround for this issue:

Under the DHCP server, set Pi-hole as the primary DNS and 8.8.8.8 as the secondary DNS.

Could you please help me test whether it could fix this issue?

Thank you very much.

I've tried this already. It does allow for the guest wifi to connect, but invalidates the point of having the primary DNS blocking things. The main devices will fall back to the secondary DNS when Pi-hole blocks something, and thus will bypass that block.

TP-Link wrote

@jaydinho 

Hi, could you please do me a favor that there is a workaround for this issue:

Under the DHCP server, set Pi-hole as the primary DNS and 8.8.8.8 as the secondary DNS.

Could you please help me test whether it could fix this issue?

Thank you very much.

@TP-Link Agree with @Dorque .  This isn't a workaround.  Setting a secondary DNS server like this means that content blocking/monitoring won't work because the client will use the secondary DNS server if the first one is blocking the content. 

As a wider point, the ability to set specific DNS servers for the Guest network could be for any number of reasons.  For me, and a lot of the commenters on this thread, content-blocking and/or monitoring is the primary one, but the ability to set DNS servers is such a basic networking feature I feel it has to be implemented to make the Guest network on Deco mesh networks suitable for anything beyond the most basic of setups.  It's really frustrating that your dev team keep seeming to push back on this.

@TP_LINK Add me to the list of people requesting this feature.

Or even giving the Guest Network a default DNS like 8.8.8.8, but not the non-accessible DNS from the main network (a Pihole in my case)

Upvoting this feature request.

My use case would be that Guest Wifi Networks DHCP by default should be able to use a limited DNS, like 1.1.1.1 For Families from Cloudfare.