Skip to content
DNSmigrator

Azure DNS easyDNS

Migrate DNS from Azure DNS to easyDNS.

9 record types move as they are. 1 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.

Azure DNS 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

TTLs below 300s are raised

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

A typical Azure DNS zone at easyDNS

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

Azure DNS easyDNS

  • UnsupportedA@

    Not migrated

    @ is an alias to an Azure resource. It needs static IP addresses at easyDNS.

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

  • ExactAapp

    192.0.2.30

  • 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 Azure DNS

    Connect Azure DNS with read-only access (Service principal (client ID + secret)).

  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 Azure DNS 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 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 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 Azure DNS 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 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 easyDNS 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