Domains and DNS

What is a name server, and how do I find mine?

Name servers are the one WHOIS field that survived GDPR untouched and still tells you something real: they name the company actually operating the domain, whatever the registration says.

A name server is a DNS server that holds the authoritative records for your domain — the A, MX, TXT and CNAME entries that tell the internet where your website and email live. Your registrar publishes two or more of them into the TLD zone as the delegation for your domain, and every lookup in the world eventually ends up asking one of them. You can read yours from any WHOIS record, in the “Name Server” lines, or by querying the NS record directly.

Worked out 2026-09-10 (IST) · Standard gTLD delegation

How a lookup actually reaches you

A resolver asks a root server where .com lives.
The TLD server for .com replies with your domain’s delegation — its name servers.
The resolver asks one of your name servers for the record it wants.
Your name server answers authoritatively, with a TTL.
The resolver caches the answer for that TTL and serves it to everyone who asks.

Only step 3 is under your control, and only step 2 is under your registrar’s. That division explains most DNS confusion: the registrar controls which servers are authoritative, the DNS provider controls what they say.

Reading name servers to identify the host

Common name-server patterns
Name servers look like	Who that is
ns1.digitalocean.com, ns2…	DigitalOcean DNS
<name>.ns.cloudflare.com	Cloudflare — note the zone is proxied or at least hosted there
ns-<n>.awsdns-<n>.com/.net/.org/.co.uk	Amazon Route 53
ns1.bigrock.in, ns2.bigrock.in	BigRock — common on Indian small-business domains
dns1.registrar-servers.com	Namecheap default DNS
ns<n>.hostinger.com / ns<n>.hostgator.in	Shared hosting, DNS bundled with the plan
pdns<n>.ultradns.net	Enterprise managed DNS
ns1.sedoparking.com, ns<n>.above.com, ns<n>.dan.com	Parked — the domain is for sale

Before you change them

Export the whole zone first. Every A, AAAA, CNAME, MX, TXT and SRV record. The new provider starts empty, and anything you forget simply stops existing.
Recreate mail records before the switch, not after. MX, SPF, DKIM and DMARC. Mail sent during a gap bounces, and bounced mail is not retried forever.
Carry over verification TXT records. Google Workspace, Microsoft 365, Search Console and payment providers all hold a domain hostage to a TXT record you will not remember creating.
Expect the TLD zone TTL, not yours. Delegation records commonly carry a 24 to 48-hour TTL, so run both providers in parallel for two days.

Sources: RFC 1034 delegation model; ICANN registry requirements on minimum name-server counts.

Check your own numbers

Query the NS records for any domain and see the full authoritative set.

DNS LookupA, AAAA, MX, NS, TXT and CNAME records, live from the resolver.

Frequently asked

How many name servers should a domain have?

At least two, on separate infrastructure - that is the point of them. Most registries require a minimum of two and allow up to thirteen. Two well-run anycast name servers beat five on the same rack in the same building, because the failure you are guarding against is that building.

What is the difference between changing name servers and changing DNS records?

Changing a record - pointing the A record at a new IP - is a small edit inside your current DNS provider and it takes effect within the record TTL. Changing name servers moves the entire zone to a different provider and every record must exist at the new one before you switch, or everything breaks at once. The first is routine; the second is a migration.

Can I use my hosting company's name servers with a domain bought elsewhere?

Yes, and it is the normal arrangement. Registration and DNS are separate services. You set the name servers your host gives you in the registrar control panel, the registrar publishes them into the TLD zone, and the host answers all lookups from then on.

Why does WHOIS show name servers that are not mine?

Three usual causes: the change has not reached the TLD zone yet, which takes minutes to hours; the domain is parked by the registrar because it expired or was never configured; or somebody else controls the registrar account. If it is the third, treat it as a security incident and reset the registrar credentials first.

Need domain and DNS checks inside your own product?

We build WHOIS, RDAP, DNS and SSL lookups as embeddable widgets or a plain JSON API in your branding, wired to your own lead form. Tell us which checks you need and we will send a working demo.