{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/",
        "slug": "choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need",
        "url": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/"
        },
        "title": "Choose Windows primary, secondary, stub, and AD-integrated zones by replication need",
        "summary": "Use DNS zones in DNS Server on Windows Server to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "managed-it",
            "label": "Managed IT operations",
            "alt": "A controlled technology lifecycle progressing from assessment to approved production.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "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:15:36+00:00",
        "modified_at": "2026-08-27T12:53:58+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 507,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of DNS zones in DNS Server on Windows Server",
        "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": "DNS zones in DNS Server on Windows Server",
            "url": "https://learn.microsoft.com/en-us/windows-server/networking/dns/zone-types",
            "published_on": "2025-03-24",
            "authority": "Microsoft Learn"
        },
        "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>Keep this document to one review outcome: Choose Windows primary, secondary, stub, and AD-integrated zones by replication need. 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://learn.microsoft.com/en-us/windows-server/networking/dns/zone-types\" target=\"_blank\" rel=\"noopener noreferrer\">DNS zones in DNS Server on Windows Server</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>Windows DNS Server supports primary, secondary, stub, and reverse lookup zones. The research record locates this support at <strong>Section &#8216;DNS zone types&#8217;</strong>.</li>\n<li>Zone data can be file-backed or stored in Active Directory Domain Services; secondary zones are read-only copies. The research record locates this support at <strong>Primary zones; Secondary zone</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>The zone-type descriptions do not determine the right administrative boundary, transfer authorization, or Active Directory replication scope for a deployment. It does not establish a deployment&#8217;s current state, authorize a production change, prove compliance, or show that Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution 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 &#8216;DNS zone types&#8217;</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Primary zones; Secondary zone</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>What inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?</li>\n<li>Which condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?</li>\n<li>What result would disprove the working assumption and return the issue to the owner?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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 Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.</p>\n<p>Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>Section &#8216;DNS zone types&#8217;</strong>; <strong>Primary zones; Secondary zone</strong>. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/windows-server/networking/dns/zone-types\" target=\"_blank\" rel=\"noopener noreferrer\">DNS zones in DNS Server on Windows Server</a> — Microsoft</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Choose Windows primary, secondary, stub, and AD-integrated zones by replication need. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official DNS zones in DNS Server on Windows Server from Microsoft supports the following bounded statements:\n\nWindows DNS Server supports primary, secondary, stub, and reverse lookup zones. The research record locates this support at Section ‘DNS zone types’.\nZone data can be file-backed or stored in Active Directory Domain Services; secondary zones are read-only copies. The research record locates this support at Primary zones; Secondary zone.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles and the conditions the source actually describes.\nWhat the source does not establish\nThe zone-type descriptions do not determine the right administrative boundary, transfer authorization, or Active Directory replication scope for a deployment. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at Section ‘DNS zone types’, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Primary zones; Secondary zone, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?\nWhich condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE 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 Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section ‘DNS zone types’; Primary zones; Secondary zone. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.\nRecord 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.\nOfficial references\n\nDNS zones in DNS Server on Windows Server — Microsoft",
        "content_markdown": "Keep this document to one review outcome: Choose Windows primary, secondary, stub, and AD-integrated zones by replication need. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [DNS zones in DNS Server on Windows Server](https://learn.microsoft.com/en-us/windows-server/networking/dns/zone-types) from Microsoft supports the following bounded statements:\n\n- Windows DNS Server supports primary, secondary, stub, and reverse lookup zones. The research record locates this support at Section ‘DNS zone types’.\n\n- Zone data can be file-backed or stored in Active Directory Domain Services; secondary zones are read-only copies. The research record locates this support at Primary zones; Secondary zone.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles and the conditions the source actually describes.\n\n## What the source does not establish\n\nThe zone-type descriptions do not determine the right administrative boundary, transfer authorization, or Active Directory replication scope for a deployment. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution are healthy. Documented options are review inputs, not universal mandates.\n\n## Applicability questions\n\n- For source statement 1 at Section ‘DNS zone types’, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Primary zones; Secondary zone, which observable configuration, record, or test can confirm applicability here?\n\n- What inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?\n\n- Which condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?\n\n- What result would disprove the working assumption and return the issue to the owner?\n\n## DSE recommendation:\n\nDSE 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 Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\n\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section ‘DNS zone types’; Primary zones; Secondary zone. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.\n\nRecord 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.\n\n## Official references\n\n- [DNS zones in DNS Server on Windows Server](https://learn.microsoft.com/en-us/windows-server/networking/dns/zone-types) — Microsoft"
    },
    "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/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/",
                "url": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Choose Windows primary, secondary, stub, and AD-integrated zones by replication need",
                        "item": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/#article",
                "identifier": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/",
                "url": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/",
                "headline": "Choose Windows primary, secondary, stub, and AD-integrated zones by replication need",
                "description": "Use DNS zones in DNS Server on Windows Server to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use DNS zones in DNS Server on Windows Server to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Choose Windows primary, secondary, stub, and AD-integrated zones by replication need. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official DNS zones in DNS Server on Windows Server from Microsoft supports the following bounded statements:\n\nWindows DNS Server supports primary, secondary, stub, and reverse lookup zones. The research record locates this support at Section ‘DNS zone types’.\nZone data can be file-backed or stored in Active Directory Domain Services; secondary zones are read-only copies. The research record locates this support at Primary zones; Secondary zone.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles and the conditions the source actually describes.\nWhat the source does not establish\nThe zone-type descriptions do not determine the right administrative boundary, transfer authorization, or Active Directory replication scope for a deployment. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at Section ‘DNS zone types’, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Primary zones; Secondary zone, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?\nWhich condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE 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 Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section ‘DNS zone types’; Primary zones; Secondary zone. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.\nRecord 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.\nOfficial references\n\nDNS zones in DNS Server on Windows Server — Microsoft",
                "datePublished": "2026-08-27T12:15:36+00:00",
                "dateModified": "2026-08-27T12:53:58+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/"
                },
                "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/choose-windows-primary-secondary-stub-and-ad-integrated-zones-by-replication-need/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Choose Windows primary, secondary, stub, and AD-integrated zones by replication need"
                },
                "articleSection": [
                    "Cybersecurity",
                    "IT",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "IT",
                    "Networks & Infrastructure",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 507,
                "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": "DNS zones in DNS Server on Windows Server",
                    "url": "https://learn.microsoft.com/en-us/windows-server/networking/dns/zone-types",
                    "datePublished": "2025-03-24"
                }
            }
        ]
    }
}