<div>
<div class="content wysiwyg-content">
We Have An Organization - ~ 1500 PCs - We Utilize Microsoft Active Directory Domain Controllers. (DDNS Integrated.)<br />
<br />
We have 3 connected sites, each with their own AD Controller. (1 site has two AD Controllers.)<br />
<br />
Due to our noticing 'dropped' DNS Resource Records, we're wondering is it;<br />
<br />
Better to have only ONE AD Controller (DDNS Integrated) performing the scavenging routine and sharing that/those changes with their counterparts? Or utilizing/turning on scavenging on each/every AD controller?
</div>
</div>


We Have An Organization - ~ 1500 PCs - We Utilize Microsoft Active Directory Domain Controllers. (DDNS Integrated.)

We have 3 connected sites, each with their own AD Controller. (1 site has two AD Controllers.)

Due to our noticing 'dropped' DNS Resource Records, we're wondering is it;

Better to have only ONE AD Controller (DDNS Integrated) performing the scavenging routine and sharing that/those changes with their counterparts? Or utilizing/turning on scavenging on each/every AD controller?

Best Practice To Have ALL Microsoft AD Controllers With DDNS Perform Scavening Or Just One Primary

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.

Microsoft Server OS

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 Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).