In this article

Network admins review this article to setup local domains and resolvers during DNS Relay setup. 

Review our local domain and resolver guide for more detail on how this solution can work in your network environment. 

Configuring local domains and resolvers with a DNS Relay ensures that internal resources—such as shared drives, domain controllers, shared printers, and custom applications—resolve correctly without being filtered or misrouted. This setup is especially beneficial in environments where multiple network segments require centralized DNS resolution, such as larger networks with distinct subnetworks with their own range of IP addresses and potentially different routing rules.

By specifying local resolvers in the relay’s config file, organizations can maintain seamless access to internal services while still enforcing DNS security policies for external traffic.

How Relays handle DNS Traffic

The DNS Relay acts as a bridge between a network and DNSFilter, serving as an on-premises DNS server. When a device queries the relay, it modifies the request before forwarding it to DNSFilter for filtering and enforcement.

Configure local domains and resolvers

To ensure internal resources like shared drives, domain controllers, and local applications resolve correctly, the relay must be explicitly configured with the local resolver’s IP in the config file. While .local domains are automatically routed to the configured local DNS, other internal domains must be manually specified. Without this configuration, the relay will forward all unresolved queries to DNSFilter, potentially blocking access to internal resources.