DNS hostingDNS hostingCapabilities verified
NextDNS rewrites
Migrate DNS zones to or from NextDNS rewrites: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at NextDNS. Free and read-only.
Access we need
- Credentials
- API key + profile ID
- Permissions
- The account API key (X-Api-Key). NextDNS keys cannot be scoped or made read-only, so the same key is used for preview and apply.
What NextDNS 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
Good to know
- NextDNS is a filtering resolver, not an authoritative DNS host: only the profile's rewrites are managed, and they answer only for devices that use that profile.
- Rewrites map a name to an IP address (A/AAAA) or another name (CNAME); MX, TXT, SRV, CAA and all other types cannot be migrated, and rewrites have no TTL setting.
- Zones are grouped from rewrite names (a rewrite for example.com also covers www.example.com rewrites); there are no nameservers to delegate to.