EdgeCenter DNS Azure DNS
Migrate DNS from EdgeCenter to Azure DNS.
8 record types move as they are. 1 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.
EdgeCenter 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
DNAME isn't available
A typical EdgeCenter zone at Azure DNS
Example records for example.com. Open any flagged row to read why it changed.
EdgeCenter 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 EdgeCenter
Connect EdgeCenter with read-only access (Permanent API token).
- 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 EdgeCenter 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 EdgeCenter
- Record sets that use GeoDNS, weighted balancing or DNS Failover filters, answer metadata or disabled answers are copied as plain answers and never changed by us.
- The API allows about 4 requests per second, so large zones are written one record set at a time.
- The minimum TTL depends on your EdgeCenter plan (usually 60 seconds); lower values are rejected by EdgeCenter.
- ALIAS, PTR, HTTPS and SVCB records aren't available, and a CNAME can't sit at the zone apex.
Access we need: A permanent API token with the Users role is enough to read zones as a migration source. Writing records needs the Engineers role; Administrators is never required.
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 EdgeCenter 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 EdgeCenter?
No. We never write to EdgeCenter. 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?