Dear all, am looking to understand a bit better the processes of windows dns server scavening processes;
1. am i right in my understanding that scavenging does need to be explicitly on a zone if it is enabled at a server level; read somewhere that behaviour varies according to AD-integrated zones / primary zones documentation throughout seems a little inconsistent on this one if then it is enabled at a server level how do you get a zone managed by that server to be 'un-enabled' for scavenging - 2. assuming the zone / server is enabled for scavenging have read that if it is enabled subsequent to a record being added / refreshed then those records will not in fact in fact be scavenged ?? have seen the /ageallrecords on dnscmd - as i read this ages all the records in a zone - including manually entered records ?? which of course are not able to refresh and therefore would ultimately be removed ? this would work if of course all records in a zone were from dynamic update capable clients but how do you handle safely the scenario where you have some records that were dynamically added (and have since become stale) that need to be removed without knocking out the manual records ?? TIA GT List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
