Yes Sean, that's the one. Thanks for finding it.
> On Nov 17, 2014, at 12:10, "Kelsey, John" <[email protected]> wrote: > > I saw that and I have those credentials configured. Am I ok on the DNS > scavenging setup or should those numbers be altered based on our 3 day lease > time? > > Thanks all! > > From: [email protected] [mailto:[email protected]] > On Behalf Of Sean Martin > Sent: Monday, November 17, 2014 3:05 PM > To: [email protected] > Subject: Re: [NTSysADM] DNS and DHCP and Scavenging...oh my! > > Are you referring to this? > > http://blogs.technet.com/b/stdqry/archive/2012/04/03/dhcp-server-in-dcs-and-dns-registrations.aspx > - Sean > > On Mon, Nov 17, 2014 at 10:06 AM, Daniel Chenault <[email protected]> wrote: > There is a known issue. With running DHCP n a DC. I'm on mobile; don't have > the article handy. > > On Nov 17, 2014, at 10:43, "Kelsey, John" <[email protected]> wrote: > > Running into an issue in our VMware environment with linked clones > recomposing. VMware support has pointed me in the direction of some kind of > DNS registration issue. > > So we have a 2008 DHCP server (running on a DC) and we have the dynamic > updates enabled. Our lease time is 3 days. > > Most of the docs I’ve found said you generally set the scavenging time to > your lease time -1 day. So I changed it from the default to 2. I have this > enabled on a single DC and its disabled on all of the others. > > I’ve found conflicting information on how to set the refresh/no-refresh > intervals. I currently have it set to 1/1. Should it be equal or greater > than the least duration, or equal or less than the lease duration? Or am I > all wet here? > > Thanks all. Happy Monday > > > *************************************** > John C. Kelsey, MCSE, CCNA > Network Architect > Penn Highlands DuBois > (: 814.375.3073 > 2 : 814.375.4005 > *: [email protected] > *************************************** > <image001.png> > > This email and any attached files are confidential and intended solely for > the intended recipient(s). If you are not the named recipient you should not > read, distribute, copy or alter this email. Any views or opinions expressed > in this email are those of the author and do not represent those of Penn > Highlands Healthcare or its affiliates.. Warning: Although precautions have > been taken to make sure no viruses are present in this email, the company > cannot accept responsibility for any loss or damage that arise from the use > of this email or attachments. > > This email and any attached files are confidential and intended solely for > the intended recipient(s). If you are not the named recipient you should not > read, distribute, copy or alter this email. Any views or opinions expressed > in this email are those of the author and do not represent those of Penn > Highlands Healthcare or its affiliates.. Warning: Although precautions have > been taken to make sure no viruses are present in this email, the company > cannot accept responsibility for any loss or damage that arise from the use > of this email or attachments.
