Skip to content
DNSmigrator

Cloudflare DNS easyDNS

Migrate DNS from Cloudflare to easyDNS.

13 record types move as they are. 6 things work differently at easyDNS, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

Cloudflare to easyDNS 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
  • PTR
  • TLSA
  • SSHFP
  • NAPTR
  • CERT

Proxied records lose the CDN

easyDNS 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

easyDNS doesn't allow a CNAME at the zone apex, but its ALIAS record does the same job. We convert them automatically.

TTLs below 300s are raised

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

"Auto" TTLs get a real value

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

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 easyDNS

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

Cloudflare easyDNS

  • TranslatedALIAS@

    app.example-host.net.

    Apex CNAME stored as a easyDNS ALIAS record.

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

  • ExactAmail

    203.0.113.25

  • ReviewAshop

    203.0.113.10

    TTL was "auto". Set to 600s.

  • ExactCNAMEwww

    example.com.

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

    Connect Cloudflare

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

  2. 2

    Connect easyDNS

    Connect easyDNS (REST API token and API key (HTTP Basic)). 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 easyDNS

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

  5. 5

    Verify

    We query easyDNS'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. Redirect and Worker route records also need Zone → Single Redirect → Edit and Zone → Workers Routes → Edit.

Good to know about easyDNS

  • API access has to be requested from easyDNS, and new keys start on the sandbox until easyDNS certifies them for the live API.
  • easyDNS limits the API to one request per second and 500 requests per day by default; large zones can exhaust the daily quota, so ask easyDNS for a higher limit before big migrations.
  • Add the domain to your easyDNS account before migrating; adding domains through the API creates an invoice, so zones aren't created through this connection.
  • URL, HTTPS and stealth forwarders, dynamic and geo-targeted records are left untouched because the API doesn't document their format.
  • Apex NS and SOA records are managed by easyDNS and can't be changed.
  • TTLs below 300 seconds and MX preferences above 100 are rejected by easyDNS.
  • DNSSEC is managed in the easyDNS control panel.

Access we need: easyDNS API credentials can't be scoped to read-only or to single domains; they act for the whole easyDNS user. Request a dedicated API token and key for DNSMigrator so you can revoke it independently.

Questions

Will there be downtime moving from Cloudflare to easyDNS?

Not if both providers serve the same answers during the switch. The records are copied to easyDNS 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 easyDNS 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 easyDNS 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