Constellix DNS Azure DNS
Migrate DNS from Constellix to Azure DNS.
9 record types move as they are. 3 things work differently at Azure DNS, and the preview shows exactly which of your records they affect.
Free preview. Read-only. Nothing changes until you apply.
Constellix to Azure DNS DNS migration differences
Generated from the same provider capability data the migration engine uses.
Moves as-is
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
Alias records are converted
NAPTR, CERT, RP, URLFWD aren't available
TTLs below 1s are raised
A typical Constellix zone at Azure DNS
Example records for example.com. Open any flagged row to read why it changed.
Constellix Azure DNS
- ExactA@
192.0.2.70
- ExactAAAA@
2001:db8::70
- ExactMX@
10 mx1.mail.example.net. +1
- ExactTXT@
"v=spf1 include:_spf.example.net -all"
- ExactCAA@
0 issue "letsencrypt.org"
- ExactTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
- ExactSRV_sip._tls
100 1 443 sip.example.net.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Azure DNS | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
Set up the connections
Use the provider-specific credential guides before you preview, then keep the migration checklist beside the cutover plan.
How the move works
- 1
Connect Constellix
Connect Constellix with read-only access (API key + secret key (HMAC-signed requests)).
- 2
Connect Azure DNS
Connect Azure DNS (Service principal (client ID + secret)). Write access is only used when you apply.
- 3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
- 4
Apply to Azure DNS
We snapshot the Azure DNS zone, write in batches, and leave Constellix untouched.
- 5
Verify
We query Azure DNS's own nameservers for every record and compare the answers before you switch.
- 6
Switch nameservers
Lower TTLs a day or two ahead, remove any DS record if DNSSEC is on, then point the domain at the new nameservers at your registrar.
Good to know about Constellix
- 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.
Access we need: 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.
Good to know about Azure DNS
- Azure alias records point at Azure resource IDs, which don't exist outside Azure.
- Apex CNAMEs are not allowed. Use an alias record to an Azure resource or A/AAAA records.
Access we need: Reader on the DNS zone for the preview, DNS Zone Contributor to apply.
Questions
Will there be downtime moving from Constellix to Azure DNS?
Not if both providers serve the same answers during the switch. The records are copied to Azure DNS and verified before you change nameservers, so resolvers get the same answer from either side while caches expire.
Do I have to delete anything at Constellix?
No. We never write to Constellix. Keep the old zone for a week after cutover so you can switch back instantly if anything looks wrong.
What about DNSSEC?
If DNSSEC is on, remove the DS record at your registrar and wait for it to expire before switching nameservers. Then enable DNSSEC at Azure DNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?