IBM NS1 Connect Name.com
Migrate DNS from NS1 to Name.com.
8 record types move as they are. 2 things work differently at Name.com, 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
- SRV
- ALIAS
CAA, PTR, DNAME, DS, DHCID, HTTPS, SVCB, TLSA, NAPTR aren't available
TTLs below 300s are raised
A typical NS1 zone at Name.com
Example records for example.com. Open any flagged row to read why it changed.
NS1 Name.com
- ExactA@
192.0.2.70
- ExactAAAA@
2001:db8::70
- ExactMX@
10 mx1.mail.example.net. +1
- ExactTXT@
"v=spf1 include:_spf.example.net -all"
- UnsupportedCAA@
Not migrated
Name.com doesn't support CAA records through its API.
- 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 Name.com | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Unsupported | CAA | @ | Not migrated | — | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect NS1
Connect NS1 with read-only access (API key).
- 2
Connect Name.com
Connect Name.com (Username + API token (Core API, HTTP Basic)). 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 Name.com
We snapshot the Name.com zone, write in batches, and leave NS1 untouched.
- 5
Verify
We query Name.com'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 NS1
- Records that use filter chains, answer metadata, data feeds or record links are copied as plain answers only and flagged in their comment. We never overwrite them on NS1.
- DNSSEC has to be available on the NS1 account before it can be turned on for a zone.
- NS1 changes one record set per request, so large zones take longer and count against the API rate limit.
Access we need: DNS → View zones for the preview; DNS → View zones and Manage zones to apply.
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.
Questions
Will there be downtime moving from NS1 to Name.com?
Not if both providers serve the same answers during the switch. The records are copied to Name.com 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 NS1?
No. We never write to NS1. 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 Name.com and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview