CDN and edgeDNS hostingCapabilities verified
Netlify DNS
Migrate DNS zones to or from Netlify DNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Netlify. Free and read-only.
Access we need
- Credentials
- Personal access token
- Permissions
- A personal access token has full access to your teams. Netlify tokens can't be read-only.
What Netlify supports
The same data the translation engine uses when it plans a migration.
- Create zones through the API
- List zones through the API
- Turn on DNSSEC through the API
- Apex CNAME (flattening)
- Apex ALIAS record
- Aliases to cloud resources
- CDN proxy on records
- Routing policies
- Minimum TTL
- 60s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- ALIAS
- SPF
Good to know
- NETLIFY and NETLIFYv6 site records are read as an ALIAS (apex) or CNAME to the site's netlify.app hostname, and we never change or delete them on Netlify.
- Netlify DNS doesn't support DNSSEC, so turn it off at the registrar before switching nameservers.
- Netlify has no record update endpoint, so each change is a delete followed by a create.