DNS hostingDNS hostingCapabilities verified
NexDNS
Migrate DNS zones to or from NexDNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at NexDNS. Free and read-only.
Access we need
- Credentials
- API key (Bearer, nxd_ prefix)
- Permissions
- zones.read and records.read for the preview; add records.write to apply and zones.write to create zones or switch DNSSEC. API access needs a Pro plan or higher.
What NexDNS 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
- 0s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- ALIAS
- DNAME
- DS
- TLSA
Good to know
- The SOA record and the apex NS records are managed by NexDNS and can't be changed, so dual-hosting a zone with a second provider isn't possible.
- Records are written one value per request against a per-account rate limit, so large zones take a while to apply.
- Only A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR, ALIAS, DNAME, DS and TLSA are supported; ALIAS is the way to point the apex at a hostname.