A record was added, but the domain still does not resolve and you need to confirm which nameservers are actually authoritative.
NS Lookup Tool
Check which nameservers are authoritative for a domain.
Use this NS lookup tool to verify delegation, confirm which nameservers are active for a domain, and catch mismatches between your registrar settings and the DNS provider you think is serving the zone.
Verify nameserver delegation before changing records or troubleshooting propagation.
Lookup result
example.com
NOERROR
Type Value TTL
No nameservers were returned for this query by the resolver.
What this NS lookup tool does
NS Lookup queries the nameservers returned for a domain so you can confirm which nameserver set is currently authoritative.
Use it to verify delegation, confirm whether the domain points to the DNS host you expect, and identify whether a registrar or migration mismatch is blocking the rest of your DNS troubleshooting.
It does not confirm that the records inside the zone are correct by itself. After NS Lookup, you usually need DNS Lookup or propagation checks next.
When to use this tool
You recently moved DNS providers and want to verify whether delegation changed cleanly.
Different tools show conflicting answers and you need to confirm whether the domain points to the expected nameserver set.
A domain works in one place but not another, and you suspect a delegation or registrar mismatch.
Certificate, email, or website changes are not visible because updates may have been made in the wrong DNS zone.
You need a fast delegation check before moving on to SOA, propagation, or DNSSEC troubleshooting.
How to use NS Lookup
- Enter the root domain you want to check.
- Run the NS lookup and review the returned nameserver set.
- Compare the nameservers with the registrar and DNS provider you expect to be active.
- Check whether all returned nameservers look correct and consistent.
- If they look wrong, verify registrar delegation before changing records in the zone.
How to interpret NS lookup results
NS records returned
Likely meaning: The resolver returned one or more nameservers for the queried domain.
Common causes: This usually means delegation exists and the domain points to a defined authoritative nameserver set.
Next action: Compare the returned nameservers with the registrar and the DNS host you expect to be authoritative.
Nameservers unexpected
Likely meaning: NS records were returned, but they are not the nameservers you expected.
Common causes: This often happens during migrations, registrar misconfiguration, or when updates were made in the wrong provider.
Next action: Check registrar delegation first, then verify which provider hosts the active zone.
Multiple nameservers returned
Likely meaning: The domain delegates to more than one authoritative nameserver.
Common causes: This is normal, but problems can appear if one nameserver is stale or serving different data.
Next action: Verify the set is complete and consistent across all authoritative servers.
No NS record found
Likely meaning: The lookup did not return delegation data for the queried name.
Common causes: The domain may not exist, the query may be for the wrong name, or there may be delegation issues higher in the DNS chain.
Next action: Check the exact domain name, then compare with DNS Lookup and registrar configuration.
NXDOMAIN
Likely meaning: The queried domain does not exist in DNS.
Common causes: Common reasons are typos, expired domains, wrong hostname level, or querying a name that was never created.
Next action: Confirm the domain spelling and whether the zone exists at all before troubleshooting delegation.
SERVFAIL
Likely meaning: The recursive resolver could not complete the NS query successfully.
Common causes: This often points to broken delegation, DNSSEC failures, or authoritative server issues.
Next action: Check DNSSEC, verify authoritative nameserver health, and compare with other resolvers.
Timeout or no response
Likely meaning: The resolver did not return an answer in time.
Common causes: Authoritative nameservers may be unreachable, overloaded, or blocked along the network path.
Next action: Retry and then verify nameserver reachability and network path conditions.
Common DNS issues this tool helps uncover
Registrar nameservers do not match the DNS provider you are editing
Partial DNS migration where one provider still serves stale data
Delegation is correct, but one authoritative nameserver has inconsistent records
DNSSEC breaks resolution even though NS records are present
Zone edits were made in a non-authoritative provider account
Subdomain delegation assumptions are wrong and the wrong name is being checked
Resolver cache or propagation hides a recent nameserver change
Authoritative nameservers respond inconsistently by location or network
Next steps after NS Lookup
Check DNS Lookup
Once delegation looks correct, verify the active records actually being served for the domain.
Check DNS propagation
Use this after registrar or nameserver changes when some resolvers may still show older delegation.
Validate DNSSEC
If delegation looks right but resolution still fails, DNSSEC may be blocking answers.
Move to service checks
After delegation and DNS records are confirmed, continue to website, email, or network-level checks.
Related tools
DNS Lookup
Query A, AAAA, CNAME, TXT, and other DNS records for a domain.
DNS Propagation Check
Verify whether recent DNS changes are visible across resolvers.
DNSSEC Check
Validate whether a domain has DNSSEC configured correctly.
MX Lookup
Inspect mail exchange records and delivery destinations for a domain.
Ping
Check whether a host responds and measure round-trip latency.
HTTP Check
Review HTTP response status, headers, and redirect behavior.
NS Lookup FAQ
What does NS Lookup check?
It checks which nameservers are returned for a domain so you can confirm delegation and identify which DNS provider is authoritative.
What input should I enter?
Enter the root domain such as example.com. NS checks are usually most useful at the zone level rather than for full URLs.
Why are the nameservers different from the provider I expected?
The registrar may still point to an older provider, or the active domain delegation may not have been updated after a migration.
What should I check after NS Lookup?
Usually DNS Lookup, propagation, SOA consistency, and DNSSEC if resolution errors continue.
How is NS Lookup different from DNS Lookup?
NS Lookup checks delegation. DNS Lookup checks the records being served for a hostname or domain.