Roaming Client Offline Behavior
launched
Craig
If a roaming client is unable to connect to DNSFilter's DNS server, I'd like to be able to change the default behavior to use the local DNS server instead and switch to DNSFilter once a connection is finally made. We've been seeing devices that have multiple WAN connections enabled (laptop with WiFi on, connected to Dock with Ethernet), the roaming client going offline and DNS is not working. Restarting the DNSFilter Client service fixes, but a user shouldn't have to do this. In my environment, I'd rather have unfiltered DNS than no DNS.
Mikey @DNSFilter
launched
Apologies, this was completed in January 2020 and not marked appropriately.
Johan
I would love this as well. Had one roaming client that remained red and a, possibly password protected feature, to fall back to local DNS (configurable to be manual or automatic) would be great. Right now, uninstalling the roaming agent is needed to get the person back online. (only one person was affected at this site).
Mikey @DNSFilter
My apologies for this report going so long without a response. I do see that you've been in contact with our support team in the interim.
We fixed a bug on our Windows Roaming Client regarding switching between networks shortly after your request. I just wanted to make sure you were aware and make sure you are no longer experiencing issues with network switching.