RegistrarDNS hostingCapabilities verified
easyDNS
Migrate DNS zones to or from easyDNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at easyDNS. Free and read-only.
Access we need
- Credentials
- REST API token and API key (HTTP Basic)
- Permissions
- easyDNS API credentials can't be scoped to read-only or to single domains; they act for the whole easyDNS user. Request a dedicated API token and key for DNSMigrator so you can revoke it independently.
What easyDNS 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
- 300s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- ALIAS
- NAPTR
- SPF
- SSHFP
- TLSA
- CERT
Good to know
- API access has to be requested from easyDNS, and new keys start on the sandbox until easyDNS certifies them for the live API.
- easyDNS limits the API to one request per second and 500 requests per day by default; large zones can exhaust the daily quota, so ask easyDNS for a higher limit before big migrations.
- Add the domain to your easyDNS account before migrating; adding domains through the API creates an invoice, so zones aren't created through this connection.
- URL, HTTPS and stealth forwarders, dynamic and geo-targeted records are left untouched because the API doesn't document their format.
- Apex NS and SOA records are managed by easyDNS and can't be changed.
- TTLs below 300 seconds and MX preferences above 100 are rejected by easyDNS.
- DNSSEC is managed in the easyDNS control panel.