Tencent Cloud DNSPod Google Cloud DNS
Migrate DNS from DNSPod to Cloud DNS.
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.
A typical DNSPod zone at Cloud DNS
Example records for example.com. Open any flagged row to read why it changed.
DNSPod Cloud 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.
| Status | Type | Name | At Cloud DNS | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect DNSPod
Connect DNSPod with read-only access (CAM SecretId + SecretKey).
- 2
Connect Cloud DNS
Connect Cloud DNS (Service account key (JSON)). Write access is only used when you apply.
- 3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
- 4
Apply to Cloud DNS
We snapshot the Cloud DNS zone, write in batches, and leave DNSPod untouched.
- 5
Verify
We query Cloud DNS's own nameservers for every record and compare the answers before you switch.
- 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 Cloud DNS
- Routing policies (weighted round robin, geolocation, failover) don't carry over to most providers.
- Apex CNAMEs are not allowed.
Access we need: roles/dns.reader for the preview, roles/dns.admin to apply.
Questions
Will there be downtime moving from DNSPod to Cloud DNS?
Not if both providers serve the same answers during the switch. The records are copied to Cloud 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 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 Cloud DNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview