NextDNS rewrites
NextDNS API key setup: copy the NextDNS account API key and the ID of the profile whose rewrites DNSMigrator should manage.
On this page
NextDNS API key permissions
- Credential type
- Account API key and profile ID
- Preview access
- Account API key (full profile access)
- Apply access
- Account API key (full profile access)
- API endpoint
- DNSMigrator uses the provider's fixed API endpoint.
Additional access
DNSControl id
This provider does not have a DNSControl id.
Create credentials
Copy the NextDNS account API key and the ID of the profile whose rewrites DNSMigrator should manage.
Access you'll grant
Account API key (full profile access)
Account API key (full profile access)
Before you start
- A NextDNS account with an existing profile.
- At least one rewrite in the profile if you want it to appear as an importable zone.
- NextDNS is a filtering resolver, not authoritative DNS; this connection manages profile rewrites only.
Setup steps
0 of 4 done
Copy the account API key
Sign in at my.nextdns.io, open Account, scroll to the bottom, and copy the API key.
Open the rewrite profile
Open the NextDNS profile that contains the Rewrites you want to import or change. Do not use a key or profile from nexdns.tech; NexDNS is a different authoritative DNS provider.
Copy the Profile ID
Copy the profile identifier from the URL. For
my.nextdns.io/abc123/setup, the Profile ID isabc123.Example Profile IDabc123Paste both values
Paste the account value into API key and the URL identifier into Profile ID, then check access.
Troubleshooting
NextDNS rejected the API key
Copy the current key again from the bottom of the Account page. Do not paste a profile ID or a NexDNS nxd_ key into this field.
The profile was not found
Confirm the Profile ID comes from a profile owned by the same account as the API key and contains only the URL identifier.
No importable zones appear
This connection groups existing profile rewrites into zones. Add at least one rewrite to the selected profile, then check access again.
MX, TXT, SRV, or other records are missing
NextDNS rewrites represent only A, AAAA, or CNAME-style answers and have no authoritative TTL. Use an authoritative DNS provider connection for full zones.
Official documentation
Guide checked against the official documentation on .
Credential fields
| Field | Requirement | Where to find it |
|---|---|---|
| API keyapiKey | Required | The account API key shown at the bottom of https://my.nextdns.io/account. |
| Profile IDprofileId | Required | The identifier in the selected profile URL, for example abc123 in my.nextdns.io/abc123/setup. |
Capabilities
- Create zones
- No
- List zones
- Yes
- DNSSEC
- Not available through this connection
- Minimum TTL
- 300 seconds
- Apex CNAME
- Supported through flattening
- Read only
- No
Record types
- A
- AAAA
- CNAME
Caveats
- 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.
Troubleshooting
- NextDNS rejected the API key
- Copy the current key again from the bottom of the Account page. Do not paste a profile ID or a NexDNS nxd_ key into this field.
- The profile was not found
- Confirm the Profile ID comes from a profile owned by the same account as the API key and contains only the URL identifier.
- No importable zones appear
- This connection groups existing profile rewrites into zones. Add at least one rewrite to the selected profile, then check access again.
- MX, TXT, SRV, or other records are missing
- NextDNS rewrites represent only A, AAAA, or CNAME-style answers and have no authoritative TTL. Use an authoritative DNS provider connection for full zones.