A quick Facebook read the first line and click “Like,” seems to be the norm. And yea, I had to state Windows 2000 and newer, because this stuff doesn’t apply to older Windows versions.
John, in the image above of the Ipv4 properties you say that the settings are the default settings for DHCP server to register the records on behalf of the client.
I am pretty sure that the option:"Dynamically update DNS records only if requested b the DHCP client" is not the setting you need to set.
=============================================================== When a client shuts down, and later returns past the lease time, it may get a different IP address.
With the default settings, a duplicate A record gets registered by DHCP with the client’s new IP.
(The first update to a record that isn't a member of Dns Update Proxy becomes the owner.) This is very dangerous if a DHCP server is also a domain controller because it means that all the Active Directory records for that domain controller are written with no security and can therefore be overwritten by other hosts (although an additional setting, Open ACLOn Proxy Updates, helps prevent this by stopping records from being overwritten by any server that isn't a member of Dns Update Proxy group when set to a value of 0).
There's a better solution, however, which also solves the issue of DHCP running on a domain controller.This is because the client will not update itself due to the current record in DNS is beyond the lease period.This happens even though DHCP registered the record.Those records have an ACL on them to stop registered records from being hijacked by other hosts.When DHCP is used to allocate IP addresses, the default configuration is shown below—which tells the DHCP server to register records in DNS on behalf of clients only if requested to do so by the client or if the client is unable to dynamically register (e.g., Windows NT 4.0).This means all DNS records registered by the DHCP servers would be owned by the specified account that is common to all DHCP servers.