Dynu
Dynu API key setup: create or reset the account API key in Dynu's API Credentials area and paste that key, not OAuth credentials.
On this page
Dynu API key permissions
- Credential type
- API key
- Preview access
- The account API key; Dynu's published API-key flow does not offer a read-only scope.
- Apply access
- The same account API key used for preview.
- API endpoint
- DNSMigrator uses the provider's fixed API endpoint.
Additional access
DNSControl id
{
"TYPE": "DYNU"
}Create credentials
Create or reset the account API key in Dynu's API Credentials area and paste that key, not OAuth credentials.
Access you'll grant
The account API key; Dynu's published API-key flow does not offer a read-only scope.
The same account API key used for preview.
Before you start
- A Dynu account with access to the DNS service you want to connect.
Setup steps
0 of 5 done
Open API Credentials
Sign in to the Dynu control panel and open API Credentials.
Create or reset the API key
Use the API key section to create a key. If an account key already exists and you cannot retrieve it, reset it; resetting replaces the key used by every existing integration on the account.
Copy the API key
Copy the complete API key. Do not copy the OAuth2 client_id, secret, or an eight-hour Bearer access token: this connection uses Dynu's non-expiring
API-Keyauthentication scheme.Request headerAPI-KeyPaste the key
Paste the value into API key, then check access. No source-IP value is part of Dynu's documented API-key setup.
Clear the key after use
If this was a migration-only connection, remove it from DNSMigrator and use Clear or Reset in API Credentials. Update any other integration before resetting a shared account key.
Troubleshooting
Dynu rejects the key
Confirm you pasted the API key from the API key section. OAuth client credentials and OAuth access tokens are different credential types and are not accepted in this field.
A previously working key stopped working
Someone may have used Reset or Clear in API Credentials. Copy the current replacement key and update every integration that shared the old one.
No DNS domains appear
The key identifies one Dynu account. Sign in to that same account and confirm the domain appears in its DNS service list.
Official documentation
Guide checked against the official documentation on .
Credential fields
| Field | Requirement | Where to find it |
|---|---|---|
| API keyapiKey | Required | The account API key from Control Panel → API Credentials. It is not an OAuth client ID, OAuth secret, or temporary access token. |
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
- DNAME
Caveats
- Wildcard records are a domain setting in Dynu and can't be migrated as DNS records.
- TLSA, SSHFP, HTTPS/SVCB and other advanced types are read but not written, because the API's encoding for them is ambiguous.
- Web redirects are separate objects and aren't migrated.
Troubleshooting
- Dynu rejects the key
- Confirm you pasted the API key from the API key section. OAuth client credentials and OAuth access tokens are different credential types and are not accepted in this field.
- A previously working key stopped working
- Someone may have used Reset or Clear in API Credentials. Copy the current replacement key and update every integration that shared the old one.
- No DNS domains appear
- The key identifies one Dynu account. Sign in to that same account and confirm the domain appears in its DNS service list.