Testing Your Connection

Article author
Josh L
  • Updated

After you have added your site to the DNSFilter dashboard, it is best practice to configure our DNS servers on one computer in order to test your policy settings and check for conflicts. After this test is successful, you can feel confident rolling out the change on your entire network.

Input the DNSFilter IPs listed below into your network adapter. You can make this change via the graphical user interface for your particular platform or using the commands below:

Windows Powershell

# Use below line for Wi-Fi adapter
Set-DnsClientServerAddress -InterfaceAlias Wi-Fi -ServerAddresses "",""

# Use below line for Ethernet adapter
Set-DnsClientServerAddress -InterfaceAlias Ethernet -ServerAddresses "",""

# Confirm change with

Mac OSX Terminal

# Use below line for Wi-Fi adapter
networksetup -setdnsservers Wi-Fi

# Use below line for Ethernet adapter
networksetup -setdnsservers Ethernet

# Confirm change with
scutil --dns | grep nameserver


There is an article on changing to custom DNS on a Google Chromebook here: https://www.howtogeek.com/204672/how-to-change-the-dns-server-on-a-chromebook/

Linux Terminal

# Backup current resolv.conf
sudo cp /etc/resolv.conf /etc/resolv.conf.bak

# Set DNSFilter nameservers
echo -e "nameserver\nnameserver" | sudo tee /etc/resolv.conf

Testing in the Browser

Now that the DNS addresses have been set, you can perform a test of your filtering policy to make sure that everything is working correctly. We recommend that you try the following in your browser:

  1. Verify your policy is active and filtering your desired categories by visiting debug.dnsfilter.com
  2. Attempt to browse to a well-known domain that is allowed by your policy (i.e., google.com)
  3. Attempt to visit a domain in your policy Block list

Use Incognito Mode

If you have visited a website 5-15 minutes prior to blocking it in your policy, you may notice that you are able to visit the site even after it is blocked. This is because the page has already been loaded into your browser cache. Therefore, it is more effective to run initial tests in incognito mode so that you can eliminate this dynamic. Policy updates take place globally across our servers in < 1 second, so this is only a temporary issue caused by visiting a site just prior to blocking it.

If everything is working as expected, you are now ready to deploy DNSFilter on your entire network. See our next article on Configuring Your Network for a walkthrough of common scenarios.

If you run into any issues, see our Site Troubleshooting section. The most common issue is to receive an error message like the one below. This indicates that DNSFilter does not recognize the IP address from which the DNS requests originate. Please ensure the IP address listed on the page is added to your site in the Dashboard. You may wish to visit whatismyip.com as well to verify.


Was this article helpful?

9 out of 11 found this helpful

Have more questions? Submit a request



Article is closed for comments.