Skip to content

NS lookup

Enter a domain to see its NS records: the nameservers that answer for it.

Example: NS records of cloudflare.com

What is an NS record?

NS records name the servers that hold a domain's DNS records. They exist in two places: at the parent zone (set through your registrar) and inside the zone itself.

Resolvers follow the parent's list to find your nameservers, so that list decides where the world looks for your records. Both lists should match.

How to read an NS record

In a zone file, the record looks like this:

example.com.   86400   IN   NS   a.iana-servers.net.
  • The zone the nameserver serves.
  • The TTL in seconds. NS records usually have long TTLs, often one or two days.
  • The host name of the nameserver.

From the command line

Look up NS records without this site.

On macOS and Linux, use dig:

dig example.com NS +short

On Windows, use nslookup:

nslookup -type=NS example.com

To skip caches, ask one of the domain’s nameservers directly: dig @ns1.example.net example.com NS. The “Its own nameservers” option on the result page does the same.

Questions and answers

I changed nameservers. How long until it takes effect?

The registry updates within minutes to hours, but resolvers cache the old delegation for the TTL the parent zone sets: up to 48 hours for .com. Use the Trace tab to see what the parent zone returns right now.

How many nameservers should a domain have?

At least two, on different networks. Most DNS hosts give you two to four.

Why do the registrar and the zone list different nameservers?

Usually a migration that was finished on only one side. It works as long as the servers in the parent's list answer, but it is fragile. The Health tab flags this mismatch.

Other record types