AppGate ZTNA admins set access rules by defining entitlements, which include actions. Within an action, you define hosts using IP addresses, subnets, hostnames, URLs, resource names (cloud resolvers), and host entitlement scripts. Resource names and entitlement scripts support the dynamic least privilege access mode, which is a key part of the product. These extend the capabilities of the system, allowing it to adapt in near-real time to changes in the infrastructure.
Name resolvers provide support for various cloud resolvers (azure://vnet:<NAME>) as well as hostname resolution (idns://crm.internal.my_company.com).
Sites include numerous name resolution options for deriving IP addresses from host definitions.
DNS in AppGate ZTNA
Appliances
Appliances need access to DNS servers to find other servers, such as Gateways looking for Controllers or Controllers looking for LDAP. This is configured when creating a new appliance in the System Settings tab. AppGate ZTNA appliances are also DNS servers in their own right as they run the Go-based CoreDNS. The appliance setting configures a CoreDNS virtual server, which the appliance then uses as a proxy for host resolution.
Gateways
Gateways need access to DNS servers to resolve all the users' entitlements. This is set up by configuring a DNS resolver for the Site where the DNS servers are located. Just like the appliance, this will use one or more CoreDNS virtual servers. Effectively you are setting up two things: the resolver which will speak to a CoreDNS instance, and the CoreDNS instance which will use the same internal DNS servers as the appliances on that Site.
To allow a Gateway to resolve all the users' entitlements, a limited default DNS resolver is included which uses the Gateway appliance's DNS server settings. This handles all hostnames without matching domains from other DNS resolvers.
There is an option for Zone transfers (to Gateway) when configuring a new DNS resolver. Zone transfers are a standard DNS feature in which a DNS server delegates part of its workload to another that is better placed to service requests for that zone. In the case of the DNS resolver, the Match Domains defined are also used to set zones for CoreDNS. Zone transfers are useful in this case as Gateways can make a lot of DNS requests, and these will effectively be resolved internally on the Gateway.
If the DNS server does not respond when CoreDNS is starting, CoreDNS retries the zone transfer request every 10 seconds until it succeeds. After a successful transfer, the start of authority (SOA) record from the DNS server sets the refresh interval (typically 12–24 hours). If a zone transfer subsequently fails, CoreDNS continues to serve DNS requests from its cache. This improves reliability when there are network issues or when the DNS server is temporarily unavailable.
The DNS resolver also includes an option to enable or disable AAAA lookups. If you do not need AAAA lookups, disable them. The DNS forwarder has no equivalent option because it responds directly to client requests. To suppress AAAA lookups when using the DNS forwarder, configure your devices and apps to stop requesting them.
Portal
Portal users face a specific challenge with DNS server access for resolving entitlements. User A might need access to a different DNS server from user B because they have a different DNS policy. For this reason, the Portal appliance also uses CoreDNS virtual servers to ensure that users' DNS requests are forwarded to the appropriate DNS servers regardless of the appliance’s DNS server settings. The way the Portal operates adds some additional DNS requirements of its own.
Using name resolvers
Depending on how you define your hosts, you may use different host definitions for each Site. If you are targeting cloud-based protected hosts, consider using cloud-based resource names, which return IP addresses directly without the need for DNS. Whether you are resolving static internal hostnames or the dynamic public IPs used by a SaaS provider, AppGate ZTNA offers multiple options. See IP/hostnames for more information.
Ensure that the client DNS settings on the user's device are ready for when the user attempts to access a protected host. This uses the same internal DNS server as the Site DNS resolver. To configure this automatically, select the Enable auto-configuration checkbox when you configure the Site's DNS resolver.