--- title: "Device DNS configuration" slug: "device-dns-configuration-v7-0" tags: ["Device DNS", "DNS Resolution"] updated: 2026-11-20T15:56:05Z published: 2026-11-20T15:56:05Z canonical: "support.appgate.com/device-dns-configuration-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 configuration The AppGate ZTNA system supports two DNS configuration methods, both designed to provide consistent DNS behavior across different operating systems. Each uses specialized configuration options with a special syntax, delivering the optimal match-domain model for DNS requests. If you are not are using the client DNS auto-configuration option, add an entitlement so the user's application can access the DNS servers you have specified. Leave access control set to *Always Allow Action(s)*. --- ## Using DNS auto-configuration (preferred method) Client DNS auto-configuration eliminates the need to manually create a DNS policy, an associated entitlement, and any related groups. Client DNS auto-configuration uses your resolver's DNS settings for clients when no other DNS policy exists. When configuring a DNS resolver for the Site, define the DNS server and the match domain. Then select *Enable auto-configuration* under ***Client DNS*** to configure the client identically to the Gateway. AppGate ZTNA then automatically creates a DNS policy and a suitable entitlement. AppGate ZTNA assigns this automatically when a user has at least one other entitlement for this Site and no other DNS policy assigned. See [Configuring Sites](/v1/docs/configuring-sites-v7-0#dns-resolving) to configure DNS using auto-configuration. --- ## Using a DNS policy (advanced method) A DNS policy lets you configure multiple DNS user groups within one system based on criteria such as IdP or user geolocation. See [Configuring policies](/v1/docs/configuring-policies-v7-0#dns-policy) to add a DNS configuration. You do not need to use special syntax with a DNS policy unless you require a default domain. The DNS policy generates the affinity pairs that link specific DNS servers to DNS domains. The policy generates as many pairs as required, which you can specify in any order: `10.11.12.13 <> foo.com` - This setting uses `10.11.12.13` but only for DNS requests ending in `foo.com`. The most specific domain has the highest priority: `10.11.12.13 <> foo.com10.11.12.113 <> bar.foo.com` - This setting uses `10.11.12.113` for DNS requests ending in `bar.foo.com` and `10.11.12.13` for DNS requests ending in `notbar.foo.com`. After all match domains are processed, the system DNS (default) resolves all remaining DNS requests. ### Default domain syntax - Mobile clients use the built-in VPN implementation of the mobile operating system, which requires a default DNS server. For iOS, iPadOS, Android, and Chrome OS, you must include a *default* domain or no DNS settings will be applied. (For example, you can set the *default* domain to `8.8.8.8` and have a match domain to an internal server such as `172.10.1.20`.) - Lite clients operate in a less advanced environment than the standard client but still require a configured DNS server. For this type of client, you must include a *default* domain or no DNS settings are applied. - Desktop clients may need to override the system DNS and send all DNS requests through AppGate ZTNA, for example to route traffic to a secure internal DNS server. You can include a *default* domain for desktop operating systems. To specify a *default* domain, enter `default` in the *Match Domain* field and add one or more IP addresses in the *DNS Servers* field: `10.11.12.13 <> default` - This forces all DNS requests to use `10.11.12.13` You can combine the *default* domain with specific domains: `10.11.12.13 <> default10.11.12.113 <> bar.foo.com` - `10.11.12.113` is used for DNS requests ending in `bar.foo.com` and `10.11.12.13` for all other DNS requests. --- ## Within IdP configuration (deprecated method) > [!NOTE] > NOTE > > To migrate your settings from your identity provider (IdP) configuration, see the [Migrating DNS settings](/v1/docs/migrating-dns-settings-v7-0) section. Configuring DNS within the IdP lets you configure DNS differently for different user groups (tenants) within one system. See [Configuring identity providers](/v1/docs/configuring-identity-providers-v7-0) to add a DNS configuration. Whether you need this special syntax depends on the native behavior of the device operating systems and your requirements. - **Portal clients** do not use this syntax. Configure DNS for Portal clients with a DNS policy. A default domain is optional. For more information, see [Default domain syntax](/v1/docs/device-dns-configuration-v7-0#default-domain-syntax1). - *DNS Domains* can be specified in any order. The DNS domain syntax follows the format: `dns.server.<IP address>.<domain>.<action>`, with the `<action>` being optional. ### All operating systems To improve affinity, use the special syntax to link a specific DNS server IP address to a DNS domain: `dns.server.10.11.12.13.foo.com` - This setting uses `10.11.12.13` but only for DNS requests ending in `foo.com`. It is possible to specify multiple domains using the special syntax, in which case the most specific domain always has the highest priority: `dns.server.10.11.12.13.foo.comdns.server.10.11.12.113.bar.foo.com` - This setting uses `10.11.12.113` for DNS requests ending in `bar.foo.com` and `10.11.12.13` for DNS requests ending in `notbar.foo.com`. ### Windows and Linux Because AppGate ZTNA has the highest priority, the *DNS Servers* setting resolves all DNS requests not specified in *DNS Domains*. ### macOS macOS has native affinity, but the *DNS Servers* setting can be used in conjunction with additional *DNS Domains* that use the special syntax: `foo.comdns.server.10.11.12.113.bar.foo.com` - This setting uses `10.11.12.113` for DNS requests ending in `bar.foo.com` and the specified *DNS Server* for DNS requests ending in `notbar.foo.com`. The system DNS resolves all DNS requests not specified in *DNS Domains*. You may also want to override the system DNS and route all DNS requests through AppGate ZTNA, for example to a secure internal DNS server. To do this, add the option to the end of the special syntax. When is set to *default*, the specified IP address is used as the default DNS server: `dns.server.10.11.12.13.default` - This forces all DNS requests to use `10.11.12.13`. You can also combine this special syntax with the normal format macOS uses, such as: `dns.server.10.11.12.13.defaultbar.foo.com` - The *DNS server* configuration is used for DNS requests ending in `bar.foo.com` and `10.11.12.13` for all other DNS requests. #### **Improving lookup times** To improve lookup times, add the option to the end of the special syntax. When is set to *nxdomain*, the driver returns NXDOMAIN immediately: `dns.server.1.2.3.4.foobar.com.nxdomain` - This setting means the driver never sends the DNS request to `1.2.3.4` for `foobar.com` and instead returns `NXDOMAIN`. > [!NOTE] > **NOTE** > > The fact that the request is never sent means the could be fake or real. The special syntax directs Windows to use lower-priority DNS servers for `foobar.com` requests instead of querying the *DNS Server* configured in AppGate ZTNA. The can be left out of the special syntax: `dns.server.1.2.3.4.nxdomain` - This setting means the driver returns `NXDOMAIN` for all domains (which is not very useful on its own). This option can be combined with the syntax explained earlier: `dns.server.10.11.12.13.foo.comdns.server.10.11.12.113.bar.foo.comdns.server.1.2.3.4.nxdomain` - This setting makes the driver immediately return `NXDOMAIN` for all domains not already matched by `foo.com` or `bar.foo.com`. This special syntax directs Windows to use lower-priority DNS servers for all unspecified requests, reducing wait times.