Test DNS Filtering in Nebula

Once you've configured your DNS Filtering rules and applied them to a policy in Nebula, a plugin is installed across endpoints assigned with the policy. The installed plugin monitors your network traffic and blocks access to restricted categories set in your DNS Filtering rule.

We recommend creating a test DNS Filtering rule against a small number of endpoints before a broader deployment:

1. Create a test policy called DNS Test Policy.
2. Create a test group called DNS Test Group with the test policy assigned.
3. Create DNS Filtering Rule with the test policy assigned.
4. Move an endpoint into the test group.
   • The DNS plugin should download immediately and be visible in console.
     1. Go to Manage > Endpoints.
     2. Click on the endpoint that was moved.
     3. Click See more details.
     4. Confirm the DNS Content Filtering plugin is in the Agent and plugins section.
        
        • If the plugin is not displayed, see Troubleshoot DNS Filtering in Nebula.
5. Monitor the DNS Filtering activity dashboard for blocked and allowed DNS lookups.
   • Modify the rule to add Categories, and Allow or Block specific domains as required.

If you want to locally test your endpoints to verify the module plugin is installed and working, use the following DNS Filtering category links in the table below.

Test URLs

If a block page does not appear, verify your DNS Filtering configuration or check the status of the installed services.

Check service status

To verify the services are installed and running:

1. Open Command Prompt as an administrator
2. Run sc query mbdnsfilter
3. Run sc query dnscrypt-proxy

Note: If the services are missing or domains are still not being filtered properly, see Troubleshoot DNS Filtering in Nebula.

Return to Malwarebytes Nebula DNS Filtering guide.