Namecheap BasicDNS Realtime Register
Migrate DNS from Namecheap to Realtime Register.
8 record types move as they are. 2 things work differently at Realtime Register, 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
URL301, FRAME, MXE aren't available
Realtime Register rewrites the whole host list
A typical Namecheap zone at Realtime Register
Example records for example.com. Open any flagged row to read why it changed.
Namecheap Realtime Register
- TranslatedALIAS@
app.example-host.net.
Stored as a Realtime Register 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 Realtime Register.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Realtime Register | 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 Realtime Register
Connect Realtime Register (API key (Authorization: ApiKey)). 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 Realtime Register
We snapshot the Realtime Register zone, write in batches, and leave Namecheap untouched.
- 5
Verify
We query Realtime Register'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 Realtime Register
- Every change rewrites the zone's full custom record list in one request; records we don't manage (such as MBOXFW and HINFO) are sent back unchanged.
- Basic and Premium DNS are separate services with separate zones; the connection works with one of them at a time.
- Zones linked to a DNS template also receive the template's records, which are managed on the template, not per zone.
Access we need: An API user with VIEW_DNS_ZONE for the preview; CREATE_DNS_ZONE and UPDATE_DNS_ZONE to apply.
Questions
Will there be downtime moving from Namecheap to Realtime Register?
Not if both providers serve the same answers during the switch. The records are copied to Realtime Register 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 Realtime Register and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview