Knowledge Base

How to configure site overrides for DNS Protection

How to configure site overrides for DNS Protection
Userlevel 3
Badge +14
Configuring web overrides for Webroot DNS Protection

Web overrides are managed in the Webroot Management console, under the Overrides tab, specifically in the Web Block / Allow List sub tab. These allow exceptions to be made so that domains can be explicitly allowed or blocked, regardless of what categories are blocked or allowed by the assigned DNS policy.

Overrides are helpful when a category is blocked, but you want to allow a site that is classified as the blocked category or if a category is allowed but you want to block a specific site belonging to that category.

Check the section for your console type to see more information related to the available override types, click here for assistance in determining console type.

Multi-site Webroot Management consoles
Multi-site Webroot Management consoles have two types of overrides:

1. Global
  • Configured and managed at the main, top level console
  • Global overrides can be applied to all sites
2. Site
  • Configured and managed at the site console
  • Site overrides are specific to that site.
Notes for multi-site consoles:
  • Site overrides take precedence over Global overrides.
  • In order to apply Global overrides to a site, the site has to be configured to Include Global Overrides. This is enabled under the Sites tab, click the Manage button for the site, go to the Endpoint Protection sub-tab, check the box to enable Include Global Overrides.
Single site Webroot Management consoles
Single site Webroot Management consoles will only have site level overrides.

To add an override for DNS Protection:

1. Log into the Webroot Management console, click the Overrides tab, then select the Web Block / Allow List sub-tab.

2. Choose the console type in use to see the next step:
  • If using a multi-site console, under the Select Overrides to View drop down menu at the top, select GSM Global Web Overrides to add a global override or select a specific site to create an override for that site.
  • If using a single site console, proceed to step 3.
3. Click the Add button, which will open the Create New Entry window.
  • If using a multi-site console, the Global or Site Override drop-down menu controls if the override created is a global override or a site override.
  • If using a single site console, the Global or Site Override drop-down menu will not be present.
4. Enter the URL into the URL field and choose the Action Allow or Block.
  • The Block Malicious URLs setting controls only applies when the Allow action is selected. With this setting checked, the service will check the URL for malware and will block access to the site if malware is detected. Disabling this setting will stop the malware check and provide access, even if the site is malicious.
5. Click the Create button.

For additional information on Overrides, see our DNS Protection User Guide.

This topic has been closed for comments

3 replies

Badge +3
We have a customer who is requiring to have access to DNS protection block/allow list in real time. However it seems there is no way to give Site admin this access (customer admin can not be GSM admin). Is there any way to enable customer to have visibility and control to their site's block/allow list?
Userlevel 7
Badge +35
Hi @JNYMAN , I would recommend that you reach out to our support team as they can let you know the best solution for your specific situation. You can open a ticket or call them at 1-866-254-8400.
Badge +3
An update/note if someone has similar issue: I did contact Webroot rep and it seems the only user that can access Web Block/Allow List is indeed GSM Global admin. So no customer access unless we set up a customer specific GSM instance. According to Webroot, there is no feature planned that would allow lower level user to edit that list (per site or global).

Cookie policy

We use cookies to enhance and personalize your experience. If you accept or continue browsing you agree to our cookie policy. Learn more about our cookies.

Accept cookies Cookie settings