Trigger secondary refresh checks with NOTIFY without treating notice as transfer

Use this document to connect an official requirement or behavior to observable evidence: Trigger secondary refresh checks with NOTIFY without treating notice as transfer. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 1996 — A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An SOA NOTIFY makes a secondary perform a refresh check against the notifying master; transfer follows only if the SOA serial increased. The research record locates this support at Section 3.11 (NOTIFY event processing).
• Data in a NOTIFY answer is only a hint and must never directly update the secondary, force a transfer, or change refresh timers. The research record locates this support at Sections 3.7 and 3.8 (NOTIFY Message).
• A secondary should ignore a NOTIFY request from a host that is not configured as a master for the affected zone. The research record locates this support at Section 3.10 (NOTIFY Message).

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers and the conditions the source actually describes.

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 3.11 (NOTIFY event processing), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections 3.7 and 3.8 (NOTIFY Message), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 3.10 (NOTIFY Message), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Tie each conclusion back to Section 3.11 (NOTIFY event processing); Sections 3.7 and 3.8 (NOTIFY Message); Section 3.10 (NOTIFY Message) and to observable material such as zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior. Preserve provenance and stable identifiers without copying secrets into the evidence set.

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 1996 — A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY) — RFC Editor / Internet Engineering Task Force