Nameservers ending in name.com mean the domain’s DNS is at Name.com. The account shows ns1 to ns4.name.com, but the domain’s records may show per-customer names like ns1dns.name.com — both are right.
| Whose | Name.com — Registrar |
| Nameservers | ns1 to ns4.name.com — or ns1dns, ns2nsy … .name.com |
| How they are given | Four per domain |
| DNSSEC | No, not on Name.com’s nameservers |
Does your domain use Name.com’s nameservers?
Enter a domain: we ask its registry which nameservers it hands out, ask each of them for the zone, and say whose they are — and whether any does not answer or disagrees.
The names
The account shows ns1 to ns4.name.com; in the domain’s records they can appear as per-customer names such as ns1dns.name.com — both are Name.com’s:
ns1.name.com
ns2.name.com
ns1dns.name.com
ns2nsy.name.com
Where to see and change them
My Domains, the domain, Domain Actions, Manage Nameservers: Default Nameservers, or delete all and add your own.
Common mistakes
- Adding new nameservers without deleting the old ones: the website and email stop working.
- Editing records at Name.com while the domain uses other nameservers: they have no effect.
Also: Turning on DNSSEC at Name.com.
Sources
Checked on 27 September 2026 against these official sources:
- Viewing your domain nameservers — name.com
- Seeing different nameservers in Whois records — name.com
- Changing nameservers for DNS management — name.com