Can you point to a source for this “known issue”? Every domain I’ve worked with had DHCP on a DC.
Regards, Hank Arnold Consumer Security “There are 10 kinds of people in the world... Those who understand binary and those who don't.” My Blog: <http://it.toolbox.com/blogs/personal-pc-assistant/> http://it.toolbox.com/blogs/personal-pc-assistant/ Twitter: @Hank_PCDoc Facebook: <https://www.facebook.com/hank.arnold.96> https://www.facebook.com/hank.arnold.96 From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Monday, November 17, 2014 2:06 PM To: [email protected] Subject: Re: [NTSysADM] DNS and DHCP and Scavenging...oh my! 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] <mailto:[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 * : 814.375.4005 *: [email protected] <mailto:[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.
