=============================================================== 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 use of Name Protection in the Windows Server® 2008 R2 operating system prevents name squatting by non-Windows-based computers.“ DHCP Name Protection The DNSupdateproxy group must be secured if Name Protection is enabled on any IPv4 scope Credentials for DNS update should be configured if secure dynamic DNS update is enabled and the domain controller is on the same host as the DHCP server
Well, I thought it’s time for an update and to just offer a summary in the beginning, because in this day and age, no one wants to read!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.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.Well, I will also offer the nitty gritty below the summary for those who want to read. But DHCP will register its PTR (reverse entry) record.The recommended update style is “interim”, which is described in this recipe.If you also want the DHCP server to handle all dynamic updates, add these statements: statements telling the DHCP server the domain names of the zones it will update, and for each of these, the address of the name server to send updates to and the TSIG key to sign those updates with. If there is no timestamp, such as a manually created, static record, it will not get scavenged.Also, if all servers, including DCs, are automatically updating their own record, then there is no fear of losing their records, because for one, their records (timestamps) are current, therefore scavenging won’t touch them, and two, Windows Servers by default will update their records every 24 hours, with the exception of domain controllers at every 60 minutes.This applies to Windows 2000 Professional and all newer operating systems.For domain controllers, due to the importance of keeping up to date and accurate SRV and other records, the Netlogon service will attempt to update these records every 60 minutes.