Skip to content
DNSmigrator

Namecheap BasicDNS Openprovider

Migrate DNS from Namecheap to Openprovider.

6 record types move as they are. 3 things work differently at Openprovider, and the preview shows exactly which of your records they affect.

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

Namecheap to Openprovider DNS migration differences

Generated from the same provider capability data the migration engine uses.

Moves as-is

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • 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 900s are raised

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

A typical Namecheap zone at Openprovider

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

Namecheap Openprovider

  • UnsupportedALIAS@

    Not migrated

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

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

    Connect Openprovider (Contact person username and password with API access enabled). 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 Openprovider

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

  5. 5

    Verify

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

  • Openprovider only accepts TTLs of 900, 3600, 10800, 21600, 43200 and 86400 seconds; other TTLs are rounded up to the next accepted value.
  • Apex NS and SOA records are managed by Openprovider. NS records can't be added for subdomains and a CNAME can't sit at the zone apex (no ALIAS/ANAME).
  • Null MX records (target ".") aren't supported. Legacy SPF-type records can be read and removed but not created; use TXT.
  • Sectigo Premium DNS zones aren't listed or changed through this connection.
  • Zones on Openprovider nameservers are signed automatically. For domains on other nameservers, Openprovider registers DNSSEC from the DNSKEY public key, not the DS digest.
  • Identical API calls are limited to 300 per 5 minutes and failed logins to 100 per hour; going over can block the contact's API access until it's unblocked in the control panel.

Access we need: Openprovider API access is switched on per contact person and uses that contact's login; it can't be limited to read-only or to DNS only. Create a dedicated contact person for DNSMigrator and turn its API access off when you're done.

Questions

Will there be downtime moving from Namecheap to Openprovider?

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