Authorize secure DNS UPDATE operations at the zone boundary

Treat this document as a focused evidence review: Authorize secure DNS UPDATE operations at the zone boundary. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 3007 — Secure Domain Name System (DNS) Dynamic Update from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• Every secure dynamic update carries TSIG or SIG(0) authentication so the primary server can identify the update principal. The research record locates this support at Section 2 (Authentication).
• A TKEY-derived shared secret established without authentication must not be used to authorize secure dynamic updates. The research record locates this support at Section 2 (Authentication), dynamically configured secrets.
• The primary server denies zone changes by default and permits only actions explicitly authorized by policy for the authenticated principal. The research record locates this support at Section 3 (Policy).

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 2 (Authentication), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 2 (Authentication), dynamically configured secrets, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 3 (Policy), 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.

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

A reviewer should be able to retrace the decision from Section 2 (Authentication); Section 2 (Authentication), dynamically configured secrets; Section 3 (Policy) 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.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• RFC 3007 — Secure Domain Name System (DNS) Dynamic Update — RFC Editor / Internet Engineering Task Force