Future Consideration Feature Request - Guest Network separate DHCP/DNS settings
Hi @TP_LINK,
I've had rock solid performance so far, and do like the Deco Labs options (although the Wifi Interference check results show 'low' then say underneath that there is significant interference), I do, however, have a feature request to put forward.
My use case:
- 3 x Deco M5s in Router mode
- Several wired and many wireless devices on the main network
- Several wireless devices on the guest network (my work devices)
- DHCP is handled by the Deco, and DNS is served by another server on the main network.
If I set the DNS to only have the DNS server, both the main and guest network use these settings. This causes the guest network to fail as it is segregated from the main network where the DNS server resides.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@richpriest I too want this separate DNS for the guest network feature. I have internal DNS that I want to use for my internal network, but I don't want Guest clients to be able to access it. If I set 8.8.8.8 as the primary option, then I can't resolve my internal systems names cause obviously Google doesn't have my info.
Anyway, the only fix I found that solves it for me is to add my DNS server first and then add Google (8.8.8.8) as a secondary. This seems to allow my guests to access the internet and still allow my internal connection to resolve internal DNS names. It does mean that they are still trying to use my internal server first and then once it fails it uses google.
Jim
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I also want this separate DHCP/DNS for the guest network. Without this feature, the guest network is useless for me.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
+1 to this feature request. I just bought the Deco WiFi 7 mesh system and everything has been great except for this issue. The guest network is useless with pi-hole on the main network.
I would argue that not being able to separately configure the DNS server for the guest network is a critical bug and not a feature request. It seems like an oversight that an isolated guest network depends on something outside of itself.
- Copy Link
- Report Inappropriate Content
Completely agree with @Deco-Gecko. This is a bug, not a feature request. Why on earth would a separate vlan not have it's own DHCP/DNS config... either laziness or neglegence.
And the workaround you offer is laughable. Why would I have a guest network if I need to tell manually configure DNS for all my un-trusted devices (or worse, tell guests to do so when they connect)...
- Copy Link
- Report Inappropriate Content
As this has now been more than 3 years and most of the replies are either agreements or totally useless 'fixes', I'm now bowing out of the TPLink ecosystem.
I've been a long standing customer, even recommending your devices to many as part of my IT career, and assisting many on these forums (and Reddit), but the lack of support here is enough for me to jump ship.
- Copy Link
- Report Inappropriate Content
@richpriest same here, been waiting for 2 years for this to come but no proper actions are taken. Already moving to Unifi brand with all my wishlist already exists.
- Copy Link
- Report Inappropriate Content
@richpriest oh, I moved on about 2 to 3 years ago already. Purchased an ASUS GT-AX11000 and never looked back. Have over 70 devices connected to it and I no longer have the router constantly crashing (which the TP Link one would do) due to their firmware update not being able to handle that many devices.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 183
Views: 72316
Replies: 259
Voters 172
