Skip to content
DNSmigrator

Namecheap BasicDNS EdgeCenter DNS

Migrate DNS from Namecheap to EdgeCenter.

7 record types move as they are. 2 things work differently at EdgeCenter, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

Namecheap to EdgeCenter DNS migration differences

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.

A typical Namecheap zone at EdgeCenter

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

Namecheap EdgeCenter

  • UnsupportedALIAS@

    Not migrated

    @ is an alias to app.example-host.net at the zone apex. EdgeCenter 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 EdgeCenter.

  • ExactCNAMEwww

    example.com.

Set up the connections

Use the provider-specific credential guides before you preview, then keep the migration checklist beside the cutover plan.

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 EdgeCenter

    Connect EdgeCenter (Permanent API 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 EdgeCenter

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

  5. 5

    Verify

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

  • Record sets that use GeoDNS, weighted balancing or DNS Failover filters, answer metadata or disabled answers are copied as plain answers and never changed by us.
  • The API allows about 4 requests per second, so large zones are written one record set at a time.
  • The minimum TTL depends on your EdgeCenter plan (usually 60 seconds); lower values are rejected by EdgeCenter.
  • ALIAS, PTR, HTTPS and SVCB records aren't available, and a CNAME can't sit at the zone apex.

Access we need: A permanent API token with the Users role is enough to read zones as a migration source. Writing records needs the Engineers role; Administrators is never required.

Questions

Will there be downtime moving from Namecheap to EdgeCenter?

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