Even if that is not what is causing the problem, the way I understand it it's bad security to not designate an account here as you point out when running DHCP on a DC.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sean Martin Sent: Friday, July 1, 2016 11:15 AM To: [email protected] Subject: Re: [NTSysADM] DHCP server not updating PTR records I seem to recall that the DHCP advanced properties need to be configured with an account to register records in DNS, specifically when DHCP is installed on a Domain Controller. - Sean > On Jun 30, 2016, at 6:51 PM, Richard Stovall <[email protected]> wrote: > > Some folks I'm working with have 2 DCs that are also DHCP servers. Each server hands out part of the scope. Long story short, clients who receive ips from DC1/DHCP1 have PTR records. Clients who receive ips from DC2/DHCP2 do not. All clients are Win7. If, on a client that has an ip received from server 2, you tick the box in advanced IPV4 properties to "Use this connection's DNS suffix in DNS registration", then run ipconfig /registerdns, a PTR record is created. No clients that have received ips from server 1 have this option checked, but they all have PTR records. > > I've checked the settings on the DHCP servers and everything I can find for DNS registration looks the same. > > Any thoughts? I'm betting it's pretty simple and we're just missing something easy. > > FWIW, the DCs and the domain/forest are Server 2008. > > Thanks, > RS
