`NS` Name Server

NS records define which name servers are authoritative for your domain. Learn delegation, glue records, and how NS changes propagate.

Record Type
NS

Category
Zone Management

RFC
RFC 1035

Email Relevant
Indirect

Format
NS <nameserver-hostname>.

Example
NS ns1.example.com.

TTL Guidance
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.