Feature Request - Guest Network separate DHCP/DNS settings
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Feature Request - Guest Network separate DHCP/DNS settings
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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
I'm also having this issue. Need separate DNS guest settings, or allow/forward DNS request to main network DNS.
Currently the workaround is manually enter DNS settings on guest device.
- Copy Link
- Report Inappropriate Content
@TP-Link count me in.
Same issue als mentioned above: I'm using an internal PiHole which is not accessible from the guest wifi.
It would only make sense to use a different DNS for the guest wifi.
- Copy Link
- Report Inappropriate Content
I agree with all of the above that this feature is lacking. Only workaround I can think of currently (for the pi-hole use case) is to set up a whole separate dns server on the guest network and then use that as your "secondary dns" ip. Still not ideal, as then there's no backup, but better than nothing I guess.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@richpriest what I wound up doing was putting a second pihole on a second rpi, and having that connected to the guest network. So everyone on my guest network tries the primary DNS but can't get to it since it's on the primary network, and then they try the secondary DNS which they can get to, since it's on the guest network. Your guest devices should be able to see each other (might be a setting I'm forgetting).
- Copy Link
- Report Inappropriate Content
I just registered to say have another upvote on this feature, I work from home and want my work devices on the guest network, I am also running a pi.hole but would be much easier if I could specify a different DNS for the guest network.
- Copy Link
- Report Inappropriate Content
Upvote from me: being unable to specify guest network DNS settings is the only really weak part of my Deco S4 setup.
I have two local DNS servers (AdGuard Home on Raspberry Pi x2) which cannot be reached when Isolation in the Guest Wi-Fi network is turned on. If I could set specific DNS server(s) for the Guest network in the Deco app or web interface (for example, use CloudFlare 1.1.1.1 DNS), the problem would be solved: main network users would have local DNS and isolated Guest network users would have CloudFlare DNS.
As it stands, I have the choice to either disable Guest Isolation (which kind of defeats the point of a Guest network) or set a third, non-local, DNS server in my DHCP settings (which adds another complication with regard to content and category blocking).
Hopefully this feature is added soon.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 20
Replies: 0
Voters 4
