Try the NS Lookup

NS Lookup — Find the Authoritative Nameservers for Any Domain

By sadiqbd · June 6, 2026

NS Lookup — Find the Authoritative Nameservers for Any Domain

NS records are the first thing to check when a domain stops resolving

Every domain has nameservers — the authoritative DNS servers that hold the actual zone data for the domain. If the NS records are wrong, missing, or pointing to servers that don't have the zone configured, every DNS query for that domain fails. Websites go down. Email stops working. Everything breaks at once.

An NS lookup queries DNS to find which nameservers are authoritative for a domain — the essential first step in diagnosing any DNS problem.

What NS Records Are

NS (Name Server) records specify the authoritative nameservers for a domain. These are the servers that hold the official DNS records for that domain and answer queries about it.

NS record example:

example.com  NS  ns1.cloudflare.com
example.com  NS  ns2.cloudflare.com

Every domain must have at least two NS records — for redundancy. If the only nameserver goes down, the domain becomes unresolvable.

Where NS records come from:

NS records exist in two places:

  1. At the registrar — when you register a domain, the registrar publishes NS records in the parent TLD zone (.com, .net, .org, etc.). These are called "delegation records" and point the internet to your nameservers.
  2. In your DNS zone — your authoritative nameservers also host NS records within your own zone, called "authoritative NS records."

Both must be consistent for DNS to work correctly.

How NS Lookup Fits Into DNS Troubleshooting

When DNS fails for a domain, the NS lookup is step one:

  1. NS lookup → find the authoritative nameservers
  2. Query those nameservers directly → see what they actually serve
  3. Compare to what public resolvers return → identify propagation gaps

If the NS lookup returns unexpected nameservers (old provider after a migration, or incorrect delegation after a registrar transfer), that explains why DNS queries are failing.

How to Use the NS Lookup Tool on sadiqbd.com

  1. Enter the domain — e.g. example.com
  2. Run the lookup — the tool queries DNS for NS records
  3. Read the result — the authoritative nameservers are listed

Real-World Examples

Verifying a DNS migration

You've moved your DNS from GoDaddy to Cloudflare. Did the NS records update?

NS lookup for example.com returns:

ns1.cloudflare.com
ns2.cloudflare.com

Migration successful — the domain is now delegated to Cloudflare.

If the lookup still returns ns1.godaddy.com, nameserver propagation hasn't completed yet — or the registrar-level NS records weren't changed.

Diagnosing a complete DNS failure

A client's website and email are both completely down. DNS lookups for the domain return nothing.

NS lookup returns: ns1.expiredprovider.com, ns2.expiredprovider.com

Those nameservers are unreachable — possibly because the DNS hosting plan lapsed. Solution: log into the domain registrar and update NS records to a working nameserver.

Checking after a domain transfer

Domain was transferred from Registrar A to Registrar B. Did the transfer complete?

NS lookup returns the nameservers configured at Registrar B. Transfer confirmed. If it still shows Registrar A's nameservers, the transfer hasn't fully propagated or completed.

Understanding which provider controls DNS

You inherit a website and need to know who manages DNS (so you can make changes).

NS lookup returns: ruby.ns.cloudflare.com, todd.ns.cloudflare.com

DNS is managed through Cloudflare. Log into the Cloudflare account associated with this domain to make changes.

NS Records vs. MX Records vs. A Records

These are all DNS records but serve different purposes:

Record Purpose
NS Points to the authoritative nameservers that host all other DNS records
A Points the domain to an IPv4 address (web server, etc.)
MX Points to the mail servers for incoming email

NS records are the meta-layer — they tell the internet where to find all the other records. If NS is wrong, A, MX, and everything else is unreachable.

What Happens During DNS Delegation

When you type example.com in a browser:

  1. Your resolver asks the root servers: who handles .com?
  2. Root servers return the .com TLD nameservers
  3. Your resolver asks .com TLD: who handles example.com?
  4. .com TLD returns the NS records for example.com — the registrar's delegation
  5. Your resolver asks those nameservers: what's the A record for example.com?
  6. The authoritative nameserver returns the IP address

NS records are what makes step 4 work. Without them pointing to the right servers, the chain breaks.

Glue Records

A circular dependency can occur: if your nameserver's hostname is within the domain it's serving (e.g. ns1.example.com for the example.com zone), the resolver needs to know the IP of ns1.example.com to look up example.com — but to get that IP, it needs to query example.com.

This is resolved by glue records — A records published in the parent TLD zone alongside the NS delegation records, providing the nameserver IP directly without a circular lookup.

Glue records only matter when your nameserver hostnames are subdomains of the domain they serve. Third-party DNS providers (Cloudflare, Route 53, etc.) use nameservers on different domains, so glue records aren't an issue.

Tips for Managing NS Records

Always have at least two nameservers. Single nameserver = single point of failure. Every major DNS provider gives you at least two — use both.

Change NS records at the registrar, not just in your DNS zone. The NS records in your DNS zone are authoritative, but the NS records at the registrar (the delegation) are what the internet uses to find your zone. Both must be updated during a migration.

Expect 24–48 hours for NS record changes to propagate globally. NS record changes propagate slowly — the parent TLD zone caches delegation information with high TTLs. Plan migrations accordingly.

Don't delete old nameservers before new ones are confirmed working. Run both old and new nameservers simultaneously during a transition to avoid any gap in resolution.

Frequently Asked Questions

What's the difference between a domain registrar and a nameserver? The registrar manages domain registration (ownership and delegation). The nameserver stores and serves the actual DNS records for the domain. They're often separate services — you might register through GoDaddy but use Cloudflare's nameservers.

Why do NS records have two or more entries? Redundancy. If one nameserver is unreachable due to maintenance, network issues, or an outage, queries automatically fall over to the other nameservers. ICANN requires a minimum of two nameservers per domain.

If I change my nameservers, do I need to re-enter all my DNS records? Yes — DNS records are stored on the nameservers. When you switch providers, you need to recreate all your records (A, MX, TXT, CNAME, etc.) in the new nameserver before switching the NS delegation. If you switch before migrating records, DNS resolution fails.

How do I find out where to log in to change DNS records? Run an NS lookup. The nameserver hostnames tell you which provider manages DNS. Log into that provider's control panel.

Is the NS lookup tool free? Yes — completely free, no sign-up needed.

NS records are the foundation of DNS — and the first thing to verify when anything DNS-related breaks. The lookup tool gives you the current delegation for any domain in seconds, which is where any DNS troubleshooting should start.

Try the NS Lookup tool free at sadiqbd.com — find the authoritative nameservers for any domain instantly.

Try the related tool:
Open tool