netcup deSEC
Migrate DNS from netcup to deSEC.
8 record types move as they are. Nothing else needs special handling.
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
- TLSA
A straightforward move.
A typical netcup zone at deSEC
Example records for example.com. Open any flagged row to read why it changed.
netcup deSEC
- TranslatedA@
192.0.2.70
TTL 300s is outside the allowed range. Set to 3600s.
- TranslatedAAAA@
2001:db8::70
TTL 300s is outside the allowed range. Set to 3600s.
- 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 deSEC | TTL | Details |
|---|---|---|---|---|---|
| Translated | A | @ |
| 1h | |
| Translated | AAAA | @ |
| 1h | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect netcup
Connect netcup with read-only access (Customer number + API key + API password (CCP API session)).
- 2
Connect deSEC
Connect deSEC (API token). 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 deSEC
We snapshot the deSEC zone, write in batches, and leave netcup untouched.
- 5
Verify
We query deSEC'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 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.
Good to know about deSEC
- The minimum TTL is 3600 seconds for most domains (deSEC sets it per domain) and the maximum is 86400.
- ALIAS/ANAME records and apex CNAMEs aren't supported; use A/AAAA or HTTPS records at the apex.
- Every zone is DNSSEC-signed automatically. Give the DS records to your registrar to complete the chain.
Access we need: Any token can read all RRsets. Applying needs write permission on the RRsets (token policies can restrict it); creating zones needs perm_create_domain.
Questions
Will there be downtime moving from netcup to deSEC?
Not if both providers serve the same answers during the switch. The records are copied to deSEC 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 netcup?
No. We never write to netcup. 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 deSEC and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview