Skip to content
dnsmigrator

Cloudflare DNS Azure Private DNS

Migrate DNS from Cloudflare to Azure Private DNS.

7 record types move as they are. 5 things work differently at Azure Private 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
  • SRV
  • PTR

Proxied records lose the CDN

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

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

"Auto" TTLs get a real value

Cloudflare's automatic TTL has no equivalent, so those records get Azure Private DNS's default of 3600s.

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

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

Cloudflare Azure Private DNS

  • UnsupportedCNAME@

    Not migrated

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

  • ExactMX@

    10 mx1.mail.example.net. +1

  • ExactTXT@

    "v=spf1 include:_spf.example.net -all"

  • UnsupportedCAA@

    Not migrated

    Azure Private DNS doesn't support CAA records through its API.

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

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect Cloudflare

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

  2. 2

    Connect Azure Private DNS

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

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

  5. 5

    Verify

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

  • Private zones only resolve inside Azure virtual networks linked to the zone, so changes can't be checked with public DNS lookups.
  • Link the zone to your virtual networks after migrating; records auto-registered by VMs are skipped.
  • Only A, AAAA, CNAME, MX, PTR, SRV and TXT records are supported; NS and CAA aren't.

Access we need: Reader on the resource group for the preview; Private DNS Zone Contributor to apply or create zones.

Questions

Will there be downtime moving from Cloudflare to Azure Private DNS?

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