Opens in a new tab

NS record: which nameservers answer for a domain

NS records name the nameservers that hold a zone’s records. They exist twice: at the registry, which sends the world to your nameservers, and in the zone itself — and the two lists should match.

Type number2
Set atThe registrar (delegation) and in the zone
How manyAt least two
Defined inRFC 1034 §4.2.1

Look up the NS records of any name

One question to DNS, answered as it is. You can change the record type too.

What it does

Changing DNS provider means changing the NS records at your registrar; the new provider’s nameservers then answer. When the registry’s list and the zone’s list disagree, resolvers can end up asking a server that no longer has your records — the classic “works for some people” fault.

When a nameserver’s name is inside the zone it serves (ns1.example.com for example.com), the registry also holds its address — a glue record — so resolvers can reach it at all.

How it is written

FieldMeaning
NameThe zone (or a delegated subdomain)
ValueA nameserver’s host name

Examples

example.com.  86400  IN  NS  ada.ns.cloudflare.com.
example.com.  86400  IN  NS  bob.ns.cloudflare.com.

A domain served by Cloudflare’s nameservers.

Common mistakes

  • Changing nameservers at the registrar before the new provider holds every record.
  • Leaving an old provider’s nameservers in the list.
  • Only one nameserver, so one outage takes the whole domain off the internet.

What we recommend

Copy every record to the new provider first, then change NS at the registrar, and keep the old zone running until the old NS TTL has passed.

NS lookup: the zone compared with the registry →

Sources

Checked on 25 September 2026 against these official sources:

Know when a record changes

Add your domain and we scan its DNS on a schedule, keep every version, and email you when a record changes — along with certificate and domain expiry. Free for your first domain.

Create a free account