Updated on:  
January 21, 2025

What is NS record

An NS record, short for Name Server record, specifies which servers are responsible for managing the DNS records of a domain. These servers hold information about your domain, such as A records, CNAME records or MX records.

colourful collage of abstract shapes and path with signpost

How does an NS record work

When someone visits your website or sends an email to your domain, their device needs to resolve the domain name to the correct IP address. This process starts with the NS record. The NS record tells the device which name servers to query for the necessary DNS information.

If the NS record for “mybusiness.com” points to “ns1.hostingprovider.com,” the device will send a query to that name server. The name server then looks up the requested DNS records, such as the A record for your website, and sends the information back to the device.

NS records act like a directory. They guide requests to the correct name servers, which then provide the specific DNS records required to complete the connection.

Understanding key components

NS records contain several components that make them function properly.

  • Domain Name: This is the domain or subdomain for which the NS record applies, such as “mybusiness.com” or “shop.mybusiness.com.”
  • Name Server Address: This is the address of the name server responsible for managing the domain’s DNS records. It is usually in the form of a hostname, such as “ns1.hostingprovider.com.”
  • TTL (Time to Live): This value determines how long DNS servers should cache the NS record. A shorter TTL allows faster updates, while a longer TTL improves performance by reducing the number of DNS queries.

Examples

Imagine you’ve registered the domain “mystore.com” with a domain registrar. The registrar provides default name servers, such as “ns1.registrar.com” and “ns2.registrar.com.” The NS record for “mystore.com” points to these name servers, which hold all the DNS records for your domain.

If you later move your website to a new hosting provider, you may need to update your NS records to point to the new provider’s name servers, such as “ns1.newhost.com” and “ns2.newhost.com.” This ensures that DNS queries for your domain are directed to the correct name servers, which now manage your updated DNS records.

Another example is using a third-party DNS service like Cloudflare. In this case, you would update your NS records to point to Cloudflare’s name servers, such as “ns1.cloudflare.com” and “ns2.cloudflare.com.” This enables you to use Cloudflare’s DNS management and performance optimization services.

How to check your NS records

Checking your NS records is important for verifying your domain’s setup or troubleshooting issues. You can do this through your domain registrar or DNS hosting provider. Log into their platform and navigate to the DNS management or domain settings section.

In the DNS settings, you’ll find a list of all DNS records, including NS records. These entries will show the name servers your domain is currently using.

You can also use external tools like WHOIS lookup, MXToolbox, or online DNS checkers. These tools let you enter your domain name and display the associated NS records.

Common problems and how to fix them

While NS records are simple in structure, issues can arise that disrupt your domain’s functionality. Understanding these problems can help keep your domain running smoothly.

  • Incorrect Name Servers: If your NS record points to the wrong name servers, your domain will not resolve correctly. Verify the name servers provided by your registrar or hosting provider and update the NS records as needed.
  • Incomplete Records: NS records often require at least two entries for redundancy. If one name server fails, the other can handle queries. Ensure your NS records include all necessary name servers.
  • Propagation Delays: Changes to NS records can take up to 48 hours to propagate. During this time, some users might experience issues accessing your domain. Plan updates during low-traffic periods to minimize disruptions.
  • Conflicts with Other DNS Records: If you have conflicting DNS records in different name servers, users may experience inconsistent results. Ensure all name servers have identical and up-to-date DNS configurations.