>>Isn't that only true if you aren't using Windows 200X for DHCP services? Possibly. I have not personally seen a difference in the behavior, though. I also do not agree with the document. Test it out, in a lab. Scavenging and aging confuses me, and I try very hard to get a handle on it. I suggest you do it in a lab because one of the "ooops" moment of again/scavening is the high probability of your deleting valid records and generating huge helpdesk calls. Sincerely,
Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I Microsoft MVP - Directory Services www.readymaids.com - we know IT www.akomolafe.com Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon ________________________________ From: [EMAIL PROTECTED] on behalf of Rimmerman, Russ Sent: Mon 11/8/2004 11:55 AM To: [EMAIL PROTECTED] Subject: RE: Spam: Spam: RE: [ActiveDir] DNS Scavenging Isn't that only true if you aren't using Windows 200X for DHCP services? >From the DNS whitepaper it says: To ensure that no records are deleted before the dynamic update client has time to refresh them, the refresh interval must be greater than the refresh period for each record subjected to scavenging within a zone. Many different services might refresh records at different intervals; for example, Netlogon refreshes records once an hour, cluster servers generally refresh records every 15 to 20 minutes, DHCP servers refresh records at renewal of IP address leases, and Windows 2000-based computers refresh their A and PTR resource records every 24 hours. Usually, the DHCP service requires the longest refresh interval of all services. If you are using the Windows 2000 DHCP service, you can use the default scavenging and aging values. If you are using another DHCP server, you might need to modify the defaults. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, November 08, 2004 11:52 AM To: [EMAIL PROTECTED] Subject: Spam: Spam: RE: [ActiveDir] DNS Scavenging Depending on how large your environment is, you may be best served by just doing regular scavenging as a part of your weekly/bi-weekly/monthly maintenance. The reason I say this is that the Scavenging option you see in the GUI is a little bit hard to get a handle on. dnscmd /startscavenging will do the work for you. Having said that, a little understanding of HOW "scavenging period", "no-refresh interval" and "refresh interval" work together to achieve desired scavenging is VERY necessary if you are going to go through the GUI scavenging settings. WRT to the Lease Period question, let's take an example: IF your lease period is 5 days AND your Scavenging Period is 7 days AND your no-refresh interval is 7 days AND your refresh interval is 7 days. The above will create unintended result. First, when your client's lease expires, and it obtains a new lease (NEW) IP, that client won't be able to register that IP for 2 more days, because your "no-refresh" inteval says "you can't update this record until it is over 7 days old". Then the old record will remain in placce for 2 more days, at which time it will be updated. However, you will still have 2 records for this client for ANOTHER 7 more days because your "Refresh Interval" says "don't clean old record unless it has NOT been updated 7 days AFTER it has expired". Makes your head hurt? Yes, I bursted a vein getting that all out, too :) As to the question of replicating Scavenging setting. I do not believe that this setting is replicated at all. I am not very positive on this, but I would wager that it's server-specific and you would have to enable it on ALL your DCs if you want all of them to be doing scavening for you. Enabling it on all your DCs is not, necessary, though. One or 2 DCs should be able to handle the scavenging for you. I still vote for dnscmd as the better option. Use it to enable scavening, and use it to perform the scavenging periodically. Sincerely, Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I Microsoft MVP - Directory Services www.readymaids.com - we know IT www.akomolafe.com Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon ________________________________ From: [EMAIL PROTECTED] on behalf of Rimmerman, Russ Sent: Mon 11/8/2004 8:44 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] DNS Scavenging What's the recommended best way to have scavenging set up? Enable on all your AD integrated DNS servers, or enable on one and let it replicate to all the others? Also, if our DHCP lease time is 5 days, would 7 days be an appropriate scavenging time? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of the Cooper Cameron Corporation and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of the Cooper Cameron Corporation and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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/ 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/
