How to Map Local Domains Using CleanBrowsing

If your organization uses internal domains on an intranet, CleanBrowsing's DNS Mapping module ensures those domains continue to resolve correctly when using CleanBrowsing as your DNS resolver.

Step 1: Why DNS Mapping is Needed

There are many different deployment configurations to account for when working with DNS filters. One common scenario involves local domains (found on an organization's intranet) vs public domains (found on the internet).

When you use CleanBrowsing as your DNS resolver, local domains like intranet.company.local or portal.internal will not resolve because CleanBrowsing's public resolvers don't know about your private domains. The DNS Mapping module solves this.

Step 2: Configure Local Domains

To map your local domains, navigate to Custom Domains > DNS Mapping in your CleanBrowsing dashboard.

This module allows you to map local domains so that CleanBrowsing knows where to reroute traffic. This solves resolution issues that come from local domains not resolving with a public DNS resolver.

Add each local domain and the IP address of the internal DNS server or resource it should resolve to. CleanBrowsing will forward queries for those domains to your specified destination.

Ready to get started with CleanBrowsing?

View Pricing Plans