Known Issues

Breaks all local domain inquiries.

I migrated from the original Ansible deployment to the Relay Manager and generated a new relay.conf. When I reboot the VM, the docker container does not autostart, and I think it should. I have tried both relay-manager start and relay-manager install in case it was a config issue, and config-manager update to make sure everything was up to date. OS: Ubuntu 22.04.5 LTS Docker: 28.2.2

Allow Site Filtering Policy allow lists (and block lists) to override the global enforcement of Universal List block/allow lists. You could add a a per-policy toggle: “Allow policy to override Universal Lists” Use case: We manage multiple client sites with a consolidated global blocklist applied via Universal Lists. For certain clients/sites, we need to permit specific domains that are blocked globally, without weakening the global list for everyone. Our currently non-ideal workaround is: Remove the domain from the Universal List. Add the domain manually to every other site’s block list, because each site uses a custom filtering policy.

Show when a domain is apart of multiple AppAware Apps. An example of this is some Twilio domains show up under SendGrid. So if you're blocking SendGrid, it will show the reason a domain was blocked for some domains was due to AppAware and it will show the Twilio app, instead of the SendGrid app. This causes issues when trying to troubleshoot why something is being blocked and having to do a lot of "shots in the dark" instead.

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.

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.

The ability to allow the RC to connect to DNSFilter when there are two NICs present in a Windows or Mac workstation equipped as such.

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