Known Issues

Apple restricted the ability for apps to capture device names in iOS 17, limiting the ability for the Roaming Client to report the device name to the Dashboard for reporting or troubleshooting. We're evaluating other methods to restore this functionality in our next iOS Release.

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

Currently, the CSV import will fail (with no error message to say WHY it failed, no less) if there are any carriage returns anywhere in the file. MS Excel is probably the most widely-used editor of CSV files in existence, and MS products are notorious for adding unnecessary things like that. The CSV import process should take this into account, and should remove or ignore any blank spaces at the beginning or the end of any/all data, as well as any carriage returns, or any other wonky stuff that may get added without the user's knowledge. This is in everyone's best interest, as it will directly reduce the number of help requests DNSFilter has to field in relation to CSV import processes, and will create a much smoother user experience as well.

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.

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

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

Requesting documentation on how to change roaming clients from 53 to 5353 or 853 for a MacOS. I was under the impression I could add upstream_order=[ "tcp-tls", "udp", "tcp" ] to /Library/Application Support/DNSFilter/daemon.conf until I realized this seems to be only in environments that use a relay server and relay.conf file? Does the daemon.conf not allow to change the upstream_order or change the ports used locally on the MacOS? We have services running on our Macs that conflict with udp port 53 and need the ability to use the available 5353 or 853 ports potentially. The documentation doesn't make it very clear if those other ports are only available outside of local macos configurations.

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.

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