Skip to content
dnsmigrator

Namecheap BasicDNS Loopia

Migrate DNS from Namecheap to Loopia.

7 record types move as they are. 3 things work differently at Loopia, 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 records are converted

Namecheap alias records become CNAMEs below the apex. At the apex they need static addresses, and the preview shows which ones.

TTLs below 300s are raised

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

A typical Namecheap zone at Loopia

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

Namecheap Loopia

  • UnsupportedALIAS@

    Not migrated

    @ is an alias to app.example-host.net at the zone apex. Loopia doesn't support apex aliases or CNAMEs.

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

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

    Connect Loopia (LoopiaAPI username + password). 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 Loopia

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

  5. 5

    Verify

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

  • Loopia's API can't read the domain's delegation or DNSSEC state, so we check those through public DNS.
  • LoopiaAPI allows 60 calls per minute and needs one call per record change plus one per host name to read, so large zones take several minutes.
  • Apex NS records are managed by Loopia and are not changed; ALIAS, PTR and DS records are not available.
  • TTLs below 300 seconds are served as 300, and TXT values longer than 450 characters are rejected.

Access we need: An API user allowed getDomains, getSubdomains and getZoneRecords for the preview; addZoneRecord, updateZoneRecord, removeZoneRecord and removeSubdomain to apply.

Questions

Will there be downtime moving from Namecheap to Loopia?

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