NS
Name Server
NS records define which name servers are authoritative for your domain. Learn delegation, glue records, and how NS changes propagate.
Published · Last verified · Maintained by TamingDNS
NS
Zone Management
RFC 1035
Indirect
NS <nameserver-hostname>.
NS ns1.example.com.
86400 s (24 h) or higher. NS records rarely change and long TTLs improve resolution speed
💬 What This Record Does
NS records define which name servers are authoritative for a DNS zone. When the global DNS resolves example.com, it first asks the .com registry where to find the authoritative nameservers. Those are defined by NS records. Every DNS change you make (adding MX records, updating SPF, etc.) is served from these authoritative nameservers. NS records are set both in your registrar's dashboard (as "glue" records in the registry) and within your DNS zone itself.
Common Uses
- Delegating a subdomain to a different DNS provider
- Identifying which nameservers are authoritative during a migration
- Verifying that registrar NS records match the zone's own NS records
⚠️ Watch Out For
- NS records at the zone apex (your domain root) must match what your registrar has on file. Mismatches cause resolution failures.
- When you change nameservers at your registrar, propagation can take up to 48 hours.
- Delegated subdomains need NS records in the parent zone, plus glue A records if the nameserver is within the delegated zone.
🔧 Related Tools
📋 Complete Example Records
Whole records in zone-file form: name, TTL, class, type, then the data. Most DNS panels ask for the pieces separately. Look them up live with the DNS Lookup tool.
example.com. 86400 IN NS ns1.example.com. example.com. 86400 IN NS ns2.example.com.
Two authoritative nameservers at the apex. This set has to match what your registrar has on file, or resolution gets unpredictable.
dev.example.com. 86400 IN NS ns1.provider.example.net. dev.example.com. 86400 IN NS ns2.provider.example.net.
Delegating one subdomain to a different provider. Everything under dev.example.com is then answered by their servers, not yours.
example.com. 86400 IN NS ns1.example.com. ns1.example.com. 86400 IN A 192.0.2.53
A nameserver inside the zone it serves needs a glue A record in the parent. Without the glue, the lookup has no way to start.
example.com. 300 IN NS ns1.newprovider.example.net.
Dropping the TTL ahead of a nameserver move. Registry-level changes can still take a day or more whatever you set here.