# Get-DnsServerRecursionScope: inventory dns server recursion scope with rollback checks > Use Get-DnsServerRecursionScope to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/get-dnsserverrecursionscope-inventory-dns-server-recursion-scope-with-rollback-checks/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:02:44+00:00 - Modified: 2026-08-27T17:26:01+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Checklist - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Get-DnsServerRecursionScope 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-DnsServerRecursionScope ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Get-DnsServerRecursionScope: inventory dns server recursion scope with rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Get-DnsServerRecursionScope](https://learn.microsoft.com/en-us/powershell/module/dnsserver/get-dnsserverrecursionscope?view=windowsserver2025-ps) from Microsoft supports the following bounded statements: - At DESCRIPTION, Microsoft states: “The Get-DnsServerRecursionScope cmdlet gets the Domain Name System (DNS) server recursion scopes.” The research record locates this support at DESCRIPTION. - At DESCRIPTION, Microsoft states: “Specify a scope by name to get only that scope.” The research record locates this support at DESCRIPTION. Only the traced statements above are asserted as source facts. Apply the review to Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles after confirming that the source and deployed context match. ## 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. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, and treat examples or options as conditional inputs rather than defaults. ## Applicability questions - For source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at DESCRIPTION, 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. Begin by recording scope and current state before deciding whether a change is warranted. 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. An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution before and after the test, and store only sanitized operational evidence. ## Verification and evidence A reviewer should be able to retrace the decision from DESCRIPTION; DESCRIPTION through PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Record what was collected, where, when, by whom, and which system or role it represents. Label this evidence set DSE-20260827-282 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. 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 - [Get-DnsServerRecursionScope](https://learn.microsoft.com/en-us/powershell/module/dnsserver/get-dnsserverrecursionscope?view=windowsserver2025-ps) — Microsoft ## Primary reference - Name: Get-DnsServerRecursionScope - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/powershell/module/dnsserver/get-dnsserverrecursionscope?view=windowsserver2025-ps - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Get-DnsServerRecursionScope: inventory dns server recursion scope with rollback checks,” DSE Security, https://update.dsesecurity.com/updates/get-dnsserverrecursionscope-inventory-dns-server-recursion-scope-with-rollback-checks/ 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.