Known Issues

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.

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

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.

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

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.

Request is for the DNSFilter macOS RC to work with the GlobalProtect VPN client.

Provide access to the Partner Portal to allow employees to utilise the training material. Currently with SSO enabled they are unable to access this portal and would like enroll them in the training provided.

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.

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

Specific instructions & documentations on how to configure Azure VMs to ensure DNSFilter Windows RC can be installed and operated without conflicts.