What is an NS record?
An NS record — short for Name Server record — is a DNS entry that identifies which servers are authoritative for a domain. In other words, NS records tell the rest of the internet where to go to find the definitive DNS records for your domain. Every registered domain must have at least two NS records for redundancy.
NS records do not point to IP addresses directly. Instead, they point to hostnames of name servers — typically provided by your domain registrar or a third-party DNS provider. Those name servers then hold all the other DNS records for your domain, such as A, MX, CNAME, and TXT records.
Why do NS records matter?
When someone types your domain into a browser, the DNS resolution process starts by finding out which name servers are responsible for your domain. This is done by looking up the NS records. Once the authoritative name servers are identified, all subsequent DNS queries — for your IP address, mail servers, and other records — are directed to those servers.
If your NS records are missing or point to the wrong servers, your entire domain becomes unreachable. No website, no email, no services. Verifying your NS records is one of the first steps in diagnosing any domain-wide connectivity issue.
How DNS resolution works with NS records
DNS resolution happens in layers. When a user enters a domain name, their device first checks its local cache. If the record is not cached, the query goes to a recursive DNS resolver — typically provided by their ISP or a public service. The recursive resolver then works its way up the DNS hierarchy: it asks the root servers which name servers handle the domain's top-level domain (like .com), then asks those servers for the domain's NS records, and finally queries the authoritative name servers directly for the specific record needed.
Authoritative name servers are the final source of truth. They hold the actual DNS zone file for a domain, containing all record types: A, AAAA, MX, TXT, CNAME, SOA, and more. NS records are what point the entire DNS system toward these authoritative servers.
How to use the NS lookup tool
Enter any domain name in the search field and click Lookup. The tool will query DNS in real time and return all NS records associated with that domain, showing the host, the name server hostname, and the TTL value. This is useful for verifying that your domain is using the correct name servers after a registrar transfer, checking which DNS provider manages a domain, or troubleshooting DNS propagation issues.
Frequently Asked Questions
What is the difference between an A record and an NS record?
An A record maps a domain name directly to an IPv4 address — it tells browsers and other clients where a server lives on the internet. An NS record, by contrast, points to the servers that hold all DNS records for a domain, including A records. Think of NS records as the directory listing that tells you which phone book to consult, while A records are the actual entries inside that phone book.
Can a domain have more than one NS record?
Yes — and it should. Having multiple NS records across different physical servers improves resilience. If one name server goes offline, DNS queries are automatically handled by the others. Most domain registrars and DNS providers assign at least two name servers by default. Some organisations configure four or more for additional redundancy and load distribution.
How long does it take for NS record changes to propagate?
NS record changes can take longer to propagate than other DNS changes because they are cached at multiple levels of the DNS hierarchy, including at the registry level for your top-level domain. Propagation typically completes within a few hours but can take up to 48 hours in some cases. During propagation, different users around the world may reach your domain through different name servers, which is normal.
What happens if NS records are wrong or missing?
If NS records are missing entirely, DNS resolvers cannot locate the authoritative servers for your domain, making it unreachable. If they point to the wrong servers, queries will be directed to servers that do not have your DNS zone, resulting in NXDOMAIN errors or stale responses. Either situation will take your website, email, and any other domain-dependent services offline until the records are corrected and propagated.
Do NS records affect email delivery?
NS records do not directly deliver email, but they are essential for email to work at all. When another mail server looks up your MX records to deliver a message, it first needs to find your authoritative name servers via NS records, then query those servers for your MX records. If NS records are broken, the entire DNS lookup chain fails and no email can be delivered to your domain.