Cloud platformDNS hostingRegistrarCapabilities verified
Amazon Route 53
Migrate DNS to or from Amazon Route 53, and switch nameservers at Amazon Route 53 as a registrar.
See how a domain's records would land at Route 53. Free and read-only.
Access we need
- Credentials
- Cross-account IAM role with an external ID
- Permissions
- route53:ListHostedZones, GetHostedZone, ListResourceRecordSets for the preview; ChangeResourceRecordSets and CreateHostedZone to apply.
What Route 53 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
- weighted, latency, geo, failover, multivalue, geoproximity, ip
- Minimum TTL
- 0s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- DS
- HTTPS
- SVCB
- TLSA
- SSHFP
- NAPTR
- SPF
Good to know
- Alias records can only target AWS resources or records in the same hosted zone.
- Weighted, latency, geolocation and failover routing are Route 53 features. Most other providers can't reproduce them.
- Apex CNAMEs are not allowed. Use an alias record instead.