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
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I'm replying with a solution. I have XE75 Decos and I recently installed PiHole on and old laptop with a Linux install. I ran into the guest network issue. So my fix was to take a second old laptop and install everything again, then set the 1st install as the primary DNS and have it connected to the main network, and the 2nd as the 2nd DNS and connected to the Guest Network.
It seems to be working. Kind of a pain. But cheaper than buying new routers at this point.
My next ones will be able to do this. So I'm not going to buy TP-LINK again when it comes time to upgrade , if they don't create a DNS setting for guest networks.
- Copy Link
- Report Inappropriate Content
@iPassButter That's not a solution, it's a workaround.
- Copy Link
- Report Inappropriate Content
I'd like to see separate DNS configuration for the Guest network. I am running a primary and secondary pihole DNS servers on my main network which makes it impossible to enable the Guest network.
I'd also like to see a separate DNS configuration for Isolated devices so that I can Isolate my IOT devices. I can enable the IOT network and place my IOT devices on it since that permits routing to the main network so there's no issue accessing the DNS, but what I really want to do with my IOT devices is to isolate them, and obviously they wouldn't have access to the local DNS at that point.
I see that this has been a feature request for a long time, but perhaps just a few more votes are all that's needed to convince the feature team that this is worthwhile.
- Copy Link
- Report Inappropriate Content
Same issue as everyone else. I bought this mesh system for my parents and regret it. The pi hole doesn't work with either the guest or iot network. So you end up having all devices share the same network which ruins security. Won't buy another tp Link product...lesson learned. Allow separate DNS entries per main, guest and iot networks.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @TP_LINK,
We're approaching the 3 year mark since my post, and have yet to have an update further than 'we'll look into it'. Is there an update please?
- Copy Link
- Report Inappropriate Content
This is shameful for a company which has official guide for how to add pihole as a dns for their routers
Does your engineers even test the functions before deploying ???
I have a tri pack S7 which has its Guest Network functions rendered useless due to your lack of expertise
This feature should not be "Future Consideration" .. this should be "Urgent"
why do you even have a guest function and custom dns function if you can't fully utilize it
Engineers in TP LINK should be ashamed to not implement a necessary option even after 2+ years of users asking
Never going TP LINK again
Also remove the recommended solution from last message... it isn't a solution
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 131
Views: 28856
Replies: 188
Voters 119
