Hello
I recently posted this issue in the Windows Server General Forum, and they suggested I try in this forum instead.
When we re-image a Windows 7 workstation using Windows Imaging, and move it to a new subnet the new PTR record gets created but the A record does not. Other PCs that haven't been recently imaged can be moved to different subnets, and their PTR and A records update right away. We have a group policy setting in place to prevent the clients from registering their own DNS records, because we want DHCP to handle that. (We started doing this because we were having problems with XP laptops registering their wireless and vpn addresses instead of their LAN addresses). There are no errors related to this issue in the event logs on the clients or servers, and a WireShark capture showed no errors. Our DHCP logs show that the DNS registration is successful. Removing/rejoining the PC from the domain does not help. Our DHCP servers are all members of the DNSUpdateProxy group, so record ownership should not be a problem. I verified that the security on the zones is set correctly. Our DNS is AD integrated and allows for secure dynamic updates only. I have also verfied that the new A record is not appearing on any of our DNS servers so it doesn't seem to be a replication problem. The only way the new A record will appear is if we manually delete the old record, and even that doesn't always work.
To recap our environment: We have AD integrated DNS running on 2008 R2 servers, and our DHCP servers are a mix of 2003 and 2008 R2 DCs. Both our DNS and DHCP settings are correct to allow dynamic updates, and all of the DHCP servers are members of the DNSUpdateProxy group, and we have a specifc account configured for DNS registrations. IPv6 is disabled on the client NICs, and a group policy setting prevents the clients from doing their own DNS registrations. Any help would be appreciated.
Thank you,
Michelle
Michelle Garrah