In this article

If local DNS resolution is failing, a possible cause is that either EDNS isn't supported or a firewall is blocking EDNS queries.

Windows deployments

Beginning with the release of Windows Remote Client 1.11.0, EDNS was added to local domain queries for failover. 

After upgrading to version 1.11.0, if local DNS resolution is failing a possible cause is that either EDNS isn't supported, such as with Windows 2012/R2 (no longer supported by Microsoft), or that a firewall is blocking EDNS queries.

Follow these steps to resolve the issue.

1. Add a registry entry to disable EDNS for local domain queries for failover
   

   • reg add “HKLM\Software\DNSFilter\Agent” /v IncludeLocalResolversEdnsRecords /d “false” /f

   • reg add “HKLM\Software\DNSAgent\Agent” /v IncludeLocalResolversEdnsRecords /d “false” /f

2. Restart the device or DNSFilter Roaming Client to apply the change

✍️ To reenable EDNS for local domain queries for failover, set the registry value to true.

macOS deployments

Follow these steps to resolve this issue.

1. In your device Terminal, open DNSFilter Agent daemon.conf
   a. see issue diagnostics for steps to navigate to the daemon.conf file
2. Add the following option to the top of the configuration file:
   
   

   IncludeLocalResolversEdnsRecords=false

   Before

   

   After

   

    

3. Restart the daemon
   

   • launchctl unload /Library/LaunchDaemons/com.dnsfilter.agent.macos.helper.plist 
     launchctl load /Library/LaunchDaemons/com.dnsfilter.agent.macos.helper.plist

   • launchctl unload /Library/LaunchDaemons/io.netalerts.agent.macos.helper.plist 
     launchctl load /Library/LaunchDaemons/io.netalerts.agent.macos.helper.plist

4. If the daemon does not restart, restart the device to push the update