What is an NS record?

An NS (Name Server) record indicates which DNS servers are authoritative for a domain. It tells recursive resolvers where to go to find the website, mail, and other DNS records for that domain.

Why do my NS lookup results show different servers than expected?

If your results show unexpected servers, you may have recently changed your name servers and are seeing cached data, or your domain registrar might not have successfully updated the delegation at the registry level.

How long does a name server change take to update globally?

Name server changes typically propagate worldwide within 2 to 24 hours. The exact duration depends on the Time to Live (TTL) values set by the parent registry and how aggressively local internet service providers cache the old records.

What is the difference between an A record and an NS record?

An A record maps a domain name directly to an IPv4 address. An NS record points to the specific name servers that store the A record and all other DNS configurations for that domain.

Can I use just one name server for my domain?

While technically possible, using only one name server violates core DNS standards and best practices. If that single server goes offline, your entire website and email infrastructure will become completely inaccessible.

What are glue records and when do I need them?

Glue records are direct IP address mappings provided at the domain registrar level for custom name servers that use your own domain name. You only need them if your name server hostnames share the same domain suffix as the domain they are authoritative for.

NS Lookup: Find the Name Servers of a Domain

The NS Lookup tool queries the global Domain Name System to find the authoritative name servers responsible for a specific domain name. It helps you identify your current DNS hosting provider and verify whether your domain's delegation is configured correctly across the internet.

What is it

An NS (Name Server) lookup is a diagnostic operation that queries root and TLD (Top-Level Domain) name servers to retrieve the NS records of a target domain. These records point to the specific servers that hold the master copy of your DNS zone file. When a user tries to visit your website or send you an email, their recursive resolver consults these authoritative name servers to find your A, AAAA, MX, and TXT records. Without correct NS records, your domain is effectively invisible on the internet.

Why it matters

Knowing your authoritative name servers is critical for managing your web infrastructure, migrating hosting providers, and securing your domain. If your NS records point to an old or compromised provider, your website traffic and emails could be misdirected. IT professionals and website owners use NS lookups during domain migrations to confirm that a new DNS provider has taken over delegation properly. It is also the first step in troubleshooting when a website fails to load or emails bounce due to DNS resolution failures.

How to use this tool

Type your domain name into the search input box.
Press the Check button to initiate the DNS query.
Wait a moment for the tool to query the root and authoritative name servers.
Review the returned list of name servers and their corresponding IP addresses.

How to read the results

When you run a lookup for example.com, the tool returns a list of authoritative name servers and often their associated glue records (IP addresses).

Name Server (NS): Shows the hostname of the server authoritative for the zone, such as ns1.example-dns.com. This indicates which company or nameserver cluster controls your DNS settings.
IP Address (Glue Record): Displays the IPv4 or IPv6 address of the name server, such as 192.0.2.1. These are required when your name server is a subdomain of the domain itself (e.g., ns1.example.com using example.com).
TTL (Time to Live): Indicates how long, in seconds, recursive resolvers should cache this record, such as 3600. A lower TTL speeds up propagation during changes, while a higher TTL reduces query load.

Common problems and how to fix them

Mismatched Name Servers

If the NS records shown by the tool do not match what you configured at your domain registrar, your domain will suffer from inconsistent resolution. Log into your domain registrar account and update the nameservers to match the exact values provided by your DNS hosting provider.

Missing Glue Records

If you use custom name servers that are child hosts of your own domain (like ns1.example.com), and they fail to resolve, you are likely missing glue records. Create the appropriate A records at your registrar level pointing your custom name server hostnames to their exact server IP addresses using syntax like:

ns1.192.0.2.1

Propagation Delays

If you recently changed your name servers and the tool still shows the old provider, you are likely experiencing a propagation delay. This is caused by caching at the ISP and TLD registry levels and can take anywhere from a few minutes up to 48 hours to fully resolve globally.

Best practices

Always maintain at least two distinct name servers for redundancy, ideally hosted on different networks or providers to prevent total downtime if one data center fails. Before changing your name servers at your registrar, lower the TTL on your existing records to speed up the transition. Document your DNS records thoroughly before migrating providers so you can recreate them accurately on the new authoritative name servers. Regularly audit your NS records to ensure your domain is not pointing to legacy or unauthorized hosting accounts.

NS Lookup