NS Lookup - Find a Domain’s Name Servers

Enter a domain to list its name servers, see which DNS provider hosts it and check that every name server resolves.

What is an NS record?

NS (name server) records say which servers hold a domain’s DNS records. When anyone looks up your website, email or any other record, they first ask the domain’s name servers. They are set at your domain registrar and published in the parent zone, such as .com.

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

What this NS lookup checks

  • Every name server for the domain, with its TTL.
  • The DNS provider, such as Cloudflare, Amazon Route 53, GoDaddy or Namecheap, recognized from the name server hostnames.
  • Redundancy: at least two name servers, so DNS keeps working if one fails.
  • Resolution: each name server must resolve to an IP address, or it cannot answer queries.
  • Subdomains: NS records live on the zone root, so for mail.example.com the tool shows the name servers of example.com.

Why name servers matter

The name servers decide where your DNS changes must be made. A common mistake is editing records at the registrar while the domain’s name servers point to another provider, such as Cloudflare. The changes are saved but never used. If an MX, SPF or DMARC change is not taking effect, check the name servers first.

Changing name servers

  • Copy all your existing records to the new DNS provider before switching, or your website and email stop working.
  • Change the name servers at your registrar, not at the DNS provider.
  • Name server changes can take up to 24 to 48 hours to reach everyone, because the parent zone caches them for longer than normal records.

NS lookup from the command line

dig example.com NS +short
nslookup -type=ns example.com

Frequently asked questions

Enter the domain in the NS lookup above. It lists every name server and, where it can tell from the hostnames, the DNS provider. On the command line, run dig example.com NS or nslookup -type=ns example.com.

At least two, ideally on different networks, so the domain still resolves if one server is down. Most registries require a minimum of two.

At the provider that runs your name servers, shown by this lookup. If your name servers belong to Cloudflare, for example, changes made in your registrar’s DNS panel have no effect.

Usually a few hours, but it can take up to 48 hours, because the parent zone such as .com publishes NS records with long TTLs and resolvers cache them.