Cloud

DNS zones and records

Manage zones, validate records and understand TTL and propagation in whycloud.

Public and private zones

Choose public or internal DNS. Public zones require ownership verification. Internal zones resolve only where the private service is available.

Records

Validate A/AAAA and CNAME destinations. Avoid unintended CNAME loops and inadvertently exposing private IP addresses in public records.

TTL and propagation

Lower TTLs help new lookups see changes sooner, but previously cached entries can survive for their original TTL. Propagation is not instant.

PaaS integration

Public PaaS endpoints need a valid exposed port and public address. DNS linking follows domain verification and network prerequisites.

Related guides