Cloud platformDNS hostingCapabilities verified
Constellix DNS
Migrate DNS zones to or from Constellix DNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Constellix. Free and read-only.
Access we need
- Credentials
- API key + secret key (HMAC-signed requests)
- Permissions
- Constellix API keys carry the permissions of the user who generated them and can't be limited to read-only. Generate them under a user that only manages the domains you're moving.
What Constellix 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
- 0s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- ALIAS
- NAPTR
- SPF
- CERT
- RP
Constellix-only records
- URLFWD
These have no equivalent elsewhere and are flagged in every preview.
Good to know
- Records using failover, traffic pools, IP filters, GeoProximity or regional answers are flagged and never changed by us; only the default answer is copied.
- HINFO records and DNSSEC aren't available through the Constellix v4 API.
- HTTP redirection records map to URL forwards for the whole hostname (301, 302 or frame); page title and keywords of frame redirects aren't copied.
- CAA records only support the issue, issuewild and iodef tags.
- Requests are signed with the current time, so the server clock must be accurate.