DNS hostingDNS hostingCapabilities verified
Netnod Primary DNS
Migrate DNS zones to or from Netnod Primary DNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Netnod. Free and read-only.
Access we need
- Credentials
- API token (Authorization: Token)
- Permissions
- A Primary DNS API token for the account. Netnod tokens are not split into read and write scopes, so the same token is used for preview and apply.
What Netnod 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
- ALIAS
- PTR
- DS
- HTTPS
- SVCB
- NAPTR
- SSHFP
- TLSA
Good to know
- Netnod publishes no public API reference; the adapter follows Netnod's official Go client, and TTL limits are not documented.
- Each change replaces a whole name+type set, so records disabled in the Netnod portal are dropped when that set is edited.
- New zones get Netnod's default nameservers; zone transfer keys and NOTIFY targets must be set up with Netnod separately.