Azure DNS Alibaba Cloud DNS
Migrate DNS from Azure DNS to Alibaba Cloud.
8 record types move as they are. 2 things work differently at Alibaba Cloud, and the preview shows exactly which of your records they affect.
Free preview. Read-only. Nothing changes until you apply.
What works differently
Generated from the same provider capability data the migration engine uses.
Moves as-is
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
PTR isn't available
TTLs below 600s are raised
A typical Azure DNS zone at Alibaba Cloud
Example records for example.com. Open any flagged row to read why it changed.
Azure DNS Alibaba Cloud
- UnsupportedA@
Not migrated
@ is an alias to an Azure resource. It needs static IP addresses at Alibaba Cloud.
- 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.
- TranslatedAapp
192.0.2.30
TTL 300s is outside the allowed range. Set to 600s.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Alibaba Cloud | TTL | Details |
|---|---|---|---|---|---|
| Unsupported | A | @ | Not migrated | — | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Translated | A | app |
| 10m | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Azure DNS
Connect Azure DNS with read-only access (Service principal (client ID + secret)).
- 2
Connect Alibaba Cloud
Connect Alibaba Cloud (RAM user AccessKey). 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 Alibaba Cloud
We snapshot the Alibaba Cloud zone, write in batches, and leave Azure DNS untouched.
- 5
Verify
We query Alibaba Cloud'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 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.
Good to know about Alibaba Cloud
- Free and Personal editions have a minimum TTL of 600 seconds; only Enterprise Ultimate allows TTLs down to 1 second.
- TXT values are limited to 512 characters and MX priorities must be 50 or lower.
- ALIAS records and DNSSEC are only available on paid editions.
Access we need: AliyunDNSReadOnlyAccess for the preview, AliyunDNSFullAccess (or a custom alidns:* write policy) to apply.
Questions
Will there be downtime moving from Azure DNS to Alibaba Cloud?
Not if both providers serve the same answers during the switch. The records are copied to Alibaba Cloud 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 Azure DNS?
No. We never write to Azure DNS. 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 Alibaba Cloud and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview