DNS NS Record Lookup: Find Nameservers for Any Domain

NS records (Nameserver records) identify which DNS servers are authoritative for a domain. They are the starting point of all DNS resolution: before any A, MX, or TXT record can be found, the resolver first queries the domain's NS records to know which nameservers to ask. Knowing your NS records is essential when managing domains, migrating hosts, or diagnosing DNS issues.

How to Look Up NS Records

1. Enter the domain name — Type the domain you want to inspect (e.g., cloudflare.com).
2. Select NS from the dropdown — Filter results to show nameserver records only.
3. Click Lookup — The tool returns a list of authoritative nameservers for that domain.
4. Check for consistency — Multiple NS records are normal and expected; they provide redundancy.

Example: Querying NS Records

# Using dig
dig example.com NS

# Using nslookup
nslookup -type=NS example.com

# Example output:
# example.com.   86400  IN   NS   ns1.exampledns.com.
# example.com.   86400  IN   NS   ns2.exampledns.com.

Why Check NS Records?

• Confirm nameserver migration — After pointing a domain to a new registrar or DNS provider, NS record lookups confirm the change has propagated.
• Identify the DNS provider — NS records reveal which company manages a domain's DNS (e.g., Cloudflare, AWS Route 53, GoDaddy).
• Troubleshoot resolution failures — If a domain is unreachable, checking NS records ensures the authoritative servers are correctly set.
• Verify subdomain delegation — Subdomains can delegate to different nameservers using NS records at the zone level.

NS Records and Domain Delegation

When you register a domain, the TLD registry (like Verisign for .com) stores your NS records. These point to your authoritative nameservers — the servers that know the full DNS zone for your domain. If these NS records are wrong or outdated, no one can resolve your domain correctly, regardless of what other DNS records you have.

How Long NS Changes Take

NS record changes can take 24–48 hours to propagate globally because the TLD registry must update its records, and resolvers cache the old NS data based on the previous TTL. During a migration, you may see different NS records depending on which resolver you query. This is normal and resolves as caches expire.

Use the DNS Lookup tool to look up NS records and see exactly which nameservers are authoritative for any domain.