Skip to content
DNSmigrator
betaDNS betaRegistrar betaDNS hostingSetup guide checked 2026-09-27

ClouDNS

ClouDNS API credentials setup: create a paid-plan API sub-user for scoped DNS access, or a main API user when the connection must also change registered-domain nameservers and DS records.

On this page

ClouDNS API credentials permissions

Credential type
API user ID or sub-user and password
Preview access
API sub-user → Read
Apply access
API sub-user → Read and Write
API endpoint
DNSMigrator uses the provider's fixed API endpoint.

Additional access

A main API user is read/write across the account. Prefer a delegated sub-user for DNS-only connections; use a main API user for registrar cutover because ClouDNS does not document registered-domain delegation to API sub-users.

DNSControl id

creds.json TYPE
{
  "TYPE": "CLOUDNS"
}

Create credentials

Create a paid-plan API sub-user for scoped DNS access, or a main API user when the connection must also change registered-domain nameservers and DS records.

Access you'll grant

Preview

API sub-user → Read

Apply

API sub-user → Read and Write

A main API user is read/write across the account. Prefer a delegated sub-user for DNS-only connections; use a main API user for registrar cutover because ClouDNS does not document registered-domain delegation to API sub-users.

Before you start

  • A paid ClouDNS plan; Free DNS does not include HTTP API access.
  • Access to API & Resellers and the DNS zones or registered domains you want to connect.

Setup steps

0 of 6 done

  1. Open API & Resellers

    Sign in to ClouDNS and open API & Resellers. For DNS-only access, find API Sub-Users and select Add new sub-user.

    ClouDNS API access and authentication

  2. Configure the DNS sub-user

    Set a username and password, choose limits large enough for the delegated zones and records, and set access to Read for preview or Read and Write for apply. In the IP field, enter our egress IP so only DNSMigrator can use it.

    Preview accessRead
    Apply accessRead and Write
    Whitelisted IPour egress IP

  3. Delegate the DNS zones

    Delegate every DNS zone this connection needs to the sub-user. A sub-user can authenticate successfully while still returning no zones if none were delegated.

    ClouDNS: delegate a zone to a sub-user

  4. Use a main API user for registrar cutover

    If DNSMigrator must change nameservers or DS records for domains registered at ClouDNS, use API Users → Add new user instead. Set its IP address to our egress IP, choose a password, save it, and copy the generated auth ID.

  5. Match the API user type

    Choose API user (auth-id) for the main numeric ID, API sub-user (sub-auth-id) for a numeric sub-user ID, or API sub-user by name (sub-auth-user) for its username.

    Main API userauth-id
    Numeric sub-usersub-auth-id
    Named sub-usersub-auth-user

  6. Paste the ID and password

    Enter the numeric ID or sub-user name in Auth ID or sub-user name, enter the password you set in API password, then check access.

Troubleshooting

Invalid authentication

Match API user type to the identifier: numeric main ID uses auth-id, numeric sub-user ID uses sub-auth-id, and a username uses sub-auth-user. Then re-enter the matching password.

The source IP is not allowed

Set the API user's IP field to our egress IP. If you entered another address when creating it, update the user or create a replacement.

The sub-user sees no zones

Delegate each DNS zone to the sub-user and make sure its zone and record limits are not exhausted.

Registrar domains are unavailable

Use a main API user with auth-id. ClouDNS documents DNS-zone delegation to sub-users, but not delegation of registered-domain management.

Official documentation

Guide checked against the official documentation on .

Credential fields

FieldRequirementWhere to find it
API user typeauthTypeRequiredSelect auth-id for a main API user, sub-auth-id for a numeric API sub-user ID, or sub-auth-user for an API sub-user username.
Auth ID or sub-user nameauthIdRequiredThe generated numeric auth ID/sub-auth ID shown in the users table, or the exact sub-auth-user username when that type is selected.
API passwordpasswordRequiredThe password you set when creating the API user or sub-user; ClouDNS does not generate it.

Capabilities

Create zones
Yes
List zones
Yes
DNSSEC
Managed through the API
Minimum TTL
60 seconds
Apex CNAME
No
Read only
No

Record types

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • NS
  • SRV
  • CAA
  • PTR
  • ALIAS
  • DNAME
  • TLSA
  • SSHFP
  • DS
  • NAPTR
  • SPF

ClouDNS-only types

  • CLOUDNS_WR

These records need translation or review when you move to another provider.

Caveats

  • 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.

Troubleshooting

Invalid authentication
Match API user type to the identifier: numeric main ID uses auth-id, numeric sub-user ID uses sub-auth-id, and a username uses sub-auth-user. Then re-enter the matching password.
The source IP is not allowed
Set the API user's IP field to {egressIp}. If you entered another address when creating it, update the user or create a replacement.
The sub-user sees no zones
Delegate each DNS zone to the sub-user and make sure its zone and record limits are not exhausted.
Registrar domains are unavailable
Use a main API user with auth-id. ClouDNS documents DNS-zone delegation to sub-users, but not delegation of registered-domain management.

Related links

ClouDNS migration overviewMarketing overview and provider differences.Connect a providerHow connection checks and permissions work.Cloudflare → ClouDNSRoute 53 → ClouDNSAzure DNS → ClouDNSCloud DNS → ClouDNS