DNSFilter
Create
Log in
Sign up
Roadmap
Feedback
Known Issues
17
Changelog
Boards
Feature Requests
Known Issues
Powered by Canny
Known Issues
Items that are known issues rather than a feature request. Feature requests should go here -
https://dnsfilter.canny.io/feature-requests
.
Description
Category
Select a category
Roaming Clients
Uncategorized
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review (next Candidate)
Next (developing In <60 Days)
Developing (live In <90 Days)
Beta
More Information Needed
Launched
posts in
All Categories
All Categories
Roaming Clients (4)
Improve the Captive Portal Experience for Windows Roaming Client
Create a list of all hotel, airline, restaurant, free wifi hotspots to bypass and use localDNS resolver so that we don't need to turn off the app The list should be accessible within the UI so admins can select what can be bypassed
25
·
under review (next candidate)
64
Revert to Previous DNS Settings After Uninstalling DNSFilter
When we uninstall DNSFilter agents, the original DNS settings are not restored, causing the operating systems to lose connections and stop responding. Is there a way to prevent this issue during the uninstallation process? We would like DNSFilter to revert the NIC's DNS settings to their original state upon uninstallation.
5
6
Roaming Client Failover
When the roaming agent fails to resolve DNS queries due to enterprise network conditions such as DNS Doctoring please provide an automatic remediation method after a specified time period to temporarily disable the DNSFilter Agent. Controlling this feature through the deployment command line would be sufficient. Why: We have roaming clients that are unable to resolve DNS requests on specific enterprise networks and it's painful as the current fix is telling them to pack up their bag and leave or 4G hotspot since they don't have Administrative rights. We're working on a scheduled task script to monitor connectivity and the script will disable the Windows service, set DNS to DHCP, and flush the DNS. We have found these three steps to resolve the issue when it happens. Command-line options: AUTOREMEDIATION="enabled" allows the roaming agent to self heal connectivity issues caused by enterprise configurations such as DNS Doctoring. Automatic Remediation will temporarily disable the Windows service and static DNS configuration when a DNS request cannot be made to DNSFilter servers. When Automatic Remediation is running a connectivity check will be issued every 300 seconds on the client and if successful will re-enable the DNSFiltering Agent protection. NETWORKTIMEOUT="300" allow you to specifiy a custom network timeout before DNSFilter will attempt automatic remediation. Default is 300 seconds.
11
78
Powered by Canny