<div>
setup dns scavenging with half period of dhcp scope lease<br />
also its already enabled on zone level<br />
enable it on any one dns server by navigating dns server console \ server \ right click \ properties \ advanced tab<br />
<br />
there many articles available how to set it
</div>


setup dns scavenging with half period of dhcp scope lease
also its already enabled on zone level
enable it on any one dns server by navigating dns server console \ server \ right click \ properties \ advanced tab

there many articles available how to set it

Director of Member Experience  

Stacy Richard

<div>
As Mahesh mentioned DNS scavenging for half the length of your DHCP lease is the best way to go. &nbsp;This also meets best practice that you requested.<br />
What is likely happening is your DHCP lease is expiring and the system will register itself with its new IP address. &nbsp;However since you do not have scavenging turned on the old ip address will remain in DNS.
</div>


As Mahesh mentioned DNS scavenging for half the length of your DHCP lease is the best way to go.  This also meets best practice that you requested.
What is likely happening is your DHCP lease is expiring and the system will register itself with its new IP address.  However since you do not have scavenging turned on the old ip address will remain in DNS.

<div>
<div class="content wysiwyg-content">
This question is also a piggyback on my newly asked question about: &nbsp;SCCM clean up regarding clients showing up on DNS duplicate wise. <br />
<br />
<a href="https://www.experts-exchange.com/questions/29145134/SCCM-clean-up-regarding-clients.html" rel="ugc">https://www.experts-exchange.com/questions/29145134/SCCM-clean-up-regarding-clients.html</a><br />
<br />
<br />
&nbsp;The issue of DNS scavenging was brought up, but was shot down because of the affects it could have. &nbsp;Also need some type of best practice resolution to this as well. &nbsp;Preferably with some document links and solutions.
</div>
</div>


This question is also a piggyback on my newly asked question about:  SCCM clean up regarding clients showing up on DNS duplicate wise. 

https://www.experts-exchange.com/questions/29145134/SCCM-clean-up-regarding-clients.html


 The issue of DNS scavenging was brought up, but was shot down because of the affects it could have.  Also need some type of best practice resolution to this as well.  Preferably with some document links and solutions.

DNS issues

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

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.

Systems Center Configuration Manager (SCCM, formerly known as Systems Management Server) is Microsoft’s system software for managing large groups of not only Microsoft computers, but those running other operating systems, such as Linux, OS-X, and various mobile technologies.

SCCM

Security is the protection of information systems from theft or damage to the hardware, the software, and the information on them, as well as from disruption or misdirection of the services they provide. The main goal of security is protecting assets, and an asset is anything of value and worthy of protection.  Information Security is a discipline of protecting information assets from threats through safeguards to achieve the objectives of confidentiality, integrity, and availability or CIA for short. On the other hand, disclosure, alteration, and disruption (DAD) compromise the security objectives.