<div>
The time (thankfully, only seen this behavior once) I saw this it was due to AD database corruption on one of the domain controllers - as part of the Windows 2008 recovery rocess it wiped the ntds.dit file and started replication, which blew away all DNS settings.<br />
<br />
I'd check the system logs on each DC for any active directory errors first to see if that's the issue.
</div>


The time (thankfully, only seen this behavior once) I saw this it was due to AD database corruption on one of the domain controllers - as part of the Windows 2008 recovery rocess it wiped the ntds.dit file and started replication, which blew away all DNS settings.

I'd check the system logs on each DC for any active directory errors first to see if that's the issue.

<div>
I turned off scaveging and it seems to be working.
</div>


I turned off scaveging and it seems to be working.

<div>
<div class="content wysiwyg-content">
I am using single domain, &quot;mydomain.com&quot;, and have 7 WAN sites using the domain. &nbsp;In each site I have a DC, a GC, WINS server and DNS server.<br />
<br />
Each DNS server is it's own SOA and all are set to replicate to ALL Domain Controllers in the forest/domain.<br />
<br />
Some DNS &quot;A&quot; records seem to disappear sporadically but my Alias &quot;C&quot; records do not. &nbsp;Knowing this I assume the dynamic updates are occurring in other sites not responsible for the &quot;A&quot; record and replicating the to other servers in the domain.<br />
<br />
What are the basic configuration steps do I need to perform to correct the &quot;Phantom&quot; record removal?
</div>
</div>


I am using single domain, "mydomain.com", and have 7 WAN sites using the domain.  In each site I have a DC, a GC, WINS server and DNS server.

Each DNS server is it's own SOA and all are set to replicate to ALL Domain Controllers in the forest/domain.

Some DNS "A" records seem to disappear sporadically but my Alias "C" records do not.  Knowing this I assume the dynamic updates are occurring in other sites not responsible for the "A" record and replicating the to other servers in the domain.

What are the basic configuration steps do I need to perform to correct the "Phantom" record removal?

DNS records dissapearing

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.