NS Lookup (Nameserver Checker)

What is an NS Lookup?

An NS lookup (nameserver lookup) queries the DNS system for NS records — the records that identify which authoritative nameservers are responsible for a domain's DNS zone. NS records are the foundation of DNS: they tell the global internet where to ask when resolving records for a domain.

Every domain registered with a registrar has at least two NS records pointing to authoritative nameservers. When a resolver needs to look up example.com, it asks the .com TLD servers for the NS set, then sends its query directly to one of those nameservers. The answer returned by the authoritative nameserver is final — not cached from elsewhere.

Major DNS Providers — NS Record Formats

Each DNS provider uses a distinct nameserver hostname pattern. Identifying the pattern in an NS record immediately tells you which provider hosts the zone.

If the NS records do not match your intended provider, the DNS zone is being served by the wrong authoritative server — all subsequent record changes to your intended provider will have no effect.

Why NS Records Matter

• DNS migrations: when you move between providers, you update NS records at the registrar. Until propagated, the old provider remains authoritative — changes at the new provider are invisible to most resolvers.
• Propagation debugging: if your NS set is wrong, no amount of waiting will fix propagation — resolvers are querying the wrong authority.
• Incident response: unexpected NS changes are a sign of domain hijacking. Verify NS records during any DNS incident before chasing A or MX records.
• Email deliverability: MX records are served by the authoritative nameserver. Wrong NS = wrong MX = mail delivery failures.

How to Change Nameservers

Changing authoritative nameservers is done at the registrar (e.g., GoDaddy, Namecheap, Google Domains), not at the DNS provider. The process:

1. Replicate all existing DNS records at the new provider before changing NS. Missing records cause outages.
2. Lower the TTL on your current NS records to 300s (5 minutes) 24–48 hours in advance so old NS caches expire quickly after the switch.
3. Log into your registrar and update the nameserver fields to the new provider's NS hostnames.
4. Verify with NS Lookup that resolvers worldwide are returning the new NS set.
5. Monitor A, MX, and TXT record resolution for 24–48 hours post-cutover.

Authoritative vs Recursive DNS

Authoritative nameservers host the zone file and return final answers. Recursive resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, ISP resolvers) query authoritative servers and cache results for users. NS Lookup queries both to show the delegated authority (from the TLD) and the live NS records.

CLI Commands