Azure DNS netcup
Migrate DNS from Azure DNS to netcup.
7 record types move as they are. 2 things work differently at netcup, 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
- SRV
- CAA
NS, PTR aren't available
TTLs below 86400s are raised
A typical Azure DNS zone at netcup
Example records for example.com. Open any flagged row to read why it changed.
Azure DNS netcup
- UnsupportedA@
Not migrated
@ is an alias to an Azure resource. It needs static IP addresses at netcup.
- TranslatedMX@
10 mx1.mail.example.net. +1
TTL 3600s is outside the allowed range. Set to 86400s.
- TranslatedTXT@
"v=spf1 include:_spf.example.net -all"
TTL 3600s is outside the allowed range. Set to 86400s.
- TranslatedCAA@
0 issue "letsencrypt.org"
TTL 3600s is outside the allowed range. Set to 86400s.
- TranslatedTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
TTL 3600s is outside the allowed range. Set to 86400s.
- TranslatedSRV_sip._tls
100 1 443 sip.example.net.
TTL 3600s is outside the allowed range. Set to 86400s.
- TranslatedAapp
192.0.2.30
TTL 300s is outside the allowed range. Set to 86400s.
- TranslatedCNAMEwww
example.com.
TTL 3600s is outside the allowed range. Set to 86400s.
| Status | Type | Name | At netcup | TTL | Details |
|---|---|---|---|---|---|
| Unsupported | A | @ | Not migrated | — | |
| Translated | MX | @ |
| 1d | |
| Translated | TXT | @ |
| 1d | |
| Translated | CAA | @ |
| 1d | |
| Translated | TXT | _dmarc |
| 1d | |
| Translated | SRV | _sip._tls |
| 1d | |
| Translated | A | app |
| 1d | |
| Translated | CNAME | www |
| 1d |
How the move works
- 1
Connect Azure DNS
Connect Azure DNS with read-only access (Service principal (client ID + secret)).
- 2
Connect netcup
Connect netcup (Customer number + API key + API password (CCP API session)). 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 netcup
We snapshot the netcup zone, write in batches, and leave Azure DNS untouched.
- 5
Verify
We query netcup'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 netcup
- netcup has no per-record TTL: every record uses the zone TTL (86400 seconds by default), so source TTLs are not kept.
- Domains can only be listed for reseller accounts; everyone else enters the zone name, and NS records are not managed.
- TXT values with quotes or backslashes and CAA values with semicolons are altered or rejected by the API.
Access we need: A CCP API key and API password. netcup keys cannot be limited to read-only or to single domains, so the same key is used for preview and apply.
Questions
Will there be downtime moving from Azure DNS to netcup?
Not if both providers serve the same answers during the switch. The records are copied to netcup 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 netcup and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview