For the complete documentation index, see llms.txt. This page is also available as Markdown.

AutoDNS

Configuration

To use this provider, add an entry to creds.json with TYPE set to AUTODNS along with username, password and a context.

Example:

creds.json
{
  "autodns": {
    "TYPE": "AUTODNS",
    "username": "autodns.service-account@example.com",
    "password": "[***]",
    "context": "33004"
  }
}

Two factor authentication

If two-factor authentication has been enabled on your account you will also need to provide a valid TOTP code. This can also be done via an environment variable:

creds.json
{
  "autodns": {
    "TYPE": "AUTODNS",
    "username": "autodns.service-account@example.com",
    "password": "[***]",
    "context": "33004",
    "totp": "$AUTODNS_TOTP"
  }
}

and then you can run

It is also possible to directly provide the shared TOTP secret using the key "totp-key" in creds.json. This secret is only available when first enabling two-factor authentication.

Security Warning:

  • Anyone with access to this creds.json file will have full access to your AutoDNS account and will be able to modify and delete your DNS entries.

  • Storing the shared secret together with the password weakens two factor authentication because both factors are stored in a single place.

totp and totp-key must not be set at the same time. Omit both if the account does not use two factor authentication.

Including sub-user zones

By default DNSControl only sees zones owned directly by the configured user. If you authenticate as a master/admin user and want get-zones (and the all keyword) to also include zones owned by sub-users β€” the same optional "include subusers" toggle the AutoDNS web UI offers β€” set children to "true":

Usage

An example configuration:

Feature Summary

Last updated