Skip to content
dnsmigrator

Cloudflare DNS netcup

Migrate DNS from Cloudflare to netcup.

8 record types move as they are. 6 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
  • TLSA

Proxied records lose the CDN

netcup has no equivalent of Cloudflare's proxy. Proxied records move as plain records pointing at your origin, which exposes the origin IP. Put a CDN in front before cutting over if that matters.

Apex CNAMEs need a different shape

netcup doesn't allow a CNAME at the apex and has no alias record for external hostnames. These become static A/AAAA records, which don't follow the target if its IPs change.

TTLs below 86400s are raised

netcup's minimum TTL is 86400 seconds. Shorter TTLs are raised to 86400s and shown as translated.

"Auto" TTLs get a real value

Cloudflare's automatic TTL has no equivalent, so those records get netcup's default of 86400s.

Domains registered at Cloudflare must transfer out

Cloudflare Registrar only allows Cloudflare's nameservers. If the domain is registered there, transfer it to another registrar before switching.

A typical Cloudflare zone at netcup

Example records for example.com. Open any flagged row to read why it changed.

Cloudflare netcup

  • UnsupportedCNAME@

    Not migrated

    @ is a CNAME at the zone apex. netcup doesn't allow that, and app.example-host.net isn't a target it can alias.

  • 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.

  • TranslatedAmail

    203.0.113.25

    TTL 300s is outside the allowed range. Set to 86400s.

  • ReviewAshop

    203.0.113.10

    TTL was "auto". Set to 86400s.

  • TranslatedCNAMEwww

    example.com.

    TTL 3600s is outside the allowed range. Set to 86400s.

How the move works

  1. 1

    Connect Cloudflare

    Connect Cloudflare with read-only access (Scoped API token).

  2. 2

    Connect netcup

    Connect netcup (Customer number + API key + API password (CCP API session)). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to netcup

    We snapshot the netcup zone, write in batches, and leave Cloudflare untouched.

  5. 5

    Verify

    We query netcup's own nameservers for every record and compare the answers before you switch.

  6. 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 Cloudflare

  • Proxied (orange-cloud) records hide the origin IP. Moving them to another provider sends traffic straight to the origin.
  • Apex CNAMEs are flattened by Cloudflare. Other providers need an ALIAS record or static A/AAAA records instead.
  • Cloudflare Registrar only allows Cloudflare nameservers, so domains registered there must be transferred out first.

Access we need: Zone → DNS → Read for the preview, Zone → DNS → Edit 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 Cloudflare 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 Cloudflare?

No. We never write to Cloudflare. 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.

What happens to Cloudflare proxied records?

They move as ordinary records pointing at your origin server, because netcup can't proxy traffic. The preview lists every proxied record and the IP it would expose.

Related migrations

Ready to see your own zone?

Start a free preview