Skip to content
dnsmigrator

NexDNS Azure DNS

Migrate DNS from NexDNS to Azure DNS.

9 record types move as they are. 3 things work differently at Azure DNS, 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
  • NS
  • SRV
  • CAA
  • PTR

Alias records are converted

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

TTLs below 1s are raised

Azure DNS's minimum TTL is 1 seconds. Shorter TTLs are raised to 1s and shown as translated.

A typical NexDNS zone at Azure DNS

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

NexDNS Azure DNS

  • ExactA@

    192.0.2.70

  • ExactAAAA@

    2001:db8::70

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

How the move works

  1. 1

    Connect NexDNS

    Connect NexDNS with read-only access (API key (Bearer, nxd_ prefix)).

  2. 2

    Connect Azure DNS

    Connect Azure DNS (Service principal (client ID + secret)). 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 Azure DNS

    We snapshot the Azure DNS zone, write in batches, and leave NexDNS untouched.

  5. 5

    Verify

    We query Azure DNS'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 NexDNS

  • The SOA record and the apex NS records are managed by NexDNS and can't be changed, so dual-hosting a zone with a second provider isn't possible.
  • Records are written one value per request against a per-account rate limit, so large zones take a while to apply.
  • Only A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR, ALIAS, DNAME, DS and TLSA are supported; ALIAS is the way to point the apex at a hostname.

Access we need: zones.read and records.read for the preview; add records.write to apply and zones.write to create zones or switch DNSSEC. API access needs a Pro plan or higher.

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.

Questions

Will there be downtime moving from NexDNS to Azure DNS?

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

No. We never write to NexDNS. 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 Azure DNS 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