Skip to content
DNSmigrator

easyDNS deSEC

Migrate DNS from easyDNS to deSEC.

14 record types move as they are. 2 things work differently at deSEC, and the preview shows exactly which of your records they affect.

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

easyDNS to deSEC 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
  • NAPTR
  • SPF
  • SSHFP
  • TLSA
  • CERT

Alias records are converted

easyDNS alias records become CNAMEs below the apex. At the apex they need static addresses, and the preview shows which ones.

TTLs below 3600s are raised

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

A typical easyDNS zone at deSEC

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

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

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 easyDNS

    Connect easyDNS with read-only access (REST API token and API key (HTTP Basic)).

  2. 2

    Connect deSEC

    Connect deSEC (API token). 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 deSEC

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

  5. 5

    Verify

    We query deSEC'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 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.

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 easyDNS 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 easyDNS?

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

Related migrations

Ready to see your own zone?

Start a free preview