Authenticate a complete DNS transaction with SIG(0), not a single RRset

Use this document to resolve one bounded operational decision: Authenticate a complete DNS transaction with SIG(0), not a single RRset. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 2931 — DNS Request and Transaction Signatures ( SIG(0)s ) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• A SIG(0) request signature is placed at the end of the additional section and covers the DNS request, including its DNS header but excluding UDP/IP headers. The research record locates this support at Section 3.1 (Calculating Request and Transaction SIGs).
• A response transaction signature covers both the full query and the corresponding response, including their DNS headers but excluding transport and IP headers. The research record locates this support at Section 3.1 (Calculating Request and Transaction SIGs), response calculation.
• A valid response SIG(0) authenticates the queried server and transaction integrity, but it does not directly authenticate each data RR in the message. The research record locates this support at Section 3.2 (Processing Responses and SIG(0) RRs).

The source support ends with the statements listed above. Use them to examine authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers in the applicable environment, not to imply a wider guarantee.

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. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at Section 3.1 (Calculating Request and Transaction SIGs), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 3.1 (Calculating Request and Transaction SIGs), response calculation, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 3.2 (Processing Responses and SIG(0) RRs), 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Section 3.1 (Calculating Request and Transaction SIGs); Section 3.1 (Calculating Request and Transaction SIGs), response calculation; Section 3.2 (Processing Responses and SIG(0) RRs) through zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior. Record what was collected, where, when, by whom, and which system or role it represents.

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 2931 — DNS Request and Transaction Signatures ( SIG(0)s ) — RFC Editor / Internet Engineering Task Force