Well, this did not turn out to be the fix. Interestingly, in the DHCP audit logs, server 2 doesn't even appear to be trying to update PTR records. There are no events at all of type 30, 31 or 32. (DNS update request, DNS update failed and DNS update succesful.)
Server 1 has lots of 30s and 32s. Perhaps a restart of the server/service is in order, though the problematic server was just restarted a little over a week ago. On Jun 30, 2016 10:59 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 >
