Learn what an NS record is, how nameservers work, how DNS delegation works, and why NS records are important when managing a domain and its DNS records.

An NS record is one of the core records used by the Domain Name System (DNS). It identifies the authoritative nameservers responsible for a DNS zone.

When someone enters a domain such as example.com, DNS needs to know which nameservers are responsible for providing the DNS information for that domain.

This is where NS records and nameservers become important.

In this guide, we will explain what an NS record is, what a nameserver does, how DNS delegation works, and how you can check NS records for a domain.

What Is an NS Record?

An NS record is a DNS record that specifies which nameserver is authoritative for a domain or DNS zone.

NS stands for Name Server.

A simple example can look like this:

example.com    NS    ns1.example-dns.com
example.com    NS    ns2.example-dns.com

These records indicate that the listed nameservers are responsible for answering authoritative DNS queries for the zone.

A domain normally uses more than one nameserver to provide redundancy.

What Is a Nameserver?

A nameserver is a DNS server that stores or provides DNS information for a domain or DNS zone.

For example, a nameserver may contain records such as:

• A records
• AAAA records
• CNAME records
• MX records
• TXT records
• Other DNS records

When a DNS resolver needs authoritative information about a domain, it can query the appropriate authoritative nameserver.

How Does DNS Delegation Work?

DNS delegation is the process of assigning responsibility for a DNS zone to specific authoritative nameservers.

For a domain such as:

example.com

the parent DNS system can identify the nameservers responsible for the domain.

The simplified process looks like this:

User
  ↓
DNS Resolver
  ↓
Root DNS
  ↓
.com DNS
  ↓
Authoritative Nameserver
  ↓
DNS Record
  ↓
IP Address / Mail Server / Other Target

The resolver follows this DNS hierarchy to find the authoritative source for the requested domain information.

Read More

Continue your DNS learning with these related guides:

• DNS Lookup: How to Check DNS Records for Any Domain
• TXT Record Explained: What Is a TXT Record and How Does DNS Verification Work?
• CNAME Record Explained: What Is a CNAME and How Does It Work?

NS Record Example

A domain may have NS records such as:

Type:   NS
Name:   example.com
Value:  ns1.example-dns.com

Type:   NS
Name:   example.com
Value:  ns2.example-dns.com

The two nameservers can provide authoritative DNS service for the domain.

The actual nameserver hostnames depend on the DNS provider managing the domain.

NS Records and Domain Nameservers

When you register a domain, your registrar usually allows you to configure the domain's nameservers.

For example, a DNS provider may give you:

ns1.dns-provider.com
ns2.dns-provider.com

You then configure those nameservers for your domain through the registrar or domain management system.

This tells the domain's DNS delegation where authoritative DNS service is provided.

NS Record vs Nameserver

The terms NS record and nameserver are related but they are not exactly the same thing.

TermMeaningNS record | A DNS record identifying an authoritative nameserver
Nameserver | A DNS server responsible for answering DNS queries
DNS zone | A portion of the DNS namespace managed together
DNS delegation | The process of assigning DNS responsibility to nameservers

In simple terms, an NS record tells DNS which nameserver is responsible.

Why Do Domains Use Multiple Nameservers?

Domains commonly have multiple authoritative nameservers.

For example:

example.com    NS    ns1.example-dns.com
example.com    NS    ns2.example-dns.com

Using multiple nameservers can provide redundancy and improve resilience if one nameserver becomes unavailable.

The exact number and architecture depend on the DNS provider.

What Is an Authoritative Nameserver?

An authoritative nameserver is a DNS server that has authoritative information for a DNS zone.

When an authoritative nameserver responds for a zone, its answer comes from the DNS data it is authoritative for rather than from a cache of another DNS server.

For example, if example.com is delegated to certain nameservers, those nameservers can provide authoritative answers for records in the zone.

Authoritative Nameserver vs DNS Resolver

A DNS resolver and an authoritative nameserver have different roles.

FeatureDNS ResolverAuthoritative NameserverMain role | Finds DNS answers for clients | Provides authoritative DNS data
Typical behavior | Can cache DNS responses | Answers from authoritative zone data
Example use | Resolves a website hostname | Provides records for a domain

For example, a user's device may use a recursive DNS resolver. That resolver can then query the authoritative nameserver for the requested domain.

NS Records and Other DNS Records

NS records work as part of the wider DNS system.

A domain's authoritative zone may contain records such as:

example.com        A       192.0.2.10
example.com        AAAA    2001:db8::10
example.com        MX      10 mail.example.com
example.com        TXT     "verification=abc123"
www.example.com    CNAME   example.com

The NS records identify the nameservers that are authoritative for the zone. Those nameservers can then provide the other DNS records.

How to Check NS Records

You can check the NS records for a domain using a DNS lookup tool.

