This post explores known antivirus software settings that can create conflicts with DNSFilter. Adjust these settings for improved compatibility and protection.

Avast Antivirus (Real Site)

The Real Site feature in Avast Antivirus proxies DNS queries to Avast’s DNS servers. This feature must be disabled to utilize DNSFilter.

This feature is not available in all versions of Avast Antivirus.

1. From the Avast app, navigate to Components 
2. Navigate to Real Site and toggle the feature to disabled

Webroot (DNS Protection)

Webroot endpoint products have a setting called “DNS Protection," which causes DNS requests to be sent to their servers.

This setting must be turned off or it will send DNS traffic to Webroot instead of to DNS Filter. Webroot products can still be used for their anti-virus and anti-malware capabilities, as long as this setting is off.

✍️ Note: Depending on the app version this process begins from a different location. 

1. From the Webroot app, navigate to Endpoint Protection or Policies and select Recommended Defaults
2. Select DNS Protection 
3. Turn Install DNS Protection off

This only changes the policy. The policy now needs applied to the endpoint to resolve the issue. 

1. From the Webroot app, select Groups
2. Create/Edit a group that contains all the endpoints with the DNSFilter Roaming Client
3. Select Edit Policy
4. Select and apply the policy to the endpoints

This policy change will take place within the next few hours, depending on the polling interval set by the Webroot software. Once this change takes place, DNS traffic can reach DNSFilter. If in use, the Roaming Client will run without conflict.

For more information, see the Webroot DNS Protection Administrator Guide. 

enSilo

The enSilo product may attempt to block communication between the computer, the DNSFilter Roaming Client, and external systems.

We have compiled a list of URLs and IP Address Ranges which are required for the proper functionality of the Roaming Client.