To check a domain’s nameservers, look up its NS records: use our DNS Lookup, run nslookup -type=ns example.com on Windows or dig NS +short example.com on macOS and Linux. The nameservers that actually count are the ones stored at the registry for the domain’s extension; a WHOIS lookup or a query to the TLD servers shows them, which is the reliable way to confirm a nameserver change.
Online
Enter the domain in DNS Lookup and look at the NS section. For a fuller check — whether the parent zone and your own nameservers agree, whether glue records exist and whether every nameserver answers — run a DNS Report. The registrar-side value appears in WHOIS as Name Server.
From the command line
nslookup -type=ns example.com
dig NS +short example.com
Resolve-DnsName example.com -Type NSRegistrar, registry and DNS host
| Role | What it does | Where you change it |
|---|---|---|
| Registrar | Where you bought the domain | Your account at the registrar (e.g. GoDaddy, Namecheap) |
| Registry | Runs the extension (.com, .org, .tr…) and publishes the delegation | Updated by the registrar on your behalf |
| DNS host | The nameservers that answer for your records (A, MX, TXT…) | The DNS provider’s panel (Cloudflare, your hosting panel…) |
When you “change nameservers” you edit the delegation at the registrar, which passes it to the registry. Your records then have to exist at the new DNS host, otherwise the domain stops resolving.
Has my nameserver change taken effect?
- Ask the TLD servers directly:
dig NS example.com @a.gtld-servers.netfor .com and .net domains. If they return the new nameservers, the registry has the change. - Check public resolvers: DNS Propagation Checker shows what several resolvers around the world return. Old answers can stay cached for up to the TTL of the NS record, often 24–48 hours.
- Query the new nameservers:
dig example.com @new-ns.example.netshould return your records. If it does not, the zone is missing at the new host.
Why the change takes time is explained in understanding DNS propagation.
Common problems
- Only one nameserver: use at least two, ideally on different networks.
- Nameservers on your own domain (ns1.example.com for example.com) need glue records at the registrar.
- Different NS records at the parent and at your DNS host: the parent wins for new lookups; keep both identical. A DNS Report shows mismatches.
- DNSSEC enabled at the registrar but not at the new host makes the domain fail to resolve for validating resolvers. Remove the DS record before moving, or set up DNSSEC at the new host first.
Common Questions
How long does a nameserver change take?
The registry usually publishes it within minutes to a few hours. Resolvers that cached the old nameservers can keep using them for up to 24-48 hours.
Why does WHOIS show different nameservers than a DNS lookup?
WHOIS shows the delegation stored at the registry, while a DNS lookup may still return cached NS records. If they differ after a change, wait for the TTL to expire.
Can I check the nameservers of any domain?
Yes. Nameservers are public information needed for the domain to work.
What happens if a nameserver is down?
Resolvers try the other nameservers, so a single failure is usually invisible. If all of them fail, the domain stops resolving.