This is a guide to the deployments panel in the dashboard. For an instructional walkthrough of deploying DNSFilter on your network, see our Site Deployment Guide.
Adding a Site is the quickest way to be protected by DNSFilter.
A Site is considered a single, physical location (or “network”), which usually has one static IP address but may have more if utilizing multiple internet connections or if you’re a larger organization with an IP subnet. If you do not have a static IP, then you can set it up using a Dynamic DNS entry. We explain this in our article here.
You can start protecting your network by adding a Site to the Dashboard, which should contain a friendly name (e.g., NYC Office), at least one IP address/hostname, and a physical address.
After creating a site, you would assign Policies to that Site, which determine what is allowed and blocked on a Site, as well as what the network’s end users see when they experience a block page. This is done on the very same page after saving your Site.
DNSFilter's Roaming Client for Windows operates well with most VPN applications. However, if you experience issues while your VPN is active, enable this toggle to turn off the Windows Roaming Client on this network.
The External ID field allows you to enter a unique external ID for your site. The purpose of this identifier is to enable you to integrate with external services, such as Zapier.
IP Subnets / CIDR Blocks
The Dashboard accepts CIDR ranges of /24 or less (ex: 18.104.22.168/24).
Only IP addresses that send DNS requests are required to be added to a Site. However, if you’re working with a large block of IP addresses, contact support, and we can add them to your account on the backend.
Dynamic IP Addresses
If your site has a dynamic IP address, which is common with consumer-grade internet connections, Dynamic DNS must be utilized to ensure DNSFilter always has the correct IP address for your network. If the IP address should change and Dynamic DNS is not utilized, it will result in DNS downtime, as DNSFilter does not serve DNS requests to unknown IP addresses for security reasons. Consult our Dynamic DNS Article for more information.