Namecheap BasicDNS Gandi LiveDNS

Migrate DNS from Namecheap to Gandi.

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

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

TTLs below 300s are raised

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

A typical Namecheap zone at Gandi

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

Namecheap Gandi

TranslatedALIAS@
app.example-host.net.
Stored as a Gandi 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 Gandi.
ExactCNAMEwww
example.com.

How each record at Namecheap BasicDNS translates to Gandi LiveDNS
Status	Type	Name	At Gandi	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
Unsupported	URL301	go	Not migrated	—
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 Gandi
Connect Gandi (Personal access token (legacy API key also accepted)). 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 Gandi
We snapshot the Gandi zone, write in batches, and leave Namecheap untouched.
5
Verify
We query Gandi'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 Gandi

LiveDNS only hosts zones for domains in your Gandi organization, so zones can't be created for domains registered elsewhere.
ALIAS records are only allowed at the zone apex; TTLs must be between 300 seconds and 30 days.
Apex NS records are managed by Gandi and are left untouched.

Access we need: A token with “Manage domain name technical configurations”, scoped to the domains you move. Gandi has no read-only LiveDNS permission.

Questions

Will there be downtime moving from Namecheap to Gandi?

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

Ready to see your own zone?

Start a free preview