# Set-DnsServerEDns: change dns server edns with rollback checks > Use Set-DnsServerEDns to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/set-dnsserveredns-change-dns-server-edns-with-rollback-checks/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:02:59+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 Set-DnsServerEDns 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-DnsServerEDns ## 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: Set-DnsServerEDns: change dns server edns with rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Set-DnsServerEDns](https://learn.microsoft.com/en-us/powershell/module/dnsserver/set-dnsserveredns?view=windowsserver2025-ps) from Microsoft supports the following bounded statements: - At DESCRIPTION, Microsoft states: “The Set-DnsServerEDns cmdlet changes extension mechanisms for DNS (EDNS) settings on a Domain Name System (DNS) server.” The research record locates this support at DESCRIPTION. - At Example 1: Change the EDNS cache setting, Microsoft states: “This command changes the EDNS cache setting on a local DNS server.” The research record locates this support at Example 1: Change the EDNS cache setting. The source support ends with the statements listed above. Use them to examine Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles in the applicable environment, not to imply a wider guarantee. ## 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: Change the EDNS cache setting, 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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 Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations DESCRIPTION; Example 1: Change the EDNS cache setting. 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. Label this evidence set DSE-20260827-267 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [Set-DnsServerEDns](https://learn.microsoft.com/en-us/powershell/module/dnsserver/set-dnsserveredns?view=windowsserver2025-ps) — Microsoft ## Primary reference - Name: Set-DnsServerEDns - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/powershell/module/dnsserver/set-dnsserveredns?view=windowsserver2025-ps - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Set-DnsServerEDns: change dns server edns with rollback checks,” DSE Security, https://update.dsesecurity.com/updates/set-dnsserveredns-change-dns-server-edns-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.