Set DNS to ChurchDNS

Configure your DNS directs traffic from your network to the ChurchDNS Resolver Network.

When a DNS request is made from a network pointed at our DNS IPs, ChurchDNS applies the security settings in line with your filter policy.

 

If you wish to test policy on a single workstation instead of entire network, you can simply change your local machine DNS to ChurchDNS resolvers assuming you local workstation is on same public IP. Be sure to change DNS back to default when leaving the network.

 

If you are an active directory/domain controller environment, please refer to this detailed guide for configuring DNS in your environment.

 


Step 1 - Locate your network DNS server settings


Identify which device or server on your network points your client devices to your public DNS servers. This is usually a router or sometimes a firewall. Typically, the device that handles your IP address (DHCP) or the device that serves as your default gateway is also where you configure public DNS servers.


Step 2 - Log on to the server or router where DNS is configured


Once you’ve logged in, find the DNS settings for this device. If you're unsure of where these settings are, please refer to your device configuration manual. 


Step 3 - Change your DNS server addresses


Change your DNS server address to IPs provided from us. If you do not have your IP addresses please open a ticket.


Make sure your DNS is set to be static. Write down the previous DNS server information in case you wish to revert the change.

** Advanced users may try to work around your DNS settings to add their own. This can be fixed by creating firewall rules. To create firewall rules restricting DNS go here.

 

*** Remember to clear ALL CACHE in local machine, browser, and domain controllers if applicable.

To confirm your system is now using ChurchDNS Resolvers, click here: verify.churchdns.com

 

Next, it's time to create a filter policy.

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.