Seperate DNS for guest network
Seperate DNS for guest network
Tp-Link allows you to create an isolated guest network which is great however it lacks some basic functionality.
I would like to be able to give devices connecting to my guest network access to a seperate DNS. I host my own DNS locally which myt router is set to use. Whenever a device connects to my network my router gives them the ip address of the local DNS server for all their DNS queries. The issue with this is obvious, if a device connects to my guest network it is unable to reach my locally hosted DNS and therefore unable to resolve DNS queries.
Being able to add a second DNS for the guest netowrk would solve this issue.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
At the moment I just manually edit the DNS per device on the guest network
If the device frequently connects to the network I assign a static IP with my router. If you assign a static IP you can manually define DNS on a per device
basis.
- Copy Link
- Report Inappropriate Content
I had conversation on that topic with someone and suggested workaround. Here is what we discussed.
Have second DNS service and connect it to Guest Network SSID. It could be separate box or same if your current DNS host has WiFi network card. If same, configure DNS service answer queries on both IP addresses: wired from Main and wireless from Guest. I know you can do that with BIND, for example.
You now have two IP addresses for DNS service: one of each reachable on Main and on Guest networks, another is not. Configure router with these two IP addreses as your primary and secondary DNS. Most devices should be able to handle properly primary/secondary DNS with one of them down.
- Copy Link
- Report Inappropriate Content
Thank you for your suggestion.
The issue is when the guest network is isolated. When you enable isolation on the guest network the devices connected to the guest network can not talk to each other. Your only option is to use a DNS that is reachable from WAN.
- Copy Link
- Report Inappropriate Content
anoncontainer wrote
The issue is when the guest network is isolated. When you enable isolation on the guest network the devices connected to the guest network can not talk to each other. Your only option is to use a DNS that is reachable from WAN.
You are correct. Just tested it: can't even ping between two devices on Guest network when isolation is enabled, can ping when it is disabled.
That means, workaround I mentioned won't work.
- Copy Link
- Report Inappropriate Content
Hi, I requested this a couple of years ago... https://community.tp-link.com/en/home/forum/topic/259432
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Yes, I want this also.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 17
Views: 1946
Replies: 16
Voters 16
