Azure DNS Scaleway Domains and DNS
Migrate DNS from Azure DNS to Scaleway.
8 record types move as they are. 2 things work differently at Scaleway, 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 60s are raised
A typical Azure DNS zone at Scaleway
Example records for example.com. Open any flagged row to read why it changed.
Azure DNS Scaleway
- UnsupportedA@
Not migrated
@ is an alias to an Azure resource. It needs static IP addresses at Scaleway.
- 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.
- ExactAapp
192.0.2.30
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Scaleway | TTL | Details |
|---|---|---|---|---|---|
| Unsupported | A | @ | Not migrated | — | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | A | app |
| 5m | |
| 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 Scaleway
Connect Scaleway (IAM API secret key (+ optional project ID)). 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 Scaleway
We snapshot the Scaleway zone, write in batches, and leave Azure DNS untouched.
- 5
Verify
We query Scaleway'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 Scaleway
- Zones must already exist in the Scaleway console. We can't create them.
- Records that use GeoIP, weighted, HTTP-service or view routing are copied as their default value, flagged in a comment and never changed by us.
- NS records below the apex need a TTL of at least 1800 seconds, so shorter TTLs are raised.
Access we need: An IAM policy with DomainsDNSReadOnly for the preview; DomainsDNSFullAccess to apply.
Questions
Will there be downtime moving from Azure DNS to Scaleway?
Not if both providers serve the same answers during the switch. The records are copied to Scaleway 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 Scaleway and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview