Skip to main content
Browse documentation

App addresses and DNS basics

Your app’s displayed URL is the address to open in a browser. A hostname such as blog.example.com is different from a server’s IP address and from an SFTP host and port.

Use the panel’s instructions​

RecordPurpose
CNAMEPoints one hostname to another hostname
APoints a hostname to an IPv4 address
AAAAPoints a hostname to an IPv6 address
TXTCarries text used for verification and other domain settings

Do not mix instructions from protected Cloud Apps, dedicated-IP apps and BYOH tunnels. Their DNS targets can differ. Public test IPs on the network page are not DNS targets for your application.

Root domain versus subdomain​

example.com is the root; blog.example.com and www.example.com are separate hostnames. A root domain may require your DNS provider’s ALIAS, ANAME or CNAME-flattening feature. Setting one hostname does not automatically configure the others.

Before changing DNS​

Record the current values, identify which provider hosts the authoritative DNS zone, and change only records relevant to the app. Leave unrelated mail and verification records alone.

Follow Connect a custom domain, then check both DNS and certificate status. DNS resolution alone is not proof HTTPS or the application’s own URL configuration is ready.