Roaming Client Auto On/Off | Voters

Roaming Client Auto On/Off

closed

Craig

Give the ability for the roaming agent to detect if the DNS on a LAN is already forwarded to DNSFilter and use the network's DNS instead. This way DNS queries from roaming clients will automatically associate with the site/network they are actually at in the Dashboard.

June 20, 2019

Carl Levine

marked this post as

closed

This has largely been solved through iterative development on the Roaming Client over the last 6 years since this request was created.

Mike Schroll

Craig Can you clarify? You're saying that if you roam on to a different DNSFilter customer's network; you would prefer that the roaming client stop following your policy, and send traffic through their resolvers so that THEIR policy is enforced instead??
If you're talking about your own network -- Roaming Clients are already associated with a site/network -- and so will show with that network/site in our interface.
I guess maybe you're saying "Allow a setting so that if a Roaming Client is on the site it is assigned to in the interface, and the DNS set before roaming client takes over goes through DNSFilter, then just allow it to keep using the DHCP-assigned DNS settings"?
It's possible -- Can you tell me more about what the benefit of this is to you?

Andrew

Mike Schroll: What we are seeing is that with the client on a machine it sets the dns to be 127.0.0.2 meaning it cannot operate inside the clients network as the local dns server simply vanishes and we cannot log onto the domain. This is a real nightmare

Craig

Mike Schroll: I didn't think about my users roaming on other DNSFilter customer's networks. What I'm looking for is a way to associate the roaming client in reporting with the site they are actually at. So for example, I have users that today may be at Site 1, but tomorrow they are at Site 2. I'd like to be able to see on the reporting their actual usage at Site 1 for today and Site 2 for tomorrow. Currently all reporting goes to the Site that the roaming client is manually assigned to.

Craig

Andrew: I'm not having this issue. The Roaming client is suppose to exclude the local domain DNS queries. So for example, my domain, Contoso.com, the roaming client has detected the DNS suffix Contoso.com via DHCP and sends all queries for *.contoso.com to the local DNS server. I have found you have to use DHCP or the roaming client will have unexpected behavior with static IPs.