NS Lookup

Query Nameserver (NS) DNS records for any domain — see authoritative name servers and SOA data

Try:

Frequently Asked Questions

An NS (Nameserver) record specifies which DNS servers are authoritative for a domain — meaning they hold the official DNS records (A, MX, TXT, etc.) for that domain. When a resolver wants to look up any record for example.com, it first queries the NS records to find out which server to ask.

The SOA (Start of Authority) record contains administrative information about the DNS zone: the primary nameserver, the admin email address, the serial number (used for zone transfers), and timing values like refresh, retry, and expire intervals. The serial number increments every time DNS records are updated.

Nameservers are set at your domain registrar (e.g. GoDaddy, Namecheap, Google Domains). Log in to your registrar's control panel, find the domain, and update the nameserver fields to the new values provided by your DNS hosting provider (e.g. Cloudflare: anita.ns.cloudflare.com). Changes can take up to 48 hours to propagate globally.

The nameserver hostname reveals the provider: ns.cloudflare.com = Cloudflare, awsdns = Amazon Route 53, domaincontrol.com = GoDaddy, dnsimple.com = DNSimple, googledomains.com or ns-cloud = Google Cloud DNS, name.com = Name.com.

Nameservers are the DNS servers that hold the authoritative DNS records for a domain. When anyone in the world looks up a record for your domain, the DNS lookup chain ultimately ends at your authoritative nameservers. They are provided by your DNS hosting provider and are listed in the domain's NS records, delegated by the TLD registry.

An authoritative nameserver holds the official DNS records for a domain and only answers questions about domains it has been delegated authority over. A recursive nameserver (resolver) performs lookups on behalf of clients by querying root, TLD, and authoritative servers. Examples: 8.8.8.8 (Google), 1.1.1.1 (Cloudflare).

NS record propagation typically takes 24–48 hours to complete worldwide, though it often completes in a few hours. The delay is caused by the TTL of the old NS records cached at resolvers. To minimize disruption, ensure your new nameservers have all your DNS records ready before making the change at the registrar.

Glue records solve a chicken-and-egg problem. If your nameservers are subdomains of your own domain (e.g. ns1.example.com for example.com), a resolver can't look up the NS record without first knowing the IP. The glue record is an A record stored at the TLD registry level that provides the IP of your nameservers directly, breaking the circular dependency.

ICANN requires domains to have a minimum of two nameservers for redundancy. If a domain only had one nameserver and it went offline, the entire domain would become unresolvable. Most DNS providers provision at least two nameservers, often spread across different geographic locations for maximum resilience.

mname: Primary nameserver. rname: Admin contact email (dot-encoded). serial: Zone version number. refresh: How often secondaries check for updates. retry: Retry interval if refresh fails. expire: How long secondaries serve the zone without refresh. minimum: Default TTL for negative caching.

About This NS Lookup

This free NS Lookup tool queries DNS Nameserver and SOA records in real time for any domain. It returns all authoritative nameservers with their IP addresses, and includes SOA (Start of Authority) zone metadata such as the serial number, refresh interval, and admin contact — useful for verifying DNS hosting and diagnosing zone propagation.

When to use this tool

Verify that nameserver changes have propagated after an update
Identify the DNS hosting provider for any domain
Check NS records after a domain transfer or registrar change
Audit the SOA serial number to confirm zone updates

SOA Record Fields

Field	Description
mname	Primary nameserver for the zone
rname	Admin contact email (dot-encoded)
serial	Zone version number — incremented on each change
refresh	How often secondaries check for zone updates (seconds)
retry	Retry interval if a refresh fails (seconds)
expire	How long secondaries serve the zone without a refresh
minimum	Default TTL for negative (NXDOMAIN) caching

Standards & References

In-depth guides and technical articles.

View all →

Internet Sep 18, 2026

Your NS Records Exist Twice — and They Might Disagree

NS records live in two places — the parent zone and your own. When they disagree, or when glue goes stale, the domain resolves for some people and not others.

Internet Jul 18, 2026

Why 1.1.1.1 Reaches Different Servers Worldwide — Anycast, DNS Propagation, and the 13 Root Nameservers That Are Really 1,500

Anycast routing means Cloudflare's 1.1.1.1 reaches different physical servers in different locations — which is why DNS changes propagate to some locations before others, and why checking propagation from multiple places gives different results. Here's how anycast works, why the "13 root nameservers" are actually 1,500+ nodes, the TTL change timing strategy for planned migrations, and why single-provider DNS isn't genuine redundancy.

Internet Jun 23, 2026

Changing Nameservers Transfers Authority for Your Entire Domain — Here's Why That Makes NS Hijacking Uniquely Dangerous

Changing nameservers transfers authority for your entire domain — website, email, subdomains, authentication records — to whoever controls the new nameservers. Here's how nameserver hijacking works (registrar account compromise, social engineering of registrar support), what registry locks actually protect against, the glue record attack surface that bypasses NS monitoring, and why proactive NS record monitoring is the minimum security practice for business-critical domains.

Internet Jun 19, 2026

Multiple Nameservers, One Provider: Why "Redundant" DNS Isn't Always as Redundant as It Looks

A domain can have multiple nameservers, all responding correctly, all passing every lookup test — and still go fully offline the moment one provider has a bad day, if all those "multiple" nameservers belong to the same provider's infrastructure. Here's the single-provider redundancy illusion, how genuine multi-provider DNS requires keeping zone data synchronized, and how Anycast architecture explains why most single-provider setups are, in practice, quite resilient anyway.

Internet Jun 16, 2026

Glue Records and DNS Delegation: Why Changing Nameservers Can Silently Break a Domain

A nameserver named ns1.example.com creates a circular dependency — to find its IP, you'd normally ask example.com's nameservers, which it is one of. Glue records solve this by storing nameserver IPs directly in the parent zone. Here's how delegation chains work, when glue is required vs unnecessary, and why stale glue at the registrar causes confusing migration failures.