How many NS records should a domain have?

A domain should have at least two independent authoritative nameservers located on distinct network subnets to ensure high availability and redundancy.

How long do NS record changes take to propagate?

Because NS records have long default TTLs (24 to 48 hours), global nameserver updates typically take 24 to 48 hours to propagate worldwide.

How do I check my domain's nameservers?

Use our DNS Lookup tool with the NS filter, or execute 'dig NS example.com' from terminal.

Home/DNS Lookup/NS Record

TXT SOA

DNS Resource Record Type

NS Record: Name Server Record

Delegates a DNS zone to authoritative nameservers responsible for publishing DNS records.

Record Type

Query Protocol

DNS Port 53

Standard / RFC

RFC 1035, Section 3.3.11

Recommended TTL

86400 seconds

Query Live NS Records

Query any domain name to inspect authoritative NS records, response latency, and TTL values.

Loading DNS lookup tool...

BIND Zone File Syntax

Standard BIND representation of this record in authoritative master zone files:

example.com. 86400 IN NS ns1.exampledns.com.

Recommended TTL: 86400 seconds (24 hours) or 172800 seconds (48 hours) for high caching stability.

Common Configuration Pitfalls

Mismatched NS records between the registrar (whois delegation) and the zone file, causing intermittent lookup failures (lame delegation).
Listing fewer than two distinct authoritative nameservers, creating single-point-of-failure risks.

How the NS Record Operates in DNS Resolution

The NS (Name Server) record delegates administrative authority for a DNS zone to specific nameservers. Both parent registries (TLDs like .com or .net) and the domain's authoritative zone file contain NS records, directing global resolvers to the machines that hold the definitive zone records.