DNS hostingDNS hostingRegistrarCapabilities verified
ClouDNS
Migrate DNS to or from ClouDNS, and switch nameservers at ClouDNS as a registrar.
See how a domain's records would land at ClouDNS. Free and read-only.
Access we need
- Credentials
- API user auth ID (or sub-user ID/name) + password
- Permissions
- A read-only API sub-user with the zones delegated is enough for the preview; applying needs a read-and-write sub-user or a main API user.
What ClouDNS 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
- geo
- Minimum TTL
- 60s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- ALIAS
- DNAME
- TLSA
- SSHFP
- DS
- NAPTR
- SPF
ClouDNS-only records
- CLOUDNS_WR
These have no equivalent elsewhere and are flagged in every preview.
Good to know
- TTLs must be one of ClouDNS's fixed values (60, 300, 900, 1800, 3600, 21600 … 2592000); other TTLs are rounded up.
- Web redirects (CLOUDNS_WR) are ClouDNS-only and are written as plain 301 redirects without frame options.
- The API is rate limited to about 20 requests per second per IP, so large zones apply record by record and take a while.