Nameservers tell the world where your domain's DNS records live. You need to know them when you move hosting, fix email problems or find out who manages a domain's DNS.
Method 1: Nameserver checker
Our nameserver checker lists the nameservers and also tests each one, showing its IP address, response time and zone serial number.
Method 2: WHOIS lookup
The WHOIS lookup shows the nameservers registered at the registry. These are the "delegated" nameservers, the ones the domain officially uses.
Method 3: DNS lookup (NS records)
The DNS lookup with the NS type shows the nameservers that the domain's own zone declares. They should match the registry list.
What to compare
- Registry vs zone: if the WHOIS nameservers and the NS records differ, there is a configuration mismatch.
- At least two nameservers: one is a single point of failure.
- Different networks: two servers on the same network can fail together.
- Same serial number: different serials mean a nameserver is out of sync.
What to do with nameserver information
- Moving hosting: change them to the ones in your hosting welcome email. See how to point a domain to hosting.
- Identifying the DNS host: nameservers like ns1.provider.com show who runs DNS.
- Troubleshooting: confirm that changes made at the registrar have been accepted.
Private (custom) nameservers
Hosting resellers sometimes use nameservers on their own domain, such as ns1.yourbrand.com, so customers see the reseller's brand. These need "glue records" at the registry that map the nameserver name to an IP address.
Reading nameservers like a detective
Nameserver names often reveal who runs the DNS. Names like ns1.somehost.com point to a hosting company. Names containing a CDN or DNS brand show that DNS is handled by a specialist service. If the nameservers use the domain itself (for example ns1.yourbrand.com) the owner runs private nameservers, common among hosting resellers.
Why registry and zone nameservers can differ
The registry holds the official delegation; the zone itself lists NS records too. If someone changed the zone at one provider but not the delegation at the registry, visitors still reach the old servers. When the two lists disagree, update the registrar so it matches the DNS host you actually want to use.
Quick fixes for common situations
- One nameserver does not respond: contact the DNS host or switch to a provider with reliable servers.
- Different serial numbers: wait a few minutes and test again; if it persists, the secondary is not syncing.
- Nameserver has no IP: a private nameserver needs glue records at the registrar.
FAQ
How many nameservers should I use?
At least two. Many providers give you two to four.
Why do I see nameservers I did not set?
Your domain may have DNS hosting at a registrar, CDN or hosting provider. Check your registrar account.
How long does a nameserver change take?
Usually minutes to hours, up to 48 hours. See DNS propagation.
Try it now: use our free WHOIS lookup, DNS lookup, nameserver checker, SSL checker and IP & hosting lookup. All free, no signup.