Sakura Cloud DNS Namecheap BasicDNS
Migrate DNS from Sakura Cloud to Namecheap.
8 record types move as they are. 4 things work differently at Namecheap, 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
- CAA
- ALIAS
SRV, HTTPS, SVCB, PTR aren't available
TTLs below 60s are raised
Namecheap rewrites the whole host list
Namecheap needs BasicDNS turned on
A typical Sakura Cloud zone at Namecheap
Example records for example.com. Open any flagged row to read why it changed.
Sakura Cloud Namecheap
- 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"
- UnsupportedSRV_sip._tls
Not migrated
Namecheap doesn't support SRV records through its API.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Namecheap | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Unsupported | SRV | _sip._tls | Not migrated | — | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Sakura Cloud
Connect Sakura Cloud with read-only access (API key (access token + access token secret)).
- 2
Connect Namecheap
Connect Namecheap (API user + API key, with our egress IP allow-listed). 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 Namecheap
We snapshot the Namecheap zone, write in batches, and leave Sakura Cloud untouched.
- 5
Verify
We query Namecheap'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 Sakura Cloud
- Every record with the same name must share one TTL, and a zone can hold at most 2,000 records.
- TXT values are limited to 500 characters of letters, digits, spaces and _ = : ; ~ , - . + / (no quotes or backslashes), and CAA records to 64 characters.
- DNSSEC isn't supported, and each write replaces the zone's whole record list, so changes are applied in one request.
Access we need: An API key with the Resource view access level for the preview; Settings edit to apply changes; Create/delete to create (billable) zones.
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.
Questions
Will there be downtime moving from Sakura Cloud to Namecheap?
Not if both providers serve the same answers during the switch. The records are copied to Namecheap 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 Sakura Cloud?
No. We never write to Sakura Cloud. 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 Namecheap and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview