Skip to content
dnsmigrator

Namecheap BasicDNS Sakura Cloud DNS

Migrate DNS from Namecheap to Sakura Cloud.

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

Sakura Cloud rewrites the whole host list

Every write to Sakura Cloud's API replaces all records. We read, merge and write once, so records outside the migration survive.

A typical Namecheap zone at Sakura Cloud

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

Namecheap Sakura Cloud

  • TranslatedALIAS@

    app.example-host.net.

    Stored as a Sakura Cloud ALIAS record to app.example-host.net.

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

  • ExactCNAMEblog

    example.github.io.

  • UnsupportedURL301go

    Not migrated

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

  • 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 Sakura Cloud

    Connect Sakura Cloud (API key (access token + access token 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 Sakura Cloud

    We snapshot the Sakura Cloud zone, write in batches, and leave Namecheap untouched.

  5. 5

    Verify

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

Questions

Will there be downtime moving from Namecheap to Sakura Cloud?

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