DNS Configuration
View as MarkdownThe exact A, CNAME, and TXT records to add for a custom domain.
When you add a custom domain, Atlasflow shows the DNS records you need to create at your DNS provider. This page explains what each record does.
Apex domains
For an apex (root) domain like example.com, add A records pointing to Atlasflow's proxy IP addresses:
example.com A <atlasflow-proxy-ip>The dashboard lists the exact IP addresses for your domain. Add one A record per IP shown.
Subdomains
For a subdomain like app.example.com, add a CNAME record pointing to Atlasflow's fallback origin:
app.example.com CNAME <atlasflow-fallback-origin>The dashboard shows the exact CNAME target for your project.
Ownership verification
Before routing traffic, Atlasflow verifies you control the domain. Add the TXT record shown in the domain setup dialog:
_acme-challenge.example.com TXT <verification-token>This record also enables automatic TLS certificate issuance.
Record summary
| Domain type | Routing record | Ownership record |
|---|---|---|
Apex (example.com) | A → proxy IPs | TXT → verification token |
Subdomain (app.example.com) | CNAME → fallback origin | TXT → verification token |
Propagation
DNS changes can take from a few minutes to a few hours to propagate, depending on your provider and the record's TTL. Atlasflow polls automatically and updates the domain status once the records resolve.
Next steps
- Custom domains: the full setup flow.
- Redirects: redirect
wwwto your apex. - Troubleshooting: domains stuck on verifying.