What Is NS record?

Who answers for the zone

When an email setup checker looks for an SPF or DKIM record, it needs an answer from the DNS infrastructure responsible for that name. NS records identify authoritative nameservers for a zone. A registrar's delegation and the zone's own records should be consistent. Registering a domain, hosting its website and operating its DNS can involve three different companies.

Changing an MX or TXT record inside an inactive DNS account will not fix delivery. The editor may show the value you entered while public resolvers continue asking another provider. This is why the first useful question is often which nameservers are actually authoritative, rather than whether someone clicked save in a dashboard.

An email migration example

Suppose a team moves DNS providers while keeping the same mailboxes. Before changing delegation, inventory the active zone and reproduce the required website and email records at the destination. Include verification records, provider-specific DKIM names and any reporting policies. A nameserver change does not automatically copy those records, and moving DNS does not itself move a mailbox or its messages.

Evidence to keep

Record the domain, current delegation, authoritative answers, responsible account and change time. Compare answers from the authoritative servers with those returned by recursive resolvers. That separates a missing publication from an older cached response. If delegation is wrong, repeatedly editing the TXT value at the abandoned provider will only make the incident harder to understand.

For an outbound operation, DNS ownership is an operational dependency. Keep access and recovery responsibilities documented before adding more sending domains. Treat nameservers as the location of the authoritative configuration, with MX and authentication records as separate settings that still require their own validation.