NS रिकॉर्ड

NS Records and Zone Delegation

NS records are the mechanism by which DNS authority is delegated. When a domain is registered, the registrar publishes NS records in the TLD zone pointing to the domain owner's chosen authoritative name servers. These are called delegation records — they tell the TLD zone "for queries about example.com, ask these servers."

The authoritative servers themselves also publish NS records for the zone they serve — these are the authoritative NS records and must match the delegation records in the parent zone. A mismatch causes resolution failures and is a common source of DNS misconfiguration.

Glue Records

A circular dependency arises when NS records point to names within the same zone. If ns1.example.com is authoritative for example.com, resolving ns1.example.com requires asking example.com's authoritative servers — but those are what we're trying to find. Glue records break this loop: the TLD zone includes A records for in-zone name servers alongside the delegation NS records, providing IP addresses without needing to query the zone being delegated.

NS Records and Zone Transfers

Secondary authoritative servers use the NS record set to identify peers. Zone transfer mechanisms (AXFR for full transfers, IXFR for incremental) synchronize zone data from primary to secondary servers. A minimum of two NS records is required by most registrars and RFC best practices — serving a zone from a single name server creates a single point of failure for all DNSDomain Name System. The hierarchical, distributed naming system that translates human-readable domain names (e.g., example.com) into IP addresses (e.g., 93.184.216.34). Often called the "phonebook of the internet." resolution for that domain.

Check NS records and verify they match delegation with DNS Lookup.