Dns is not updating records
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.Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.The default Time To Live (TTL) value used for dynamic registrations is 20 minutes.You can use the following registry subkey to modify the TTL value: HKEY_LOCAL_MACHINE\SYSTEM\Current Control Set\Services\Tcpip\Parameters\Default Registration TTL . Scavenging Refresh and No Refresh settings must be equal to or less than the lease period.This happens even though DHCP registered the record.
If there is a problem with PTRs getting updated even after configuring credentials, please see this article: DHCP server processes expired PTR resource records in Windows Server 2003 . The use of Name Protection in the Windows Server® 2008 R2 operating system prevents name squatting by non-Windows-based computers.
With the default settings, a duplicate A record gets registered by DHCP with the client’s new IP.
This is because the client will not update itself due to the current record in DNS is beyond the lease period.
This is true regardless of whether the computer is a client or a server, except domain controllers, which are every 60 minutes.
You can use the following registry subkey to modify the update interval: HKEY_LOCAL_MACHINE\SYSTEM\Current Control Set\Services\Tcpip\Parameters\Default Registration Refresh Interval Data type: REG_DWORD Range: 0x0 – 0x FFFFFFFF seconds Default value: 0x15180 (86,400 seconds = 24 hours) for Windows 2000 Professional Default value: 0x E10 (3,600 seconds = 1 hour) for Windows 2000 Server and Windows Advanced Server Scope: Affects all adaptors This specifies the time interval between DNS update registration updates.