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.
After some digging I found that I needed to provide the DHCP server with credentials to do so, and finally got the dynamic, secure updates working.
To make sure DNS was always accurate, I told DHCP to update the A and PRT records even if the client does not ask for that.
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.
Ace Fekay, MCT, MVP, MCITP EA, Exchange 2010 Enterprise Administrator, MCTS Windows 2008, Exchange 2010 & Exchange 2007, MCSE 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP: Directory Services Active Directory, Exchange and Windows Infrastructure Engineer Compiled 4/2006, recompiled 7/2009, & 1/4/201011/30/2011 – added DHCP credentials and DHCP/DNS tab properties screenshots.3/10/2012 – Added enabling DNS scavenging screenshots.8/22/2012 – Verified with a Microsoft enginner, we need to use the Dns Update Proxy group and configure credentials to work, not one or the other. Also fixed missing screenshots8/3/2012 – Additional info about DHCP Name Protection and that it requires Credentials, Dns Update Proxy, but more so to secure the Dns Update Proxy group .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.Dont have a router there, only a 3750 tied in via a fiber link.I have been looking at the Cisco docs for getting this to work but nothing yet.