Windows 7 clients not updating dns dating a flake
So it looks like it will add new records but not update existing ones. I started wondering if this had something to do with installing the Pertino client on my DCs last Friday but am not sure. I'd really appreciate some advice if anyone has come across this before.I believe what you are wanting to do is simply tell all your DHCP clients to not register their own DNS records in AD.They request a DHCP address, and the DHCP server hands them one and updates DNS.If I check the security of the 'A' record created through the dynamic update, the record is owned by the account created for DNS dynamic update registration and populated in the DHCP server.
It has been about 45 minutes and DNS still shows the old ip address in the forward lookup zone.If you find it useful, here is a reference for GPOs which apply to the Windows DNS client.You will find this specific GPO at computer scope, under administrative templates and network, in DNS settings.Each DHCP server has the 'DNS dynamic updates registration credentials' setting populated with a user account which is a member of the 'Dns Update Proxy' group, and (although I've seen arguments for and against) I've added the servers themselves to the 'Dns Update Proxy' group.The DHCP servers are configured with the following settings ticked: 'Enable DNS dynamic updates according to the settings below' 'Always dynamically update DNS A and PTR records' 'Discard A and PTR records when a lease is deleted' Some PCs seem to work fine.
The dynamic update GPO controls this behaviour on a per-computer basis; when it is disabled, the per-connection "register this connection's address in DNS" option has no effect and dynamic registration does not occur, leaving the DHCP server to take care of it without interference.