IP/hostnames

Prev Next

When you create an action in an entitlement, you can define the host using an IP address (or subnet) or a hostname.


Using IP addresses

IP addresses can be entered directly.

Supported formats

Host definition

Use for

1.0.0.26

Single entries

1.0.0.26, 1.0.0.30

Multiple entries

1.0.0.0/28

Subnets

1.0.0.0/28, 1.0.0.128/28

Multiple subnets


Hostnames (DNS)

You can use hostnames with an optional prefix that controls how AppGate resolves the name. Gateways resolve hostnames using the DNS servers configured for the Site. Use fully qualified domain names (FQDNs). Do not use short names.

Client DNS is set in the following order:

NOTE

If the client gets DNS from the resolver or identity provider, create an entitlement that allows access to the required DNS servers.

AppGate resolves hostnames using either the DNS resolver or the DNS forwarder, depending on the prefix used.

With the DNS forwarder, different hostnames that resolve to the same IP addresses (for example, shared hosting or CDNs) are treated as the same destination. In this case, dnsfwd:// glob entitlements cannot separate access by hostname, because access is enforced by resolved IPs — not by hostname.

Supported syntax

Host definition

Resolved by

Result

myserver1.my_co.com

DNS Resolver

Resolves to the IP addresses of myserver1.my_co.com

myserver1.my_co.com,
myserver2.my_co.com

DNS Resolver

Resolves the IP addresses of myserver1.my_co.com and
myserver2.my_co.com

dns://myserver1.my_co.com

DNS Resolver

Resolves to the IP addresses of myserver1.my_co.com

dns://myserver1.my_co.com,
dns://myserver2.my_co.com

DNS Resolver

Resolves the IP addresses of myserver1.my_co.com and
myserver2.my_co.com

http://myserver1.my_co.com

DNS Resolver

Resolves to the IP addresses of myserver1.my_co.com - see URL access below

https://myserver1.my_co.com

DNS Resolver

Resolves to the IP addresses of myserver1.my_co.com - see URL access below

dnsfwd://myserver1.my_co.com

DNS Forwarder

Resolves explicitly to myserver1.my_co.com.

dnsfwd://*.my_co.com

DNS Forwarder

Resolves only to hosts matching the glob exactly — does not also match my_co.com itself.

*.my_co.com

Deprecated: Glob patterns are no longer accepted in new dns:// entries or bare hostname entries; existing configured entitlements continue to function unchanged.

DNS Forwarder

Resolves the IP addresses of myserver1.my_co.com,
myserver2.my_co.com, myserver3.my_co.com, and so on.

dns://*.my_co1.com

Deprecated: Glob patterns are no longer accepted in new dns:// entries or bare hostname entries; existing configured entitlements continue to function unchanged.

DNS Forwarder

Resolves the IP addresses of myserver1.my_co1.com,
myserver1.my_co2.com, myserver2.my_co2.com, and so on.

NOTE

Use dnsfwd:// for hostname or glob matches through the DNS Forwarder, and dns:// for single-host entries resolved through the DNS Resolver. As of 7.0, dns:// no longer accepts glob patterns in new entries — existing dns://<glob> entries keep working. Glob patterns still carry a security risk: they resolve, and grant access to, every subnet or host in the matched domain.

When you configure access to a SaaS provider, DNS synchronization issues can occur if you use the DNS resolver. To avoid this, the DNS forwarder.