CDN and edgeDNS hostingCapabilities verified
EdgeCenter DNS
Migrate DNS zones to or from EdgeCenter DNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at EdgeCenter. Free and read-only.
Access we need
- Credentials
- Permanent API token
- Permissions
- A permanent API token with the Users role is enough to read zones as a migration source. Writing records needs the Engineers role; Administrators is never required.
What EdgeCenter 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
- DNAME
Good to know
- Record sets that use GeoDNS, weighted balancing or DNS Failover filters, answer metadata or disabled answers are copied as plain answers and never changed by us.
- The API allows about 4 requests per second, so large zones are written one record set at a time.
- The minimum TTL depends on your EdgeCenter plan (usually 60 seconds); lower values are rejected by EdgeCenter.
- ALIAS, PTR, HTTPS and SVCB records aren't available, and a CNAME can't sit at the zone apex.