# Govern Windows DNS record creation, modification, and deletion as production changes > Use Manage DNS resource records using DNS server on Windows Server to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/govern-windows-dns-record-creation-modification-and-deletion-as-production-changes/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:15:29+00:00 - Modified: 2026-08-27T12:56:24+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: Cybersecurity, IT, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Manage DNS resource records using DNS server on Windows Server 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 Manage DNS resource records using DNS server on Windows Server ## 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: Govern Windows DNS record creation, modification, and deletion as production changes. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Manage DNS resource records using DNS server on Windows Server](https://learn.microsoft.com/en-us/windows-server/networking/dns/manage-resource-records) from Microsoft supports the following bounded statements: - Windows Server supports creating, modifying, and deleting DNS resource records through DNS Manager and PowerShell. The research record locates this support at Article introduction. - The documented record data includes record type, owner name, host address, and other record-specific information. The research record locates this support at Article introduction. 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 task procedures do not prove that a requested record, TTL, owner, or target is correct for an application or delegation. 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 Article introduction, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Article introduction, 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 Article introduction; Article introduction 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. 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 - [Manage DNS resource records using DNS server on Windows Server](https://learn.microsoft.com/en-us/windows-server/networking/dns/manage-resource-records) — Microsoft ## Primary reference - Name: Manage DNS resource records using DNS server on Windows Server - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/networking/dns/manage-resource-records - Source publication date: 2023-06-15 ## Citation and use Preferred citation: “Govern Windows DNS record creation, modification, and deletion as production changes,” DSE Security, https://update.dsesecurity.com/updates/govern-windows-dns-record-creation-modification-and-deletion-as-production-changes/ 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.