<div>
you can migrate your zones from bind to windows, but you really need it ?, windows PC register automatically, or you want keep both.<br />
Scavenging remove old records from windows, so, if a PC doesn´t refresh &nbsp;his dns registration , it will be removed.<br />
If you want to keep both DNS (win and Unix), you can keep ona of then as primary and on it set Scavenging, and the other DNS can get the zones through &quot;zone transfer&quot; .<br />
<br />
<br />

</div>


you can migrate your zones from bind to windows, but you really need it ?, windows PC register automatically, or you want keep both.
Scavenging remove old records from windows, so, if a PC doesn´t refresh  his dns registration , it will be removed.
If you want to keep both DNS (win and Unix), you can keep ona of then as primary and on it set Scavenging, and the other DNS can get the zones through "zone transfer" .




<div>
<div class="content wysiwyg-content">
We recently transitioned from UNIX bind to Microsoft DNS. My question is if I setup scavenging will the imported dns records for UNIX be scavenged or would I have to manually delete these records? &nbsp;
</div>
</div>


We recently transitioned from UNIX bind to Microsoft DNS. My question is if I setup scavenging will the imported dns records for UNIX be scavenged or would I have to manually delete these records?  

scavenging dns records imported from UNIX

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