NS Lookup Guide: How to Check a Domain's Nameservers
An NS lookup shows you which nameservers hold authority over a domain's DNS zone. This single check often reveals the root cause of a stubborn "site not found" error, and it confirms whether a hosting or DNS provider migration has actually taken effect. This guide explains what NS records do and how to read the results of an NS lookup.
What is an NS record?
An NS, or nameserver, record names the servers that store the authoritative, current copy of a domain's DNS zone. Every other DNS record for that domain, including its A, MX and TXT records, ultimately lives on those nameservers. When a resolver anywhere on the internet needs to look up your domain, it eventually asks one of these nameservers for the answer.
Why nameservers and hosting are not the same thing
A domain's nameservers and its web hosting often come from the same company, but they do not have to. A domain's NS records can point to one provider's DNS service, such as Cloudflare, while the actual website lives on a completely different server, as long as the DNS zone's A or CNAME records point to the right place. Understanding this distinction helps when you troubleshoot a site that will not load even though the hosting account looks correct.
When to run an NS lookup
- After switching web hosts. Confirm the domain now points at your new host's nameservers instead of the old ones.
- After switching DNS providers. Verify that a change you made at your registrar, for example moving DNS management to Cloudflare, has actually taken effect.
- When a domain will not resolve. If NS records are missing, incorrect, or point to nameservers that no longer respond, nothing else in the DNS zone can resolve either.
- As a redundancy check. Best practice calls for at least two nameservers, ideally on separate networks, so the domain stays reachable if one nameserver goes offline.
How to read your results
Run our free NS Lookup tool and it returns each nameserver along with its resolved IP address and TTL. Most registrars and DNS providers assign between two and four nameservers by default. Two is the practical minimum for redundancy, and adding more than four rarely brings any real benefit for a typical website.
If the nameservers shown do not match what you configured at your registrar, do not assume something is broken immediately. Nameserver changes carry their own TTL and can take up to 48 hours to propagate fully, since every resolver on the internet caches NS records independently. Our DNS records guide explains TTL and propagation in more detail.
Pair it with a full health check
An NS lookup answers one specific question well, but it will not catch every DNS issue on its own. For a broader view that also covers mail servers and email authentication, run our DNS Health Checker, or read the accompanying guide to understand what each check means.
Try it yourself
Check any domain's nameservers right now with the NS Lookup tool. If the domain also needs to receive email, follow up with our MX Lookup tool to confirm its mail servers work correctly too.
Back to all posts