What is an NS record?

An NS (Name Server) record identifies the authoritative nameservers for a domain or delegated DNS zone.

These records tell recursive resolvers which DNS servers should be queried to obtain authoritative answers for a domain.

Without correct NS records, a domain cannot be reliably resolved, regardless of how accurate the underlying DNS records are.

• NS Lookup

A typical NS record defines which nameserver is authoritative for a domain.

example.com. 3600 IN NS ns1.dns-provider.net.

Most domains will have multiple NS records for redundancy:

example.com. 3600 IN NS ns1.dns-provider.net.
example.com. 3600 IN NS ns2.dns-provider.net.

Having multiple nameservers improves availability and resilience.

• Hostname: the domain or zone the NS record applies to
• TTL: how long resolvers cache the delegation information
• Type: NS indicates a nameserver record
• Value: the hostname of the authoritative nameserver (must resolve to an IP)

DNS resolution relies on delegation from parent zones to child zones.

For example, when resolving example.com, a resolver queries the .com nameservers first. These return the NS records for example.com, and the resolver then queries those nameservers for authoritative answers.

; Step 1: ask TLD
example.com. IN NS

; Step 2: TLD response
example.com. IN NS ns1.dns-provider.net.
example.com. IN NS ns2.dns-provider.net.

; Step 3: query authoritative server
www.example.com. IN A

This chain of trust is what allows DNS to scale globally.

• What are glue records?

NS records exist in two critical locations: the parent zone (registrar level) and inside the authoritative DNS zone.

• Parent NS records (delegation): configured at your registrar and determine which nameservers are used globally
• Zone NS records: exist within the DNS zone and should match the parent delegation
• Mismatch between these can lead to inconsistent or intermittent resolution

; Parent (registry/registrar)
example.com. IN NS ns1.provider-a.net.
example.com. IN NS ns2.provider-a.net.

; Zone (authoritative DNS)
example.com. IN NS ns1.provider-b.net.
example.com. IN NS ns2.provider-b.net.

In this scenario, different resolvers may follow different paths, causing inconsistent results.

NS records are fundamental to DNS resolution. If they are incorrect, resolvers may query the wrong servers or fail to resolve the domain entirely.

They are particularly critical during DNS migrations, where delegation changes must be coordinated carefully.

Even small inconsistencies can cause partial outages affecting only some users or regions.

• Whether the nameservers match the intended DNS provider
• Whether at least two nameservers are configured
• Whether each nameserver hostname resolves to an IP (A/AAAA)
• Whether parent delegation matches zone NS records
• Whether changes have propagated across different resolvers

# Check delegation
nslookup -type=ns example.com

# Check authoritative server directly
nslookup example.com ns1.dns-provider.net

# Compare using dig
dig NS example.com
dig @ns1.dns-provider.net example.com

• What is a DNS record?
• What is a CNAME record?

• Leaving old provider nameservers in place after migration
• Assuming nameserver changes propagate instantly
• Mismatch between registrar delegation and zone NS records
• Using in-bailiwick nameservers without proper glue records
• Not verifying that nameserver hostnames resolve correctly

When diagnosing DNS issues, NS records should be one of the first checks.

Validate delegation, query authoritative servers directly, and compare results across multiple resolvers to identify inconsistencies.

# Trace full resolution path
dig +trace example.com

# Query specific resolver
dig @8.8.8.8 example.com

# Query authoritative directly
dig @ns1.dns-provider.net example.com

• NS Lookup
• What is a PTR record?

If you want to validate this topic in practice, these DNS Pro tools are the fastest next step.

• NS Lookup
• Delegation Checker
• Glue Record Checker