Use the AuraTools DNS Lookup tool and query the domain you want to inspect.

Look for records with the type NS.

A result may look like:

NS    ns1.example-dns.com
NS    ns2.example-dns.com

You can compare these nameservers with the nameservers configured for the domain at your registrar or DNS provider.

NS Records vs Nameservers Configured at a Registrar

This is an important distinction when troubleshooting DNS.

Your domain registrar can display the nameservers configured for the domain. The authoritative DNS zone can also contain NS records.

These pieces of information work together as part of DNS delegation.

If you recently changed nameservers, it is useful to check both the registrar configuration and the publicly visible DNS delegation.

What Happens When You Change Nameservers?

Changing nameservers changes where DNS authority for the domain is delegated.

For example, you may move from:

ns1.old-provider.com
ns2.old-provider.com

to:

ns1.new-provider.com
ns2.new-provider.com

After the delegation changes, DNS resolvers will gradually begin using the new authoritative nameservers according to DNS caching and delegation behavior.

During a DNS migration, it is important to configure the required DNS records correctly at the new provider before switching the delegation.

Common NS Record Problems

1. Incorrect Nameserver

If the domain is delegated to the wrong nameserver, DNS queries may return incorrect results or fail to find the expected records.

2. Missing Nameserver

If the domain does not have the required authoritative nameserver configuration, DNS resolution can be affected.

3. DNS Records Added to the Wrong Provider

A common mistake is adding records at one DNS provider while the domain is actually delegated to another provider.

The public DNS system follows the authoritative delegation, so changes made at an inactive DNS provider may not affect the domain.

4. Nameserver Migration Before DNS Setup

If you switch nameservers before creating the required DNS records at the new provider, websites, email, and other services can stop working.

5. Incorrect Glue Configuration

When a nameserver is itself inside the domain it serves, additional DNS information may be needed for the delegation to work correctly. This is commonly associated with glue records.

What Are Glue Records?

Glue records help solve a special DNS delegation problem.

Consider a domain using a nameserver such as:

ns1.example.com

If example.com depends on ns1.example.com to resolve the domain, DNS could otherwise encounter a circular dependency.

Glue information provides the required address information for the nameserver during delegation.

Glue records are mainly relevant when operating custom or in-domain nameservers. Most users using a third-party DNS provider do not need to create them manually.

How to Troubleshoot Nameserver Problems

If your domain is not resolving correctly after a DNS change, check the nameserver configuration first.

1. Confirm which nameservers are configured at your registrar.
2. Check the publicly visible NS records.
3. Confirm that the nameservers belong to the intended DNS provider.
4. Verify that the required DNS records exist at that provider.
5. Check whether the nameserver change is still propagating through cached DNS data.
6. Check for incorrect or missing glue information if you operate custom nameservers.

You can start by checking the domain's DNS information with AuraTools DNS Lookup .

How Long Do Nameserver Changes Take?

Nameserver changes are affected by DNS caching and delegation information.

There is no single fixed time that applies to every domain and resolver.

After changing nameservers, some DNS resolvers may continue using previously cached information for a period of time.

During a migration, check the authoritative configuration and allow cached DNS information to expire rather than repeatedly changing the same records.

Can You Change NS Records?

Yes, but you should understand whether you are changing records inside the DNS zone or changing the domain's delegation.

When most website owners say they want to "change nameservers," they are usually referring to changing the authoritative nameservers configured for the domain at the registrar.

Follow the instructions provided by your DNS provider before making this change.

Frequently Asked Questions

What is an NS record?

An NS record identifies a nameserver that is authoritative for a DNS zone.

What does NS stand for in DNS?

NS stands for Name Server.

What is a nameserver?

A nameserver is a DNS server that stores or provides DNS information for a domain or DNS zone.

How many nameservers should a domain have?

Domains commonly use multiple authoritative nameservers for redundancy, but the exact number depends on the DNS provider and configuration.

What is DNS delegation?

DNS delegation is the process of assigning responsibility for a DNS zone to authoritative nameservers.

What is the difference between NS and A records?

An NS record identifies an authoritative nameserver. An A record maps a hostname to an IPv4 address.

How can I check my domain's nameservers?

You can use a DNS lookup tool to query the domain and inspect its NS records.

What are glue records?

Glue records provide address information needed when a nameserver is located within the domain it is responsible for.

Final Takeaway

An NS record identifies the nameservers responsible for a DNS zone. Nameservers provide the authoritative DNS information needed to resolve websites, email services, verification records, and other domain services.

Understanding NS records is especially useful when moving a domain between DNS providers or troubleshooting a domain that is not resolving correctly.

Before changing nameservers, make sure the required DNS records have been configured at the new provider.

Check NS records with AuraTools DNS Lookup to inspect the nameservers currently visible for a domain.