Namecheap BasicDNS AutoDNS (InterNetX)
Migrate DNS from Namecheap to AutoDNS.
8 record types move as they are. 2 things work differently at AutoDNS, 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
URL, URL301, FRAME, MXE aren't available
AutoDNS rewrites the whole host list
A typical Namecheap zone at AutoDNS
Example records for example.com. Open any flagged row to read why it changed.
Namecheap AutoDNS
- TranslatedALIAS@
app.example-host.net.
Stored as a AutoDNS 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 AutoDNS.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At AutoDNS | TTL | Details |
|---|---|---|---|---|---|
| Translated | ALIAS | @ |
| 30m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | CNAME | blog |
| 30m | |
| Unsupported | URL301 | go | Not migrated | — | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Namecheap
Connect Namecheap with read-only access (API user + API key, with our egress IP allow-listed).
- 2
Connect AutoDNS
Connect AutoDNS (API user + password + context (Basic auth), optional TOTP 2FA secret). Write access is only used when you apply.
- 3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
- 4
Apply to AutoDNS
We snapshot the AutoDNS zone, write in batches, and leave Namecheap untouched.
- 5
Verify
We query AutoDNS's own nameservers for every record and compare the answers before you switch.
- 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 AutoDNS
- AutoDNS replaces the whole zone on each update, so we read, merge and write the full record list.
- Legacy zones with a "main" IP (and automatic www record) are converted into normal A records on the first write.
- TXT values lose interior double quotes, unpaired backslashes and leading or trailing spaces.
Access we need: A sub-user with the zone info and zone list ACLs for the preview; zone update (and zone create to create zones) to apply.
Questions
Will there be downtime moving from Namecheap to AutoDNS?
Not if both providers serve the same answers during the switch. The records are copied to AutoDNS 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 AutoDNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview