Skip to content
dnsmigrator

Azure DNS Tencent Cloud DNSPod

Migrate DNS from Azure DNS to DNSPod.

8 record types move as they are. 2 things work differently at DNSPod, 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

TTLs below 600s are raised

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

A typical Azure DNS zone at DNSPod

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

Azure DNS DNSPod

  • UnsupportedA@

    Not migrated

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

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

  • TranslatedAapp

    192.0.2.30

    TTL 300s is outside the allowed range. Set to 600s.

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect Azure DNS

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

  2. 2

    Connect DNSPod

    Connect DNSPod (CAM SecretId + SecretKey). 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 DNSPod

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

  5. 5

    Verify

    We query DNSPod'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 DNSPod

  • DNSSEC and DS records are managed in the DNSPod console; the API can't change them.
  • The minimum TTL depends on the DNSPod plan: 600 seconds on the free plan, lower on paid plans.
  • China-site and International-site accounts use different API endpoints; pick the matching site.
  • Records on non-default resolution lines (ISP or region routing) are read as geo-routed records.

Access we need: QcloudDNSPodReadOnlyAccess for the preview, QcloudDNSPodFullAccess (or a custom dnspod:* write policy) to apply.

Questions

Will there be downtime moving from Azure DNS to DNSPod?

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