--- title: "Resolution of host definitions in entitlements" slug: "resolution-of-host-definitions-in-entitlements-v7-0" description: "Explore how AppGate ZTNA's DNS resolver and forwarder ensure reliable access to hosts and SaaS providers, adapting to dynamic IP changes effectively." tags: ["DNS Resolution", "DNS Forwarding", "DNS Resolver", "Entitlements"] updated: 2026-11-02T15:51:09Z published: 2026-11-02T15:51:09Z canonical: "support.appgate.com/resolution-of-host-definitions-in-entitlements-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. # Resolution of host definitions in entitlements The concept of a resolver in AppGate ZTNA is a loose term covering the mechanisms used by the system to resolve a range of host definitions. These mechanisms are invoked according to the syntax used to define the hosts in the entitlement action. The remainder of this topic covers hosts defined using `dns://myserver1.myco.com` which will always use the [DNS resolver](/v1/docs/resolution-of-host-definitions-in-entitlements-v7-0#dns-resolver), and `dnsfwd://myserver1.myco.com` which will always use the [DNS forwarder](/v1/docs/resolution-of-host-definitions-in-entitlements-v7-0#dns-forwarder). In both cases, the appliance's hosts file is checked first, if enabled in Sites, before any external DNS requests are made. The DNS resolver works in parallel with the Device DNS used by the client; the DNS forwarder effectively works in series, providing answers to any device DNS requests. --- ## Fast-changing IP addresses AppGate ZTNA responds to changes in resolved names, such as when an autoscaled instance is added. It is not designed to handle large numbers of frequently changing resolved names. Gateways run a dynamic queuing system to handle such changes on a per-user basis. For example, if the system has 500 users and all have 20 actions that change, the queue immediately grows to 10,000 entries. Larger, faster Gateways handle bigger queues more quickly, but you must still ensure that host definitions resolve to consistent values appropriate for your use case. The DNS resolver includes a built-in warning mechanism that triggers when the AppGate ZTNA system receives inconsistent DNS values. Once there are more than 10 results, the system divides the number of changes over a given time frame by the number of results to produce an instability score. When the score exceeds a certain threshold, a warning appears in the dashboard. ![Warning message indicating unstable DNS names for github.com and www.google.se.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag55-change_warning.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A40%3A07Z&se=2026-11-21T22%3A40%3A07Z&sr=b&sp=r&sig=DsdGDZ%2FRP3tZjTxpNC0k4G%2BhlkAjv5n7dpUwvZ6hbnU%3D) --- ## Accessing SaaS providers To control access to SaaS providers using AppGate ZTNA, use the DNS forwarder. Most SaaS providers use global DNS load balancing to answer DNS requests, and the DNS responses can list many IP addresses (for example, [https://ip-ranges.amazonaws.com/ip-ranges.json](https://ip-ranges.amazonaws.com/ip-ranges.json)) that can change frequently. Each time the DNS record expires (typical TTL between one and five minutes), the Gateway retrieves the new list and updates the firewall rules and client routes if there have been changes. This can lead to two problems: - If a DNS resolver is used (even to the same DNS server the Gateway uses), DNS may be queried at different times by the client and the DNS resolver, so each can end up with a different set of results. - The client may use a local ISP's DNS server (because this is a public URL). If that ISP is in a different region from the Gateways, the client may receive a different set of results. The user's device DNS and Gateway DNS must remain in sync for reliable operation. Use the DNS forwarder in this case. --- ## DNS resolver The user's device and Gateway operate independently in different network environments, and each makes DNS requests independently. ### At sign-in - The client uses the user's DNS policy to set the device's DNS (based on *Match Domains* and internal *DNS Servers*). - When no DNS policy is specified, the IdP's DNS settings are used. - The DNS resolver used by the Gateways is specified in the Site configuration. - The user's access policy defines the entitlements allowed, which include all host definitions. The Gateway uses the Go name daemon to resolve these hostnames based on *Match Domains* and *DNS Servers*. The results are obtained from the hosts file, Go name daemon's DNS cache, or a fresh DNS request. - Thereafter, this is refreshed at the *Update Interval* for the Site (default 60 seconds). - The Go name daemon updates the session daemon. - The session daemon updates the VPN daemon for firewall rules. - The session daemon sends the client the required routes. - The client writes host routes to the device. ### At use time - The user accesses an application, triggering a DNS request. - The client captures the DNS request (based on match domain) and routes this through the appropriate Gateway to the DNS server. - The Gateway sends the DNS response to the user's application. - Application traffic is routed through the client’s tunnels through the appropriate Gateway to the protected host. The two DNS request cycles trigger at different times and may use different TTLs. Initially, the Gateway looks up the allowed protected hosts defined in entitlements; later, the device looks up the specific protected host the user is accessing. Even when both use the same DNS server, short TTLs on resolved IP addresses can cause inconsistencies. Use this model with relatively static DNS records. See [Configuring Sites](/v1/docs/configuring-sites-v7-0#dns-resolving) to set up a DNS resolver. --- ## DNS forwarder The DNS forwarder supports hostname resolution (`dnsfwd://crm.internal.my_company.com`) as well as subdomain resolution (`dnsfwd://internal.my_company.com`). Although the client and Gateway remain independent, the Gateway handles DNS requests on behalf of the client. ### At sign-in - The client uses the user's DNS policy configuration based on *Match Domains* and *DNS Servers* to set the device's DNS to point towards the DNS forwarder's CoreDNS instance. - Site settings define that DNS forwarding should be used on the Gateways. Both *Match Domains* and *DNS Servers* can be specified for one or more internal DNS servers. ### At use time - The user triggers a DNS request. - The client captures the DNS request (based on match domain) and routes this to the Gateway's DNS forwarder on `100.127.x.y`. - The Gateway uses the DNS forwarder to resolve hostnames based on *Match Domains* and *DNS Servers*. The results are obtained from the hosts file, the DNS cache, or a fresh DNS request. - This is repeated for each user request. - If the DNS result includes a TTL, the forwarder honors it and caches the result for that duration. - If the DNS result does not include a TTL, then the *Default TTL for DNS lookups* for the Site is used (default 300 seconds). - The DNS forwarder updates Sessiond. - The session daemon verifies that the entitlements are allowed. - Sessiond updates VPNd for firewall rules. - Sessiond sends the client the required routes. - The DNS forwarder sends the DNS response to the user's application. - Application traffic is routed through the client's tunnels to the protected host through the appropriate Gateway firewall rule. Client DNS auto-configuration sets DNS in two places in the AppGate ZTNA system: once for the user's device and again for the Gateway. Rather than operating in parallel, these configurations work in series, so DNS behavior is unified. Every DNS request sent through the client triggers the DNS forwarder, which provides a single response shared between the requesting application and the Gateway's firewall engine. See [Configuring Sites](/v1/docs/configuring-sites-v7-0#dns-forwarding) to set up a DNS forwarder.