--- title: "Device DNS" slug: "device-dns-v7-0" description: "Configure DNS effectively across different operating systems to ensure secure connections and avoid connectivity issues with AppGate ZTNA." tags: ["DNS Resolution", "DNS Resolver"] updated: 2026-06-05T19:17:37Z published: 2026-06-05T19:17:37Z canonical: "support.appgate.com/device-dns-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Device DNS DNS on a user's device can be difficult to configure due to differences between operating systems and the use of local DNS servers that may be remote from the internal DNS servers you need clients to use. --- ## Resolving appliance hostnames Controllers and Gateways need public DNS records. To create predictable behavior, the driver caches the DNS responses for both Controllers and Gateways before establishing the secure tunnel connection to the Gateways. Once the tunneled connection is established, the client uses these cached responses instead of any new internal DNS server that entitlements may have configured. This prevents issues where the client receives DNS responses from the internal domain and then cannot perform token renewal because that IP address is not accessible. When the device roams to a different network, the client reconnects, clears the cache, and restarts the caching process. --- ## Resolving protected hosts Protected hosts frequently sit within a few internal domains, so using match domain is the best way to configure the operating system’s DNS for resolving hosts defined in entitlement actions. Two problems must be addressed first: - Generic DNS configuration options across different operating systems do not always support this. - DNS behaviors may not be consistent across different operating systems. **Windows** includes a lesser-known mechanism called Name Resolution Policy Table (NRPT). AppGate ZTNA uses NRPT when a DNS policy is configured. The NRPT contains rules that specify DNS settings for given names or namespaces. When Windows performs DNS name resolution, it always checks the NRPT first for a match, and sends a DNS request to configured DNS servers only on a non-match. Windows tries configured DNS servers sequentially according to network priority. When no DNS record is returned, Windows tries the next lower-priority DNS servers until it gets a reply. When the AppGate ZTNA identity provider (IdP) is used, it sets specific DNS servers with the highest priority, so those servers always receive all DNS requests. When you also set a DNS domain name in the AppGate ZTNA IdP (not recommended), this adds one or more search domains (such as `here.mycompany.com`) to DNS search requests. This supports Windows' use of shortnames, which generates a DNS request for `youtrack.here.mycompany.com` for the shortname `youtrack`. This means there is no affinity between the configured DNS domain names and configured DNS servers. If you have two internal domains with independent DNS servers and want to avoid DNS timeout delays, both internal DNS servers must handle DNS requests for both domains. **macOS** and **Linux** use a form of limited affinity that aligns better with the way AppGate ZTNA works. For a given NIC, DNS domains are matched to the DNS server configured; then all other DNS requests are sent to the configured DNS server for the local network. You must configure both DNS servers and match domains, or DNS requests will only reach the local network DNS server. This approach works when all configured domains use the same DNS servers but does not support two internal domains with independent DNS servers. Unlike Windows, macOS and Linux have no built-in way to route all DNS requests to a server other than the local network DNS server. Because these operating systems use advanced DNS configurations, you must check device DNS settings and hostname resolution in specific ways. If you think DNS is causing connectivity issues, see [Troubleshooting user and device access.](/v1/docs/troubleshooting-user-and-device-access-v7-0) ### Private DNS Browsers and operating systems are are introducing another challenge in the form of private DNS, also known as DNS over HTTPS (DoH). DoH sends DNS requests through an encrypted connection, which makes it harder for third parties to see which websites users are accessing. Many browsers and operating systems include limited DoH fallback when local DNS providers are configured or a VPN is in use. These local settings take precedence over the configured DoH provider. Because browsers and operating systems behave differently and users may have configured fallback options differently, there is no guarantee that the configurations set by AppGate ZTNA will work. DoH settings often override all other settings, so you may need to limit or disable DoH for AppGate ZTNA to work correctly. Check the documentation for the browser and operating system combination and adjust settings accordingly.