Skip to content
IPeek

NS Lookup

Authoritative name servers

Checking…

What is an NS record?

NS (Name Server) records list the authoritative name servers for a domain — the servers that hold its DNS zone and answer queries about it. They are set at the registrar and delegate DNS resolution to your provider. Get them wrong and the entire domain can stop resolving, taking your website and email down with it.

How NS records delegate DNS authority

DNS is a hierarchy. When a resolver looks up your domain, it asks the parent zone — the .com servers, say — which name servers are authoritative. The parent answers with your NS records, and the resolver then queries those servers directly for the actual records. This handoff is called delegation. The NS records exist in two places: at the registrar (the parent delegation) and inside your own zone. Both should agree, or you risk inconsistent and unreliable resolution.

How to read your NS lookup results

IPeek returns the authoritative name servers published for the domain, typically two to four hostnames such as ns1.example-dns.com and ns2.example-dns.com. Confirm they match your DNS provider — Cloudflare, AWS Route 53, your registrar's own service, or a self-hosted setup. Most providers assign a fixed set, so a mismatch suggests an incomplete migration or a hijack. More than one name server is expected and healthy; it provides redundancy. If results look wrong, compare them against what your registrar shows.

Common NS problems and how to fix them

The classic mistake is a delegation mismatch: the registrar points to one set of name servers while your zone lists another, causing intermittent failures as resolvers reach different servers. After moving DNS providers, update the NS records at the registrar and wait for the change to propagate before decommissioning the old zone. Having only one name server is fragile — add at least a second for redundancy. Lame delegation, where a listed server does not actually serve the zone, also breaks resolution and should be removed.

Frequently asked questions

What is the difference between NS records and a registrar?

The registrar is where you register and manage the domain, while NS records name the servers that actually answer DNS queries for it. At the registrar you set which name servers are authoritative; those servers, run by your DNS provider, hold the zone with your A, MX and other records. The two roles can belong to different companies.

How many NS records should a domain have?

A domain should have at least two name servers for redundancy, and many providers assign three or four. Multiple name servers ensure that if one is unreachable, resolvers can still get answers from another. Relying on a single name server is a single point of failure that can take the whole domain offline.

Why do my NS records differ between the registrar and the zone?

This is a delegation mismatch, and it usually means a migration was left incomplete. The registrar's NS records control the actual delegation from the parent zone, so resolvers follow those. The NS records inside your zone should match them. Align both sets to avoid intermittent resolution failures.

How long do NS record changes take to propagate?

NS changes at the registrar propagate through the parent zone and can take from a few hours up to 48 hours, depending on TTLs and registry processing. During this window, resolvers may use either the old or new name servers. Keep both sets serving identical records until propagation completes to avoid downtime.

What happens if NS records are wrong?

Incorrect NS records can make the entire domain fail to resolve, taking down the website, email and every other service that depends on its DNS. Because NS records control delegation, an error here is more severe than a single bad record. Always verify changes with a fresh lookup before retiring old name servers.