<div>
<br />
In my experience Scavenging works best when set to match with the DHCP Lease Time. That is, when both Aging Intervals are added together they are equal or slightly greater than the lease time.<br />
<br />
For example, a DHCP Lease Time of 10 days will work well with a No-Refresh Interval of 6 days and a Refresh Interval of 4 days.<br />
<br />
This keeps replication traffic for DNS relatively low, while keeping DNS clear of clients which only leased an address once.<br />
<br />
Remember that Aging Intervals are set per-zone, and it won't do any good at all unless you set Scavenging to run on a regular basis from the Advanced Properties of the DNS Server node in MMC.<br />
<br />
Chris
</div>



In my experience Scavenging works best when set to match with the DHCP Lease Time. That is, when both Aging Intervals are added together they are equal or slightly greater than the lease time.

For example, a DHCP Lease Time of 10 days will work well with a No-Refresh Interval of 6 days and a Refresh Interval of 4 days.

This keeps replication traffic for DNS relatively low, while keeping DNS clear of clients which only leased an address once.

Remember that Aging Intervals are set per-zone, and it won't do any good at all unless you set Scavenging to run on a regular basis from the Advanced Properties of the DNS Server node in MMC.

Chris

<div>
<div class="content wysiwyg-content">
For 2003 domain with XP clients...Many 5805's &nbsp;are recorded in the DNS system event log. &nbsp;When I connect to the machine that is flagged via RDP or Pcanywhere the machine name that I am connecting to is different that the one recorded in the DNS system log Two differnt nmaes are pointing to one IP. &nbsp;Is it necessary to match up DNS scavening with WINS extinction? 
</div>
</div>


For 2003 domain with XP clients...Many 5805's  are recorded in the DNS system event log.  When I connect to the machine that is flagged via RDP or Pcanywhere the machine name that I am connecting to is different that the one recorded in the DNS system log Two differnt nmaes are pointing to one IP.  Is it necessary to match up DNS scavening with WINS extinction? 

WINS / DNS record cleanup

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.

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).

DHCP

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).