Name.com Gandi LiveDNS
Migrate DNS from Name.com to Gandi.
8 record types move as they are. Nothing else needs special handling.
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
- ALIAS
- CNAME
- MX
- TXT
- NS
- SRV
A straightforward move.
A typical Name.com zone at Gandi
Example records for example.com. Open any flagged row to read why it changed.
Name.com Gandi
- ExactA@
192.0.2.70
- ExactAAAA@
2001:db8::70
- 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"
- ExactSRV_sip._tls
100 1 443 sip.example.net.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Gandi | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Name.com
Connect Name.com with read-only access (Username + API token (Core API, HTTP Basic)).
- 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 Name.com 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 Name.com
- Only A, AAAA, ANAME, CNAME, MX, NS, SRV and TXT records are supported (no CAA or PTR).
- The minimum TTL is 300 seconds and TXT values are limited to about 512 characters.
- Only domains registered at Name.com can be managed, and apex NS records follow the domain's nameservers.
Access we need: Name.com API tokens are account-wide with no read-only scope; the same token is used for preview and apply.
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 Name.com 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 Name.com?
No. We never write to Name.com. 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