# Get-DnsServerZone: inventory dns server zone with before-and-after evidence > Use Get-DnsServerZone to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/get-dnsserverzone-inventory-dns-server-zone-with-before-and-after-evidence/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:03:02+00:00 - Modified: 2026-08-27T17:26:01+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Guide - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Get-DnsServerZone 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 Get-DnsServerZone ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to connect an official requirement or behavior to observable evidence: Get-DnsServerZone: inventory dns server zone with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Get-DnsServerZone](https://learn.microsoft.com/en-us/powershell/module/dnsserver/get-dnsserverzone?view=windowsserver2025-ps) from Microsoft supports the following bounded statements: - At DESCRIPTION, Microsoft states: “The Get-DnsServerZone cmdlet gets the zones that exist on a Domain Name System (DNS) server.” The research record locates this support at DESCRIPTION. - At Example 1: Get GlobalName zone settings, Microsoft states: “This command gets details of all zones on the local DNS server.” The research record locates this support at Example 1: Get GlobalName zone settings. Keep the evidence boundary at these traced claims. They support a review of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles; they do not support conclusions outside the source’s stated conditions. ## What the source does not establish The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. 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 DESCRIPTION, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Example 1: Get GlobalName zone settings, which observable configuration, record, or test can confirm applicability here? - Which deployed instance of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles will be compared with the source, and why that instance? - How will the review distinguish a source mismatch from a failure in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution? - Who approves the conclusion, exception, test window, and rollback threshold? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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. If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention. ## Verification and evidence Tie each conclusion back to DESCRIPTION; Example 1: Get GlobalName zone settings and to observable material such as PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Preserve provenance and stable identifiers without copying secrets into the evidence set. Label this evidence set DSE-20260827-264 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent. ## Official references - [Get-DnsServerZone](https://learn.microsoft.com/en-us/powershell/module/dnsserver/get-dnsserverzone?view=windowsserver2025-ps) — Microsoft ## Primary reference - Name: Get-DnsServerZone - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/powershell/module/dnsserver/get-dnsserverzone?view=windowsserver2025-ps - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Get-DnsServerZone: inventory dns server zone with before-and-after evidence,” DSE Security, https://update.dsesecurity.com/updates/get-dnsserverzone-inventory-dns-server-zone-with-before-and-after-evidence/ 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.