Skip to content
dnsmigrator

Tencent Cloud DNSPod Akamai Edge DNS

Migrate DNS from DNSPod to Akamai.

9 record types move as they are. Nothing else needs special handling.

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

A straightforward move.

Every record type DNSPod supports has a direct equivalent at Akamai.

A typical DNSPod zone at Akamai

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

DNSPod Akamai

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

    Connect DNSPod with read-only access (CAM SecretId + SecretKey).

  2. 2

    Connect Akamai

    Connect Akamai (EdgeGrid API client (host, client token, client secret, access token)). 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 Akamai

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

  5. 5

    Verify

    We query Akamai'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 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.

Good to know about Akamai

  • AKAMAICDN and non-DUAL AKAMAITLC records point at Akamai edge hostnames. Other providers have no equivalent, so recreate them as CNAME or ALIAS records by hand.
  • Apex ALIAS records are stored as AKAMAITLC records with the DUAL answer type. ALIAS records below the apex become CNAMEs.
  • TXT values can't contain double quotes or backslashes.

Access we need: DNS—Zone Record Management API: READ-ONLY for the preview, READ-WRITE to apply.

Questions

Will there be downtime moving from DNSPod to Akamai?

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

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