Request and interpret EDNS NSID without assigning it global semantics

Use this document to resolve one bounded operational decision: Request and interpret EDNS NSID without assigning it global semantics. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 5001 — DNS Name Server Identifier (NSID) Option from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• A resolver requests server identification by sending an empty NSID option in an EDNS OPT record; request payload data is not allowed. The research record locates this support at Section 2.1 (Resolver Behavior).
• An NSID request identifies only the server that directly receives it, so a recursive server does not transitively forward the client’s request semantics. The research record locates this support at Sections 2.1 (Resolver Behavior) and 2.2 (Name Server Behavior).
• NSID response data is an opaque byte string whose meaning is deliberately outside the DNS protocol. The research record locates this support at Section 2.3 (The NSID Option).

Keep the evidence boundary at these traced claims. They support a review of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

This RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. No current deployment state or change approval follows from the source alone. Validate Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at Section 2.1 (Resolver Behavior), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections 2.1 (Resolver Behavior) and 2.2 (Name Server Behavior), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 2.3 (The NSID Option), which observable configuration, record, or test can confirm applicability here?
• Within authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?
• Could Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state and sanitize protected material before retention.

Verification and evidence

Keep the source locations Section 2.1 (Resolver Behavior); Sections 2.1 (Resolver Behavior) and 2.2 (Name Server Behavior); Section 2.3 (The NSID Option) adjacent to the sanitized artifacts used for comparison. Prefer zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, with enough identity and timing data for an independent recheck.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• RFC 5001 — DNS Name Server Identifier (NSID) Option — RFC Editor / Internet Engineering Task Force