NS Lookup
Find the authoritative nameservers for a domain, the servers that hold its DNS records.
What this tool checks
The NS lookup asks a public resolver (Cloudflare by default, or Google Public DNS or Quad9) for the NS records of a domain. These name the authoritative nameservers: the servers that hold the original copy of the domain’s zone and answer for it. Every other DNS record of the domain, from A to MX to TXT, comes from these servers.
The answer you get here is the NS set published at the apex of the zone, as cached by the resolver.
How to read the result
Each line shows a nameserver host name and its TTL, for example:
example.com. 86400 IN NS ns1.example.net.
example.com. 86400 IN NS ns2.example.net.
What to look for:
- At least two nameservers. RFC 1034 calls for at least two, so that one failure does not take the domain offline.
- Ideally on different networks. Most large providers run anycast networks, which spread each nameserver across many locations.
- Names you recognise. They should belong to the DNS provider you think you are using. Unexpected names after a migration mean the delegation was not updated.
- Long TTLs are normal. Nameservers rarely change, so 86400 seconds (one day) or more is common.
An NXDOMAIN status means the domain does not exist or is not delegated: it may be expired, suspended or not yet registered. Check it with the WHOIS lookup.
Delegation and zone: two copies of the NS set
NS records exist in two places:
- In the parent zone, such as
.com, as the delegation. You set these at your registrar. The WHOIS lookup shows them as the domain’s registered nameservers. - At the apex of your own zone, published by your DNS provider. This is what this tool shows.
Both lists should be identical. If they differ, resolvers may use either one, and your domain can behave differently for different users.
Before you change nameservers
Moving a domain to a new DNS provider is safe if you follow a simple order:
- Recreate every record at the new provider: web, mail (MX, SPF, DKIM, DMARC), verification records and any subdomains.
- Check the new zone by querying the new nameservers before the move. Many providers show a preview; the DNS lookup will show the result once the delegation changes.
- If the domain uses DNSSEC, remove the DS record at the registrar and wait for it to expire, or follow your providers’ documented key transfer.
- Change the nameservers at the registrar.
- Keep the old zone unchanged for at least two days, so resolvers that still use the old delegation get correct answers.
Common problems and fixes
- Nameservers changed in the zone but not at the registrar. The delegation did not move. Change the nameservers in your registrar’s control panel.
- New provider set at the registrar, old NS records left in the new zone. Update the apex NS records at the new provider so both sides match.
- A nameserver that does not answer for the zone (lame delegation). Remove it from the registrar’s list, or configure it to serve the zone. The propagation checker queries each authoritative nameserver directly and shows which ones fail.
- Nameservers inside the domain itself (
ns1.example.comforexample.com) stopped working after an IP change. Update the glue records at the registrar. - The domain stopped resolving after a provider change, and it uses DNSSEC. The DS record at the registrar still points to the old provider’s key. See DS and DNSKEY.
Going further
- The NS record guide explains delegation and glue in detail.
- The SOA record guide covers the zone’s serial number, which you can compare across nameservers with the propagation checker and type SOA.
- The DNS lookup can query any other record type once you know the nameservers are right.
Frequently asked questions
Is this the same as the nslookup command?
Not quite. The nslookup command can query any record type; this tool asks specifically for NS records, which list a domain's nameservers. For other types, use the DNS lookup tool.
How do I find out which company hosts my DNS?
The nameserver names usually reveal it, for example ns1.provider.example. The WHOIS lookup shows which registrar the domain is registered with, which may be a different company.
I changed nameservers at my registrar but the lookup still shows the old ones.
Delegation records in TLD zones often have TTLs of a day or two, and resolvers keep the old set until it expires. Also make sure the new zone's own NS records list the new servers.
Why do I get no NS records for www.example.com?
NS records exist at zone boundaries, normally only on the domain itself (the apex). A subdomain has its own NS records only if it is delegated to different servers.