Introduction

As a Field Effect partner, the DNS Firewall can be set up on a per-client level using the organization selector, meaning that the configuration for every client is unique, and would need to be manually configured. 

But if you prefer that all your end clients use the same configuration, you can set a default partner policy that will apply to all new end clients (and, if you choose, it can be applied to existing clients). 

This is done through the organization's partner view, and this article walks through the process of setting up a DNS partner policy. 

Setting a Default DNS Configuration Policy 

Set the organization selector to your partner view and navigate to the Administration section's DNS Firewall page. From here, click create a policy.

If the Administration > DNS Firewall page looks different than the image below, the organization selector is set to a client view.

The DNS Policy wizard will open. All of the settings you select throughout this wizard will apply to all new end clients, and existing clients set to Partner Managed (see Applying the DNS Policy below). 

Start by selecting which categories you would like to block. When finished, click Next. 

For step 2, provide the URLs that you would like to restrict for all clients that are enrolled in this policy. You can also upload a .csv file of your restricted URLs. When finished, click Next.

For step 3, provide the URLs that you would like to provide full access to for all clients enrolled in this policy. You can also upload a .csv file of your approved URLs. When finished, click Next.

The final step allows you to decide how this new policy will impact existing clients in the MDR Portal using the DNS firewall. 

Selecting "Override existing client configurations" will apply this newly created policy to all your existing clients within the MDR Portal. This will remove any custom URLs or categories you have enabled for them. 

If you would rather leave all existing client configurations as they are, and only apply this policy to new end clients, leave the check mark unselected.

When ready, click Create.

If you selected the override checkbox, you will be asked to confirm your choice and warned of the impacts.

Applying and Managing the Policy 

Once you create a policy, you can see which client is enrolled in the partner policy by viewing the client's Configuration Type on their Administration > DNS Firewall page. 

Set the organization selector to the client you want to verify and navigate to Administration > DNS Firewall. The Configuration Type is the first record listed on this page.

In the example below, the organization selector is set to Adams and Sons, and since they are listed as being client managed, they are not enrolled in the default DNS partner policy. Click Update to make changes.

The Update Configuration Type window will open, and you can select between enrolling the client in the DNS policy (partner managed) or using a custom configuration (client managed).