Skip to content
dnsmigrator

Namecheap BasicDNS Azure Private DNS

Migrate DNS from Namecheap to Azure Private DNS.

5 record types move as they are. 2 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

Alias records are converted

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

A typical Namecheap zone at Azure Private DNS

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

Namecheap Azure Private DNS

  • UnsupportedALIAS@

    Not migrated

    @ is an alias to app.example-host.net at the zone apex. Azure Private DNS doesn't support apex aliases or CNAMEs.

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

  • ExactCNAMEblog

    example.github.io.

  • UnsupportedURL301go

    Not migrated

    URL301 is a Namecheap redirect feature, not a DNS record. Recreate it as a redirect rule at Azure Private DNS.

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect Namecheap

    Connect Namecheap with read-only access (API user + API key, with our egress IP allow-listed).

  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 Namecheap 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 Namecheap

  • Namecheap's API replaces the whole host list on every write, so we always read, merge and then write.
  • SRV records can't be managed through the API.
  • URL redirect records are Namecheap-specific and aren't real DNS records.

Access we need: API access enabled under Profile → Tools, with our static IP added to the allow-list.

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

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

Related migrations

Ready to see your own zone?

Start a free preview