RegistrarDNS hostingCapabilities verified
TransIP
Migrate DNS zones to or from TransIP: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at TransIP. Free and read-only.
Access we need
- Credentials
- Username + API private key (signed JWT), or an access token
- Permissions
- An API key pair on the account (optionally IP-whitelisted), or a read-only access token for the preview and a read/write token to apply.
What TransIP supports
The same data the translation engine uses when it plans a migration.
- Create zones through the API
- List zones through the API
- Turn on DNSSEC through the API
- Apex CNAME (flattening)
- Apex ALIAS record
- Aliases to cloud resources
- CDN proxy on records
- Routing policies
- Minimum TTL
- 60s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- ALIAS
- NAPTR
- SSHFP
- TLSA
Good to know
- Every change replaces the domain's full DNS entry list in one request; entries outside the plan are sent back unchanged.
- The API allows 1000 requests per 15 minutes per account, and access tokens expire after at most one month.
- TXT values with double quotes, backslashes, backticks or trailing spaces are rejected or altered by TransIP.