They specify which nameservers manage the zone.
Usually, they are not changed.
An NS record describes an authoritative nameserver of a zone. A zone can have more than one authoritative nameserver (usually it has at least two so that if one nameserver fails, the zone can still be resolved from the other nameserver), so there can be multiple NS records.
ℹ️ The Nameserver Hostname field should contain the hostname or FQDN of a server which should be considered authoritative for the zone listed in Zone.
Example: ns1.example.com. (FQDN)
Example: ns1 (hostname only)
The form contains the following fields:
• Zone: Fill in the name of the zone, i.e., the domain.
Examples:
- example.com.
- You can also leave the field empty which has the same meaning as if you'd fill in example.com.
• Nameserver Hostname: The Nameserver Hostname field should contain the hostname or FQDN of a server which should be considered authoritative for the zone listed in Zone.
Examples:
- ns1.somedomain.com. (FQDN)
- ns1.example.com. (FQDN)
- ns1 (hostname only)
❔ If the nameserver is in the same zone (i.e., if the zone is example.com. and you fill in ns1.example.com. or just ns1 in the Nameserver Hostname field), you also need a glue record which you can usually create at your domain registrar.
• TTL: The time interval (in seconds) that this record may be cached before the source of the information should again be consulted. Zero values are interpreted to mean that the record can only be used for the transaction in progress, and should not be cached.
• Active: This defines whether this NS record is active or not.
