# Scope Phantoms, tombstones, and the infrastructure master in observed AD/DNS state > Use Phantoms, tombstones, and the infrastructure master to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/scope-phantoms-tombstones-and-the-infrastructure-master-in-observed-ad-dns-state/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:01:30+00:00 - Modified: 2026-08-27T17:33:23+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Briefing - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Phantoms, tombstones, and the infrastructure master 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 Phantoms, tombstones, and the infrastructure master ## 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 resolve one bounded operational decision: Scope Phantoms, tombstones, and the infrastructure master in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Phantoms, tombstones, and the infrastructure master](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/phantoms-tombstones-infrastructure-master) from Microsoft supports the following bounded statements: - At Introduction below H1, Microsoft states: “This article describes how phantoms are used in Windows Server.” The research record locates this support at Introduction below H1. - At More information, Microsoft states: “Phantom objects are low-level database objects that Active Directory uses for internal management operations.” The research record locates this support at More information. Only the traced statements above are asserted as source facts. Apply the review to Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services 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, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## Applicability questions - For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at More information, which observable configuration, record, or test can confirm applicability here? - Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services 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, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials? - 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 Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation. Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials. Handle credentials, keys, recovery data, and personal information through approved secure channels. ## Verification and evidence A reviewer should be able to retrace the decision from Introduction below H1; More information through sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Record what was collected, where, when, by whom, and which system or role it represents. Label this evidence set DSE-20260827-356 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 - [Phantoms, tombstones, and the infrastructure master](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/phantoms-tombstones-infrastructure-master) — Microsoft ## Primary reference - Name: Phantoms, tombstones, and the infrastructure master - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/phantoms-tombstones-infrastructure-master - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Scope Phantoms, tombstones, and the infrastructure master in observed AD/DNS state,” DSE Security, https://update.dsesecurity.com/updates/scope-phantoms-tombstones-and-the-infrastructure-master-in-observed-ad-dns-state/ 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.