# Set-DnsServerClientSubnet: change dns server client subnet with bounded evidence > Use Set-DnsServerClientSubnet to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/set-dnsserverclientsubnet-change-dns-server-client-subnet-with-bounded-evidence/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:03:31+00:00 - Modified: 2026-08-27T17:22:20+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Playbook - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Set-DnsServerClientSubnet 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 Set-DnsServerClientSubnet ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Set-DnsServerClientSubnet: change dns server client subnet with bounded evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Set-DnsServerClientSubnet](https://learn.microsoft.com/en-us/powershell/module/dnsserver/set-dnsserverclientsubnet?view=windowsserver2025-ps) from Microsoft supports the following bounded statements: - At DESCRIPTION, Microsoft states: “The Set-DnsServerClientSubnet cmdlet updates the IP addresses in a client subnet on a Domain Name System (DNS) server.” The research record locates this support at DESCRIPTION. - At DESCRIPTION, Microsoft states: “You can modify the IPv4 addresses, IPv6 addresses, or both kinds of addresses.” 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. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## 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? - 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. 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. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence Keep the source locations DESCRIPTION; DESCRIPTION adjacent to the sanitized artifacts used for comparison. Prefer PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, with enough identity and timing data for an independent recheck. Label this evidence set DSE-20260827-235 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 - [Set-DnsServerClientSubnet](https://learn.microsoft.com/en-us/powershell/module/dnsserver/set-dnsserverclientsubnet?view=windowsserver2025-ps) — Microsoft ## Primary reference - Name: Set-DnsServerClientSubnet - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/powershell/module/dnsserver/set-dnsserverclientsubnet?view=windowsserver2025-ps - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Set-DnsServerClientSubnet: change dns server client subnet with bounded evidence,” DSE Security, https://update.dsesecurity.com/updates/set-dnsserverclientsubnet-change-dns-server-client-subnet-with-bounded-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.