Dhcp not updating lease
I did a bit of reading and discovered that the group should have DNS computer accounts in, if the zones are configured to only be updated securely - which they were. I am forever getting incorrect / outdated lookups when connecting to machines.
I also read that a service account should be configured to carry out the zone updates - which I have now done. Our domain's zone is configured as an AD-Integrated zone with replication to all DNS servers in the forest.
To facilitate this interaction, servers running Windows Server® 2008 and DHCP and clients running DHCP can register with DNS, allowing cooperation between the two.
When DHCP changes IP address information, corresponding DNS updates synchronize name-to-address associations for the computer.
DNS servers provide domain name resolution for network resources.
They associate the TCP/IP address assigned by DHCP to a client with its fully qualified domain name (FQDN).
This association, or mapping, of an IP address to a domain name requires that a change in either the address or the name necessitates an update of the information in DNS.
The DHCP protocol does not automatically update DNS in the event that the DHCP server changes the IP address of a client.
I mentioned this and got 'Yeah, we know.'So I decided to do some poking around.The DNS Client service performs this function for all network connections on the client, including any that are not configured to use DHCP.When a qualified DNS client (such as a computer running Windows XP Professional or Windows Vista®) issues an update, DHCP servers running Windows Server 2008 process the update to determine in which of three ways the server will initiate updates on behalf of the client: The ability to register both A and PTR resource records enables a DHCP server to act as a proxy for clients running other operating systems, such as Microsoft Windows Millennium Edition, or Windows 98, for the purpose of DNS dynamic update registration.This happens even though DHCP registered the record.This is because DHCP doesn’t own the record, the client does, even though DHCP registered it. If you have Windows 2008 R2, in addition to configuring the DNS tab to force registration, you still must configure credentials and add the server to the Dns Update Proxy group.