What Is an NS Record
Learn what NS records are, how nameservers work, authoritative DNS, and why nameserver changes affect your entire zone.
Introduction
Nameserver (NS) records delegate DNS control for a domain to a specific DNS provider or hosting company.
Registrar nameserver settings and zone NS records must align. Editing DNS in the wrong panel is a common mistake when NS records point elsewhere.
Quick answer
NS records identify which nameservers are authoritative for a DNS zone. When you change nameservers at your registrar, you tell the internet which DNS provider controls records like A, MX, TXT and CNAME for your domain.
What it means
NS stands for Name Server. NS records answer the question: “Who is authoritative for this domain’s DNS zone?”
- Defines authoritative DNS for a domain
- Set at registrar when you change nameservers
- Also appear inside the zone at the DNS provider
- Custom nameservers may need glue (A/AAAA) records
- NS changes affect all DNS records in the zone
Where you see this:
- Pointing a domain to Cloudflare, Route 53 or another DNS host
- Registrar nameserver updates during DNS migration
- Child zones and subdomain delegation (less common for beginners)
- Custom branded nameservers for resellers
example.com. 172800 IN NS ns1.dnsprovider.com.
example.com. 172800 IN NS ns2.dnsprovider.com.Why this matters
If NS records point to the wrong provider, changes you make elsewhere have no public effect. Nameserver migrations without copying records can take email, website and SSL offline.
How to check it
- Run DNS Lookup and check NS records for the domain.
- Compare with nameservers shown in WHOIS Lookup or registrar panel.
- Confirm you edit DNS where those nameservers are hosted.
- Use dig +short example.com NS or dig +trace example.com.
- After NS changes, verify A, MX and TXT records exist at the new provider.
Look up nameservers
Use DNS Lookup to see which nameservers are authoritative for a domain.
Common mistakes
Editing DNS at non-authoritative provider
HighRecords were changed where NS no longer points.
Next step: Check NS records and edit DNS at the live authoritative provider.
Nameserver change without copying records
HighNew DNS host has an empty or incomplete zone.
Next step: Export and recreate A, MX, TXT and other records before switching NS.
Custom NS missing glue records
HighChild nameservers under the domain lack required A/AAAA glue.
Next step: Add glue at the registrar for custom nameserver hostnames.
DNSSEC DS mismatch after NS change
HighOld DS records remain at registrar while the new zone is unsigned or different.
Next step: Remove or update DS records when migrating DNS providers.
Example
example.com. 86400 IN NS ns1.cloudprovider.net.
example.com. 86400 IN NS ns2.cloudprovider.net.Frequently asked questions
What is the difference between registrar and nameservers?
The registrar is where the domain is registered. Nameservers are where the live DNS zone is hosted and answered authoritatively.
How long do nameserver changes take?
Registry updates can take minutes to 48 hours depending on TLD, registrar and caching.
Do NS records replace A and MX records?
No. NS records only say who hosts DNS. You still need A, MX, TXT and other records inside that zone.
What are glue records?
Glue A/AAAA records at the registrar for custom nameservers like ns1.example.com when those nameservers are under the same domain.
Related tools
Use these free tools to verify your configuration after applying changes.
Related guides
Browse all Glossary guides →Need help applying this fix?
Send us your domain, report link or issue details. CheckDomainHealth will review the request and route it to the right technical team if hands-on support is needed.
Was this guide helpful?
Your feedback helps us improve our guides for everyone.
Thanks for your feedback!