Mythic Beasts
Mythic Beasts API key setup: create a Primary DNS API v2 key restricted to the zones and record operations DNSMigrator needs.
On this page
Mythic Beasts API key permissions
- Credential type
- Primary DNS API v2 key ID and secret
- Preview access
- Primary DNS API v2 access to list zones and read records with GET.
- Apply access
- Preview access plus permission to replace and delete records with PUT and DELETE.
- API endpoint
- DNSMigrator uses the provider's fixed API endpoint.
Additional access
DNSControl id
{
"TYPE": "MYTHICBEASTS"
}Create credentials
Create a Primary DNS API v2 key restricted to the zones and record operations DNSMigrator needs.
Access you'll grant
Primary DNS API v2 access to list zones and read records with GET.
Preview access plus permission to replace and delete records with PUT and DELETE.
Before you start
- A Mythic Beasts account with each zone already added and DNS enabled; this connection cannot create zones.
- Permission to create API keys for the account.
Setup steps
0 of 5 done
Prepare each zone
Open Domains, add each domain if needed, and enable DNS. If its DNS template is Mythic Beasts nameservers only, change it to None before DNSMigrator manages the complete record set.
Open API Keys
Sign in to the customer control panel and open API Keys. Primary DNS API v1 credentials do not work with v2.
Create a DNS API v2 key
Create a key for Primary DNS API v2, then restrict it to the zones you are connecting. For the narrowest access, also restrict it to the record types you intend to move.
APIPrimary DNS API v2Choose record access
For preview-only access, permit zone listing and record reads. To apply changes, also permit record replacement and deletion. DNSMigrator calls
GET /zones,GET .../records,PUT .../records/{host}/{type}, andDELETE .../records/{host}/{type}.Preview methodsGETApply methodsGET, PUT, DELETECopy both credential values
Copy the new Key ID and Secret. Paste them into API key ID and API key secret here; keep them as a pair.
Troubleshooting
Mythic Beasts rejects the key ID or secret
Confirm both values came from the same Primary DNS API v2 key. DNS API v1 credentials and temporary OAuth access tokens are not accepted here.
The zone list is empty or a zone is missing
Add the domain in the control panel, enable DNS, and include that zone in the API key restrictions.
Preview works but apply returns 403
The access check only lists zones. Edit or replace the key so it can PUT and DELETE records in every selected zone and for every record type being changed.
Official documentation
Guide checked against the official documentation on .
Credential fields
| Field | Requirement | Where to find it |
|---|---|---|
| API key IDkeyId | Required | The Key ID shown for the new Primary DNS API v2 key on the API Keys page. |
| API key secretsecret | Required | The secret paired with that Key ID. This is the password in Mythic Beasts Basic authentication. |
Capabilities
- Create zones
- No
- List zones
- Yes
- DNSSEC
- Managed in the provider console
- Minimum TTL
- 60 seconds
- Apex CNAME
- No
- Read only
- No
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- ALIAS
- DNAME
- PTR
- SSHFP
- TLSA
Caveats
- Domains must be added in the control panel with DNS enabled before records can be managed through the API.
- ANAME records are resolved by a periodic job, so their generated A/AAAA records can take a few minutes to appear.
- TXT values containing double quotes or backslashes are rejected by the API.
Troubleshooting
- Mythic Beasts rejects the key ID or secret
- Confirm both values came from the same Primary DNS API v2 key. DNS API v1 credentials and temporary OAuth access tokens are not accepted here.
- The zone list is empty or a zone is missing
- Add the domain in the control panel, enable DNS, and include that zone in the API key restrictions.
- Preview works but apply returns 403
- The access check only lists zones. Edit or replace the key so it can PUT and DELETE records in every selected zone and for every record type being changed.