Dns timestamp not updating

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.=============================================================== 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.

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.By default, on a computer that is running Windows XP/2003 or newer, the Default Registration Refresh Interval key value controls this (except Windows 2000, whichdoes not have this key but can be added), and is set by default to 1 day.This is true regardless of whether the computer is a client or a server, except domain controllers, which are every 60 minutes..================================================================= There are some misconceptions prompting fears that Scavenging will remove everything in your zone, includind servers.Please understand, the main thing that scavenging works on is the timestamp.