Choose Windows primary, secondary, stub, and AD-integrated zones by replication need

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.

Source fact:

The official DNS zones in DNS Server on Windows Server from Microsoft supports the following bounded statements:

• Windows DNS Server supports primary, secondary, stub, and reverse lookup zones. The research record locates this support at Section ‘DNS zone types’.
• 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.

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.

What the source does not establish

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’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.

Applicability questions

• For source statement 1 at Section ‘DNS zone types’, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Primary zones; Secondary zone, which observable configuration, record, or test can confirm applicability here?
• 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?
• Which condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

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 Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, 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 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.

Verification and evidence

Evidence 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.

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

• DNS zones in DNS Server on Windows Server — Microsoft