ThreatLocker uses a Zero Trust approach to prevent threats by default, which means additional cyber security measures like adding DNSFilter's Roaming Client to your network environment require Allow Listing in ThreatLocker to avoid conflicts.

What does this look like in DNSFilter?

If you don't take the step to Allow List our agent and ThreatLocker quarantines it:

• End-users could lose internet connectivity
• Certain elements of DNSFilter Policies (e.g. SSL Certificate) could fail to install
• Query traffic to internal servers could be stopped

How to fix the issue

If you think ThreatLocker is the culprit, go ahead and adjust the account settings to allow DNSFilter.  If that doesn't solve the problem here are some other useful troubleshooting steps:

• Prep your full security environment for the new recruit: examine all your firewall, VPN, and previous DNS configurations to confirm nothing will block DNSFilter from doing it's thing  
• Confirm DNS traffic is resolved through DNSFilter 
• Check IPv6 and Local Domain settings: misconfigurations to either can result in lost connectivity for some websites but not others