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.
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.
Name squatting does not present a problem on a homogeneous Windows network where Active Directory® Domain Services (AD DS) can be used to reserve a name for a single user or computer.” DHCP Step-by-Step Guide: Demonstrate DHCP Name Protection“Name squatting occurs when a non-Windows-based computer registers in Domain Name System (DNS) with a name that is already registered to a computer running a Windows® operating system.
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.
For example, using the default DHCP lease period of 8 days with a 7day scavenge setting, is perfect.
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.
The default Time To Live (TTL) value used for dynamic registrations is 20 minutes.
This is because DHCP doesn’t own the record, the client does, even though DHCP registered it.
The way to get around this is you can configure DHCP’s Option 081 to update the record for all client, no matter if the client asks or not.
This applies to Windows 2000 Professional and all newer operating systems.