What are NS records? (and why your DNS edit did nothing)

The one-sentence version

NS (name server) records list the servers that are authoritative for your domain: the ones that hold the real answers and respond when anyone looks you up. Whoever your NS records point to is the provider in charge of your DNS, and the only place where editing a record has any effect.

example.com.   86400   IN   NS   ns1.dnsprovider.net.
example.com.   86400   IN   NS   ns2.dnsprovider.net.

Delegation: how your domain is handed off

DNS is a chain of handoffs called delegation. The .com servers do not hold your records; they hold a pointer that says “for example.com, go ask these name servers.” That pointer is a set of NS records in the parent zone. Your own zone then repeats the same NS records at its apex, this time as the authoritative copy.

So the same name servers are named in two places: the parent (a referral that sends resolvers onward) and your zone's apex (the authoritative answer). When you “set your nameservers” at a registrar, you are editing that parent-side delegation, choosing which provider the rest of the internet gets sent to.

Glue records

There is a chicken-and-egg case worth knowing. If your name server's own name lives inside the domain it serves (say ns1.example.com is authoritative for example.com), a resolver would have to ask the server for its own address before it can reach it. To break the loop, the parent zone includes a glue record: the A or AAAA address of that name server, supplied alongside the delegation. Most people never touch glue directly; your registrar manages it when you use custom nameservers.

The trap that wastes the most time

Here is the single most common DNS support ticket, and it is almost always NS records: “I added the DMARC record and nothing changed.”

The cause is a split between where you bought your domain and where its DNS is actually hosted. You log into your registrar, find a DNS panel, add the record, and wait, but your NS records delegate to Cloudflare (or your web host, or a managed DNS provider). The record you added at the registrar is never consulted, because resolvers were sent somewhere else. Nothing is broken; you simply edited the wrong zone.

The fix is always the same:

• Find your real DNS host. Look up your live NS records (dig NS example.com +short or a whois lookup) and see which provider they name.
• Edit there. Whatever your NS records point to is the only place a new SPF, DKIM, DMARC, or MX record will take effect. Our universal provider guide walks this for the common hosts.

The rule to remember is short: edit wherever your NS records point. Some registrars are also your DNS host, in which case the registrar panel is correct, but the only way to be sure is to check the NS records, not to assume.

Two rules that connect to your other records

• An NS record must never point to a CNAME. Like an MX target, a name server must be a real hostname with its own address record. RFC 2181 prohibits aliasing it, and a CNAME there fails to return the address resolvers need.
• Your apex always carries NS and SOA records. That is precisely why you cannot put a CNAME at your domain root: a CNAME is not allowed to coexist with the NS and SOA that have to be there.

How to check yours

• dig NS example.com +short returns the name servers actually answering for your domain right now.
• A whois lookup shows the nameservers recorded at the registry, which should match. If they disagree, a delegation change is still propagating.
• After any record change, run a DMARC audit to confirm the record is live where receivers will look, not just saved in a panel.

Common questions

I changed my DNS record but nothing happened. Why?

Most often because you edited DNS at your registrar while your NS records delegate elsewhere. Check your live NS records, find the provider they name, and make the change there. (If you only just edited the right place, give it up to your record's TTL to appear everywhere.)

What is the difference between my registrar and my DNS host?

Your registrar is where you bought and renew the domain. Your DNS host is whoever your NS records point to, the provider that actually answers lookups. They are often the same company, but not always, and only the DNS host's records are live.

How do I find out who hosts my DNS?

Look up your NS records: dig NS example.com +short, or any online NS lookup. The provider those nameservers belong to is your DNS host, and the place to edit records. Our any-provider guide covers identifying the common ones.