Usage
NS records point (sub)domains to domain names of name servers.
Example:
| Type | Name (use @ for root) | Value | TTL |
|---|---|---|---|
| NS | @ | hydrogen.ns.hetzner.com. |
Requests to a domain are always handled by the domain provider. If you add an NS record in the domain provider's zone pointing to
hydrogen.ns.hetzner.com, DNS queries for the domain are answered by the name serverhydrogen.ns.hetzner.com, which holds the records configured in the zone at Hetzner.
Aexample.com203.0.113.1
Records are stored on the name server ns.example.org
example.com
Aexample.com203.0.113.1Ashop.example.com198.51.100.1CNAMEwww.example.comexample.com
Records are stored on the name server hydrogen.ns.hetzner.com
Description
The zone itself is appended automatically at the end of the entry (e.g. www is interpreted as www.example.com).
Period at the end of the (sub)domain
The entry is used exactly as provided and no domain suffix is appended (e.g. www.example.com. is interpreted as www.example.com).
More information
The NS in NS records stands for name servers. NS records tell you which name server is authoritative for the domain/subdomain. A single domain usually has more than one NS record address (often 2 or 3) as it can be dangerous to not have multiple NS records. Clients (should) choose one of the provided NS records at random.
There are two main reasons that administrators use NS records:
- They want to delegate part of their domain/subdomains to use different name servers.
- They want to separate traffic to their domain between their local name servers and other name servers.
When you create NS records, the value that you enter for each record is the fully-qualified domain name (FQDN) that you want to point the NS record to. When you do a name server lookup, you enter the domain in the search and see which name server(s) contain the NS record.