NS Lookup
Find the nameservers returned by a public recursive resolver.
01 / QUERY RESULTS
Ready for a queryYour DNS answer will appear here.
Enter a name, choose a record type, then look it up. There are no live results yet.
Nameservers and zones
NS records identify nameservers for a DNS zone. Enter the exact domain you want to inspect. A subdomain may have a separate delegation or may be served by its parent zone; not every hostname publishes its own NS set.
The selected recursive resolver returns these records. This browser tool does not open direct UDP or TCP DNS connections to each authoritative nameserver.
example.com. 86400 IN NS ns1.example.net.
example.com. 86400 IN NS ns2.example.net.
DOCUMENTATION EXAMPLE — not a live DNS responseWhy nameserver addresses are separate
Supplemental A and AAAA queries show addresses attached to returned nameserver hostnames. Returned Additional records are retained in response details if the resolver provides them.
An address lookup is not evidence of parent-zone glue consistency. The first version does not query the parent and child zones directly or assert that every nameserver is reachable.
Delegation checks need more evidence
A recursive NS answer alone cannot establish that parent and child NS sets agree. It cannot establish zone transfer availability, serial synchronization or authoritative DNSSEC validity either.
If you recently moved DNS providers, compare the registrar’s configured delegation and the intended DNS zone. Do not remove old infrastructure solely because one public cache has changed.
What if no NS records appear?
A hostname below a zone apex may have no NS records of its own. NOERROR without records is therefore not enough to diagnose a broken delegation.
SERVFAIL may involve upstream availability, validation or other resolver conditions. The raw response and DNS flags provide evidence, but AD=false alone is not a DNSSEC failure.