Skip to content

Namecheap BasicDNS Constellix DNS

Migrate DNS from Namecheap to Constellix.

8 record types move as they are. 1 things work differently at Constellix, and the preview shows exactly which of your records they affect.

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

Namecheap to Constellix 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

A typical Namecheap zone at Constellix

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

Namecheap Constellix

  • TranslatedALIAS@

    app.example-host.net.

    Stored as a Constellix 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.

  • TranslatedURLFWDgo

    "/" "https://example.com/start" 301 0 0

    URL301 becomes URLFWD at Constellix, with the same behaviour.

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

    Connect Constellix (API key + secret key (HMAC-signed requests)). 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 Constellix

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

  5. 5

    Verify

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

  • Records using failover, traffic pools, IP filters, GeoProximity or regional answers are flagged and never changed by us; only the default answer is copied.
  • HINFO records and DNSSEC aren't available through the Constellix v4 API.
  • HTTP redirection records map to URL forwards for the whole hostname (301, 302 or frame); page title and keywords of frame redirects aren't copied.
  • CAA records only support the issue, issuewild and iodef tags.
  • Requests are signed with the current time, so the server clock must be accurate.

Access we need: Constellix API keys carry the permissions of the user who generated them and can't be limited to read-only. Generate them under a user that only manages the domains you're moving.

Questions

Will there be downtime moving from Namecheap to Constellix?

Not if both providers serve the same answers during the switch. The records are copied to Constellix 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 Constellix and publish its new DS record. The cutover plan walks you through each step.

Ready to see your own zone?