{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/",
        "slug": "bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp",
        "url": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/"
        },
        "title": "Bound AXFR to a complete SOA-delimited zone transfer over TCP",
        "summary": "Use RFC 5936 — DNS Zone Transfer Protocol (AXFR) to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T12:17:48+00:00",
        "modified_at": "2026-08-27T12:18:09+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 598,
        "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.",
        "primary_source": {
            "name": "RFC 5936 — DNS Zone Transfer Protocol (AXFR)",
            "url": "https://www.rfc-editor.org/rfc/rfc5936.html",
            "published_on": null,
            "authority": "www.rfc-editor.org"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>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.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.rfc-editor.org/rfc/rfc5936.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 5936 — DNS Zone Transfer Protocol (AXFR)</a> from RFC Editor / Internet Engineering Task Force supports the following bounded statements:</p>\n<ul>\n<li>An AXFR response that transfers a zone consists of one or more DNS messages carrying the zone&#8217;s contents. The research record locates this support at <strong>Section 2.2 (AXFR Response)</strong>.</li>\n<li>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 <strong>Section 2.2 (AXFR Response), SOA delimiters and RR ordering</strong>.</li>\n<li>AXFR uses TCP, but a TCP connection is not necessarily dedicated to a single zone-transfer session. The research record locates this support at <strong>Section 4 (Transport)</strong>.</li>\n</ul>\n<p>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.</p>\n<h2>What the source does not establish</h2>\n<p>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&#8217;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.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Section 2.2 (AXFR Response)</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Section 2.2 (AXFR Response), SOA delimiters and RR ordering</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 3 at <strong>Section 4 (Transport)</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>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?</li>\n<li>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?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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.</p>\n<p>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.</p>\n<h2>Verification and evidence</h2>\n<p>A reviewer should be able to retrace the decision from <strong>Section 2.2 (AXFR Response)</strong>; <strong>Section 2.2 (AXFR Response), SOA delimiters and RR ordering</strong>; <strong>Section 4 (Transport)</strong> 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.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.rfc-editor.org/rfc/rfc5936.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 5936 — DNS Zone Transfer Protocol (AXFR)</a> — RFC Editor / Internet Engineering Task Force</li>\n</ul>",
        "content_text": "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.\nSource fact:\nThe official RFC 5936 — DNS Zone Transfer Protocol (AXFR) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nAn 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).\nThe 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.\nAXFR 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).\n\nThe 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nFor source statement 1 at Section 2.2 (AXFR Response), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 2.2 (AXFR Response), SOA delimiters and RR ordering, which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 4 (Transport), which observable configuration, record, or test can confirm applicability here?\nWithin 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?\nCould 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?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE 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.\nTranslate 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.\nVerification and evidence\nA 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.\nKeep 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.\nOfficial references\n\nRFC 5936 — DNS Zone Transfer Protocol (AXFR) — RFC Editor / Internet Engineering Task Force",
        "content_markdown": "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.\n\n## Source fact:\n\nThe 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:\n\n- 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).\n\n- 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.\n\n- 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).\n\nThe 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.\n\n## What the source does not establish\n\nThis 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.\n\n## Applicability questions\n\n- For source statement 1 at Section 2.2 (AXFR Response), which observable configuration, record, or test can confirm applicability here?\n\n- 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?\n\n- For source statement 3 at Section 4 (Transport), which observable configuration, record, or test can confirm applicability here?\n\n- 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?\n\n- 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?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\n\n## DSE recommendation:\n\nDSE 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.\n\nTranslate 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.\n\n## Verification and evidence\n\nA 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.\n\nKeep 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.\n\n## Official references\n\n- [RFC 5936 — DNS Zone Transfer Protocol (AXFR)](https://www.rfc-editor.org/rfc/rfc5936.html) — RFC Editor / Internet Engineering Task Force"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/",
                "url": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Bound AXFR to a complete SOA-delimited zone transfer over TCP",
                        "item": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/#article",
                "identifier": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/",
                "url": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/",
                "headline": "Bound AXFR to a complete SOA-delimited zone transfer over TCP",
                "description": "Use RFC 5936 — DNS Zone Transfer Protocol (AXFR) to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use RFC 5936 — DNS Zone Transfer Protocol (AXFR) to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "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.\nSource fact:\nThe official RFC 5936 — DNS Zone Transfer Protocol (AXFR) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nAn 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).\nThe 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.\nAXFR 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).\n\nThe 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nFor source statement 1 at Section 2.2 (AXFR Response), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 2.2 (AXFR Response), SOA delimiters and RR ordering, which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 4 (Transport), which observable configuration, record, or test can confirm applicability here?\nWithin 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?\nCould 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?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE 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.\nTranslate 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.\nVerification and evidence\nA 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.\nKeep 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.\nOfficial references\n\nRFC 5936 — DNS Zone Transfer Protocol (AXFR) — RFC Editor / Internet Engineering Task Force",
                "datePublished": "2026-08-27T12:17:48+00:00",
                "dateModified": "2026-08-27T12:18:09+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/bound-axfr-to-a-complete-soa-delimited-zone-transfer-over-tcp/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Bound AXFR to a complete SOA-delimited zone transfer over TCP"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 598,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "RFC 5936 — DNS Zone Transfer Protocol (AXFR)",
                    "url": "https://www.rfc-editor.org/rfc/rfc5936.html"
                }
            }
        ]
    }
}