Encrypted and private DNS routing
Configure resolvers while preserving the routes used by internal and VPN namespaces.
Review your DNS dependencies
Section titled “Review your DNS dependencies”Identify public resolvers, internal company domains and any DNS routing supplied by the operating system or VPN. Check which services rely on private names before changing group DNS settings.
Configure resolvers
Section titled “Configure resolvers”In the selected group’s Base policy, review DNS Servers. PacketTale supports resolver settings for DNS over UDP or TCP and encrypted DNS over TLS or HTTPS. Configure the resolver address and options appropriate to your network.
Use Secure Protocols Only restricts allowed DNS protocols. Review this setting alongside internal resolver capabilities; enabling it can prevent a private resolver from being used if that resolver cannot meet the requirement.
Preserve system routing
Section titled “Preserve system routing”Follow System DNS Routing uses the operating system’s routes for company, private and VPN namespaces. Review Ignore System/Network Servers at the same time, since ignoring assigned resolvers changes how the endpoint can resolve names.
For matching private namespaces, the assigned resolver is used rather than an unrelated public fallback. Validate behaviour when the private route is available and unavailable.
Test the published policy
Section titled “Test the published policy”Publish the change, check synchronization and test both a public domain and a required internal service. If results differ from expectations, inspect the endpoint’s DNS state and the active trusted-network profile before changing application rules.