DNS record types · Updated

DNS NS record

An NS (name server) record names a server that holds the authoritative DNS records for a domain. The set of NS records is how the rest of the internet finds out where to ask about your domain.

Look up a NS record

Check what DNS returns right now:

Format and example

example.com.   86400   IN   NS   ns1.example.net.
  • Name: The domain the nameserver is responsible for.
  • TTL: Often long (a day or two). The copy held by the registry cannot be shortened by you.
  • Nameserver: A hostname with its own address records. Publish at least two, on separate networks.

Common mistakes

  • Publishing a single nameserver. If it fails, the domain disappears. Registries expect at least two.
  • Changing nameservers at the registrar before copying every record to the new DNS host. Websites and email stop until the old records exist there.
  • Letting the NS records at the registrar differ from those in the zone. Resolvers get different answers depending on which they ask.
  • Naming a nameserver inside your own domain without glue records, so resolvers cannot find the address needed to reach it.

Related record types

SOA record, MX record. The DNS record types guide compares them all.

Frequently asked questions

What is an NS record?

An NS record says which servers are authoritative for a domain, meaning they hold its real records and give the final answer. Registrars publish them at the parent (such as .com) when you set your nameservers.

How do I find who hosts the DNS for a domain?

Look up its NS records. Names such as ns1.cloudflare.com or ns-123.awsdns-45.org tell you the DNS provider.

How many NS records should a domain have?

At least two, on separate networks. Most DNS providers give you two to four.

How long do NS changes take?

The delegation at the registry usually has a TTL of 24 to 48 hours, so a nameserver change can take that long to reach every resolver.

What is the difference between NS records at the registrar and in the zone?

The registrar publishes the delegation at the parent zone. The zone itself lists its own NS records. They should match; a mismatch causes intermittent failures.