Known Issues

Currently even when Interstitial Page Feature is Disabled the block page can take over 10 seconds until it loads which is a disaster this has been this way forever and its a total disgrace

Please can these be an update on the latest issues with MacOS silent installs via RMM. Currently we are stil not able to install DNS Filter via script on an RMM on MacOS 15. It was aknowledged by Bailey Taylor at the bottom of this page: https://help.dnsfilter.com/hc/en-us/community/posts/33941697546387-Deploying-macOS-Roaming-Client-using-Jamf-Pro but we've seen nothing since.

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.

I have encountered issues where DNS agent are not working even if it has started successfully on windows services. I have to manually stop and start the service to make it work. I hope there will be a function where we can monitor the last sync activity of the users or the status of the DNS agent connection on the portal for us to have a heads-up information on which agent fails to load up and for immediate troubleshooting.

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.

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

We are running into issues in an office that has Comcast SecurityEdge and a static IP. We don't know when Comcast turned on SecurityEdge. We know that DNSFilter's icon is green in that office. We use Microsoft Global Secure Access (GSA) Entra Private Access as a ZTNA feature across all the offices, especially for IT. When DNS Filter is green, Microsoft Global Secure Access client won't connect. This is not just happening to the office but is happening to another user who uses Spectrum Internet. GSA has three features. Send all MS traffic through MS Servers - we want to use that. That is a really good anti-phishing tool. Entra Private Access (vpn replacement) - we use that today DNS Filter competitor- we don't want to have to use that. This issue is also happening with Spectrum

Check for non-whitelabel roaming client when installing whitelabel version to avoid configuration issues.

Hi enforcing safe search is very benefitial but when i go incognito it turns straight off and its not enforced anymore

A lot of seemingly basic documentation does not exist for DNSFilter products. I have requested documentation for roaming client config and relay config, neither of which exist in a complete format. This would save time for both customers and DNSFilter's support team. Additionally, there are some pretty glaring inconsistencies in the documentation for the relays using docker (using the docker compose file directly from the docs does not work correctly). Some more attention to detail regarding documentation would be greatly appreciated.