Namecheap BasicDNS INWX

Migrate DNS from Namecheap to INWX.

8 record types move as they are. 2 things work differently at INWX, 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

MXE isn't available

INWX can't store MXE records through its API. They're marked Unsupported with the reason, never dropped silently.

TTLs below 300s are raised

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

A typical Namecheap zone at INWX

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

Namecheap INWX

TranslatedALIAS@
app.example-host.net.
Stored as a INWX 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.
ExactURL301go
https://example.com/start
ExactCNAMEwww
example.com.

How each record at Namecheap BasicDNS translates to INWX
Status	Type	Name	At INWX	TTL
Translated	ALIAS	@	app.example-host.net.	30m
Exact	MX	@	10 mx1.mail.example.net. 20 mx2.mail.example.net.	1h
Exact	TXT	@	"v=spf1 include:_spf.example.net -all"	1h
Exact	CAA	@	0 issue "letsencrypt.org"	1h
Exact	TXT	_dmarc	"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"	1h
Exact	CNAME	blog	example.github.io.	30m
Exact	URL301	go	https://example.com/start	30m
Exact	CNAME	www	example.com.	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 INWX
Connect INWX (Username + password session login, with 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 INWX
We snapshot the INWX zone, write in batches, and leave Namecheap untouched.
5
Verify
We query INWX'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 INWX

TTLs must be between 300 seconds and 10 days.
Each record value is a separate API call, and INWX limits login attempts, so large zones apply slowly.
Accounts with 2FA need the TOTP shared secret, which stores both factors together.

Access we need: A sub-account with nameserver view rights for the preview; nameserver edit (and DNSSEC) rights to apply.

Questions

Will there be downtime moving from Namecheap to INWX?

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

Ready to see your own zone?

Start a free preview