Loading…
Loading documentation...
Configure DNS A, AAAA and CNAME records in Cloud DNS or an external registrar and automate TLS certificate issuance and renewal.
Commands checked on 2026-11-12 with SAU Cloud DNS, Caddy 2.8, Let's Encrypt ACME v2, sau CLI 0.2.0.
Your custom apex domain (example.com) and subdomains (app.example.com, api.example.com) will resolve through authoritative DNS with optional DNSSEC signing, route traffic to your Servers Are Up Linux VPS, container stack, or Network > API gateway & edge WAF (/dashboard/api-gateway), and renew TLS 1.3 HTTPS certificates automatically at least 30 days before expiration.
203.0.113.25 on Compute > Servers at /dashboard/instances) or an Edge Gateway hostname on Network > API gateway & edge WAF (/dashboard/api-gateway).dig or nslookup and curl on your workstation to verify propagation and TLS handshakes.You can host authoritative DNS directly inside Network > Cloud DNS zones (/dashboard/cloud-dns)—with one-click DNSSEC signing and BIND zone export—or keep your existing DNS provider:
# Create an authoritative public zone with DNSSEC via the sau CLI
sau network dns-create example.com --dnssec
# Inspect your zone and assigned nameservers
sau network dns-list --zone example.com -o table
If you host the zone in Network > Cloud DNS zones (/dashboard/cloud-dns), update your domain registrar's nameserver (NS) delegation to match the authoritative nameservers displayed in the zone header. If you keep your registrar's DNS, simply add the records in Step 2 there.
A, CNAME, and CAA DNS recordsCreate explicit records with a short 300-second TTL during initial cutover so typos can be corrected in five minutes:
| Name | Type | Value | TTL | Purpose |
|---|---|---|---|---|
@ |
A |
203.0.113.25 |
300 |
Routes apex example.com to your server's public IPv4 |
www |
CNAME |
example.com. |
300 |
Aliases www.example.com to the apex |
app |
A |
203.0.113.25 |
300 |
Routes app.example.com to your web server |
@ |
CAA |
0 issue "letsencrypt.org" |
3600 |
Restricts certificate issuance to Let's Encrypt |
Verify DNS resolution against a public recursive resolver (1.1.1.1 or 8.8.8.8) before starting ACME certificate issuance so you do not trigger Let's Encrypt validation rate limits:
dig @1.1.1.1 +short A app.example.com
dig @1.1.1.1 +short CAA example.com
80 and 443 in your perimeter firewallLet's Encrypt's standard HTTP-01 challenge connects to TCP port 80 (/.well-known/acme-challenge/...), and TLS-ALPN-01 plus HTTPS visitors connect to TCP/UDP port 443.
Open Network > Firewall (/dashboard/network?tab=firewall) and confirm both 80/tcp and 443/tcp (plus 443/udp for HTTP/3 QUIC) are permitted inbound to your server. Keep your backend application port (3000, 8080, or 5432) bound to 127.0.0.1 so all external requests pass through TLS termination.
www to canonical apexOn a Linux VPS running Caddy, add both your apex redirect and your app proxy to /etc/caddy/Caddyfile and reload:
sudo tee /etc/caddy/Caddyfile > /dev/null <<'EOF'
www.example.com {
redir https://example.com{uri} permanent
}
example.com, app.example.com {
encode zstd gzip
header Strict-Transport-Security "max-age=31536000; includeSubDomains"
reverse_proxy 127.0.0.1:3000
}
EOF
sudo caddy validate --config /etc/caddy/Caddyfile
sudo systemctl reload caddy
If you prefer managed layer-7 rate limiting, subscription API keys, and OWASP WAF rules in front of your origin without managing reverse proxies on the VM, attach your domain on Network > API gateway & edge WAF (/dashboard/api-gateway) instead; see Route APIs with Edge WAF, rate limits and Cloud DNS.
Inspect the live X.509 certificate chain, issuer, SANs, and HTTP-to-HTTPS redirect from your terminal:
curl -fsSI http://app.example.com | grep -iE "^HTTP/|^location:"
echo | openssl s_client -servername app.example.com -connect app.example.com:443 2>/dev/null \
| openssl x509 -noout -subject -issuer -dates
http://app.example.com returns 308 Permanent Redirect to https://app.example.com/, and openssl x509 prints issuer=C = US, O = Let's Encrypt with a valid notAfter timestamp ~90 days out.
CAA record authorizes a different CA. Run dig +short CAA example.com. If CAA records exist and do not include letsencrypt.org, Let's Encrypt is required by RFC 8659 to refuse issuance until you add 0 issue "letsencrypt.org".ERR_TOO_MANY_REDIRECTS) when using an external proxy CDN. If you place an external CDN in front of Caddy in "Flexible SSL" mode, the CDN talks to Caddy over plain HTTP 80, causing Caddy to redirect back to HTTPS endlessly. Always set upstream TLS mode to Full (Strict) so end-to-end traffic is encrypted on 443.PRIVATE_VNET zone (sau network dns-create internal.example --private) in Network > Cloud DNS zones (/dashboard/cloud-dns) for east-west service discovery.300 seconds to 3600 seconds once cutover is verified so resolvers cache answers and absorb transient DNS blips./dashboard/saas) or your uptime monitor so a blocked port 80 never silently breaks renewal at day 60./dashboard/cloud-dns) into version control after major DNS changes.Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.