# Bound AXFR to a complete SOA-delimited zone transfer over TCP > Use RFC 5936 — DNS Zone Transfer Protocol (AXFR) to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:17:48+00:00 - Modified: 2026-08-27T12:18:09+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Explainer - DSE priority: Advisory - Topics: Cybersecurity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use RFC 5936 — DNS Zone Transfer Protocol (AXFR) to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of RFC 5936 — DNS Zone Transfer Protocol (AXFR) ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Frame this document as a source-led configuration and assurance check: Bound AXFR to a complete SOA-delimited zone transfer over TCP. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [RFC 5936 — DNS Zone Transfer Protocol (AXFR)](https://www.rfc-editor.org/rfc/rfc5936.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements: - An AXFR response that transfers a zone consists of one or more DNS messages carrying the zone’s contents. The research record locates this support at Section 2.2 (AXFR Response). - The AXFR message series begins and ends with the same zone SOA; non-SOA records may otherwise arrive in any order or grouping. The research record locates this support at Section 2.2 (AXFR Response), SOA delimiters and RR ordering. - AXFR uses TCP, but a TCP connection is not necessarily dedicated to a single zone-transfer session. The research record locates this support at Section 4 (Transport). 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.2 (AXFR Response), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Section 2.2 (AXFR Response), SOA delimiters and RR ordering, which observable configuration, record, or test can confirm applicability here? - For source statement 3 at Section 4 (Transport), 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. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence A reviewer should be able to retrace the decision from Section 2.2 (AXFR Response); Section 2.2 (AXFR Response), SOA delimiters and RR ordering; Section 4 (Transport) 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. Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed. ## Official references - [RFC 5936 — DNS Zone Transfer Protocol (AXFR)](https://www.rfc-editor.org/rfc/rfc5936.html) — RFC Editor / Internet Engineering Task Force ## Primary reference - Name: RFC 5936 — DNS Zone Transfer Protocol (AXFR) - Authority: www.rfc-editor.org - URL: https://www.rfc-editor.org/rfc/rfc5936.html - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Bound AXFR to a complete SOA-delimited zone transfer over TCP,” DSE Security, https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.