NS Lookup

Find the authoritative nameservers for any domain — returned with nameserver hostname and TTL in seconds.

More Tools

NS Lookup — What It Is and What It Returns

NS lookup queries the Domain Name System for the NS (Name Server) resource records defined in RFC 1034 and RFC 1035. NS records identify which name servers are authoritative for a domain — these servers hold the zone file containing all other DNS records for that domain, including A, MX, CNAME, and TXT records. A lookup returns one or more nameserver hostnames and their TTL, expressed in seconds.

Field	Meaning	Example
Record Type	Always NS — indicates a Name Server record	NS
Nameserver	Fully qualified hostname of the authoritative name server	ns1.google.com
TTL	Time to live in seconds — how long resolvers cache this record before re-querying	86400 (24 hours)

How to Use the NS Lookup Tool

Enter any domain name and run a live NS record query in seconds.

Enter a Domain Name

Type any domain name into the input field — e.g., google.com, github.com, or mail.example.com.

Choose a DNS Resolver

Select Google, Cloudflare, Quad9, OpenDNS, Yandex, or Authoritative DNS from the dropdown menu.

Run the Lookup

Click 'Lookup NS Records' to send a live UDP query to the selected resolver.

Read the Nameserver Results

Each row in the results table shows one NS record — the nameserver hostname and its TTL in seconds.

Use Authoritative DNS for Uncached Results

Select Authoritative DNS to bypass recursive resolvers and query the domain's own name servers directly.

Recursive vs Authoritative Mode — Which Resolver to Use

NS lookup results can differ depending on the DNS resolver selected. Recursive resolvers such as Google (8.8.8.8) and Cloudflare (1.1.1.1) may serve cached NS records up to the record's TTL. Authoritative DNS mode bypasses all intermediate caching by discovering the domain's own name servers first and querying them directly.

Diagram: a recursive resolver may answer NS records from cache up to the TTL; authoritative mode asks 8.8.8.8 for the NS records, resolves them and asks those servers directly for a live answer — Recursive answers may be cached; authoritative mode reads the zone’s current truth.

The authoritative discovery process runs in two steps: first, Google 8.8.8.8 is queried for the domain's NS records; each NS hostname is then resolved to an IP address via an A record lookup; those name server IPs are queried directly per RFC 1035. This guarantees a live, uncached response from the zone's primary source of truth.

Resolver	IP Address	Query Type	May Be Cached?
Google	8.8.8.8	Recursive	Yes — up to TTL
Cloudflare	1.1.1.1	Recursive	Yes — up to TTL
Quad9	9.9.9.9	Recursive	Yes — up to TTL
OpenDNS	208.67.222.222	Recursive	Yes — up to TTL
Yandex	77.88.8.8	Recursive	Yes — up to TTL
Authoritative DNS	Domain's own NS servers	Direct zone query	Never — live zone data

Do it yourself

How to Look Up NS Records Without an Online Tool

All major operating systems include command-line DNS tools that can query NS records directly. The online tool queries from a neutral external resolver — results may differ from your local resolver due to caching.

Windows Command Prompt

nslookup -q=ns google.com
nslookup -q=ns google.com 8.8.8.8
nslookup -q=ns google.com 1.1.1.1

Use -q=ns to explicitly request NS records. Append a resolver IP address after the domain name to query a specific DNS server — e.g. Google (8.8.8.8) or Cloudflare (1.1.1.1).

Windows PowerShell

Resolve-DnsName google.com -Type NS
Resolve-DnsName google.com -Type NS -Server 8.8.8.8
Resolve-DnsName google.com -Type NS -Server 1.1.1.1

Mac / Linux dig

dig google.com NS
dig google.com NS @8.8.8.8
dig google.com NS @1.1.1.1
dig google.com NS +short

dig is the preferred tool for sysadmins and developers — it exposes the full NS response including TTL, response flags, and the authority section. The +short flag returns nameserver hostnames only, without the full answer block. On macOS, dig is pre-installed. On Ubuntu/Debian, install it with apt install dnsutils.

Common Uses for NS Lookup

Verifying a domain registrar transfer. When moving a domain to a new registrar or hosting provider, the name servers must be updated at the registrar level. A migration that fails silently typically means the NS records have not propagated. Running an NS lookup against multiple resolvers — including Authoritative DNS — confirms whether the new name servers are live before further troubleshooting.

Diagnosing email delivery failures. Before investigating MX records, the name servers must be reachable and returning correct zone data. A mail server administrator investigating bounce messages typically starts with NS lookup to confirm the domain is delegated correctly, then proceeds to MX lookup and reverse DNS verification.

Detecting unauthorized DNS changes. A security engineer conducting a routine domain audit uses NS lookup to verify that the authoritative name servers match the approved registrar configuration. Unexpected name servers — particularly those pointing to unknown providers — may indicate DNS hijacking or an unauthorized domain transfer.

Frequently Asked Questions

What is the difference between a nameserver and a DNS record?

An NS record is a type of DNS record that identifies which servers are authoritative for a domain. A nameserver is the actual server those NS records point to — it stores and serves all other DNS records for the domain, including A, MX, CNAME, and TXT records. The NS record is a pointer; the nameserver is the destination.

Why does a domain have more than one NS record?

Multiple NS records provide redundancy. If one name server is unreachable, DNS resolvers fall back to the others automatically. Most domain registrars require a minimum of two name servers. RFC 1034 recommends at least two authoritative name servers per zone to ensure continuous availability.

Why are the NS records for my domain not showing up?

NS records may not appear if the domain has not been delegated at the registrar level, or if the domain does not exist or has expired. If you recently changed name servers, allow 24–48 hours for propagation. Selecting Authoritative DNS and receiving no result typically confirms a delegation problem at the registrar.

How accurate are the NS records returned by this tool?

NS records are retrieved in real time from the selected DNS resolver with no caching applied by this tool. Recursive resolvers such as Google and Cloudflare may return cached answers up to the record's TTL. Selecting Authoritative DNS always returns live zone data queried directly from the domain's own name servers.

How long does it take for NS record changes to propagate?

NS record changes typically propagate within a few hours but can take up to 48 hours globally, depending on the TTL of the previous NS record. Lowering the TTL to 300 seconds before making the change shortens the propagation window. Use the DNS Lookup tool to monitor propagation across resolvers during the transition.

Do you store or log the domains I look up?

No. Domain names entered into this tool are not stored, logged, or retained after the query completes. Queries are forwarded directly to the selected DNS resolver and results are returned in real time without persistent storage on our servers.

NS records return nameserver hostnames, not IP addresses. Understanding how DNS resolves those hostnames to IPv4 addresses is foundational to reading NS lookup results and tracing the full DNS resolution chain.

Guide What Is IPv4? Address Structure, Classes, and CIDR Explained

Most authoritative name servers respond on IPv4 addresses. This guide explains IPv4 address structure and how IP addressing underpins all DNS resolution, including NS queries.