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

AutoDNS (InterNetX)

AutoDNS API credentials setup: create a dedicated AutoDNS user with the zone and domain ACLs needed to preview DNS, update records, and run registrar cutovers.

On this page

AutoDNS API credentials permissions

Credential type
API user credentials
Preview access
ZoneList, ZoneInfo, and DomainList/DomainInfo (0105)
Apply access
ZoneUpdate, optional ZoneCreate, DomainUpdate (0102), domain DNSSEC update (0102007), and JobInfo (300114)
API endpoint
DNSMigrator uses the provider's fixed API endpoint.

Additional access

Check access performs list requests; it does not make a test write, so a successful check does not prove that every apply ACL is present.

DNSControl id

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

Create credentials

Create a dedicated AutoDNS user with the zone and domain ACLs needed to preview DNS, update records, and run registrar cutovers.

Access you'll grant

Preview

ZoneList, ZoneInfo, and DomainList/DomainInfo (0105)

Apply

ZoneUpdate, optional ZoneCreate, DomainUpdate (0102), domain DNSSEC update (0102007), and JobInfo (300114)

Check access performs list requests; it does not make a test write, so a successful check does not prove that every apply ACL is present.

Before you start

  • An AutoDNS account whose administrator can create users and assign ACLs.
  • The original base32 shared secret if two-factor authentication is enabled for the API user.

Setup steps

0 of 6 done

  1. Open user management

    Sign in to AutoDNS and open User management. Create a separate API user instead of sharing an administrator login.

    Read AutoDNS API authentication

  2. Create a restricted API user

    Choose a recognizable username and a unique password. Limit the user to the zones and registered domains DNSMigrator should manage.

  3. Assign the API tasks

    For previews, allow the zone and domain list/info tasks. For apply and cutover, add the update tasks below; add ZoneCreate only if DNSMigrator should create missing zones.

    PreviewZoneList, ZoneInfo, DomainList/DomainInfo (0105)
    ApplyZoneUpdate, DomainUpdate (0102), DNSSEC update (0102007), JobInfo (300114)

  4. Record the context

    Use context 1 for an AutoDNS demo account. Live accounts use context 4 or their PersonalAutoDNS context number. Paste that number into Context.

    Common live context4

  5. Save the 2FA shared secret

    If this API user has two-factor authentication, paste the base32 secret shown when 2FA was enrolled into 2FA shared secret. Do not enter the rotating six-digit code. Leave the field empty when the user has no 2FA.

  6. Enter the connection values

    Paste the API username into API user, its password into Password, and the numeric context into Context. Turn on Include sub-user zones only when this is a parent user that should see child accounts.

Troubleshooting

AutoDNS rejects the username, password, context, or 2FA token

Check all four values together. A live PersonalAutoDNS account may need its own context number rather than 4, and the 2FA field needs the enrollment secret rather than a current code.

Access is forbidden after authentication succeeds

The user is missing an ACL for the API task being called. Add the matching list/info task for preview or update/job task for apply.

Sub-user zones or domains are absent

Use a parent user with permission to see child accounts, then turn on Include sub-user zones.

Check access succeeds but a cutover fails

Check access only lists objects. Confirm DomainUpdate, DNSSEC update, and JobInfo are assigned before retrying the write.

Official documentation

Guide checked against the official documentation on .

Credential fields

FieldRequirementWhere to find it
API userusernameRequiredThe dedicated AutoDNS API user's login name, exactly as created in User management.
PasswordpasswordRequiredThe password belonging to that API user.
ContextcontextRequiredThe numeric API context: 1 for the demo system, or 4/the PersonalAutoDNS context number for the live system.
2FA shared secrettotpSecretOptionalOptional base32 shared secret displayed when 2FA was enrolled. This is not the current six-digit TOTP code.
Include sub-user zonesincludeSubUsersOptionalOptional. Turn on only for a parent or administrator user when zones and domains owned by sub-users must be included.

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

Caveats

  • AutoDNS replaces the whole zone on each update, so we read, merge and write the full record list.
  • Legacy zones with a "main" IP (and automatic www record) are converted into normal A records on the first write.
  • TXT values lose interior double quotes, unpaired backslashes and leading or trailing spaces.

Troubleshooting

AutoDNS rejects the username, password, context, or 2FA token
Check all four values together. A live PersonalAutoDNS account may need its own context number rather than 4, and the 2FA field needs the enrollment secret rather than a current code.
Access is forbidden after authentication succeeds
The user is missing an ACL for the API task being called. Add the matching list/info task for preview or update/job task for apply.
Sub-user zones or domains are absent
Use a parent user with permission to see child accounts, then turn on Include sub-user zones.
Check access succeeds but a cutover fails
Check access only lists objects. Confirm DomainUpdate, DNSSEC update, and JobInfo are assigned before retrying the write.

Related links

AutoDNS (InterNetX) migration overviewMarketing overview and provider differences.Connect a providerHow connection checks and permissions work.Cloudflare → AutoDNSRoute 53 → AutoDNSAzure DNS → AutoDNSCloud DNS → AutoDNS