Also, it will allevaite another issue – If DHCP is on a DC, it will not overwrite the original host record for a machine getting a new lease with an IP previoulsy belonging to another host. Quoted from the following link: “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.
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.
“ 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
.================================================================= There are some misconceptions prompting fears that Scavenging will remove everything in your zone, includind servers.
To configure DHCP Option 081, you must look at the DHCP server properties, under the DNS Tab in DHCP properties. If you have Windows 2008 R2 or Windows 2012 R2, in addition to configuring the DNS tab to force registration, you still must configure credentials and add the server to the Dns Update Proxy group.If I run ipconfig /registerdns from any of the clients. There is no error any of the event logs (server or local) and the static entry in forward never updates. I noticed on each record that there is an account called Self with special permissions, yet when you drill down there are none set.If I restart the machine, it still does not update. I hate to have to delete all this suff in forward, because I am not sure which items actually need to be static.I know it's not quite right because if I do $ORIGIN . Running DNS on two 2008 R2 Servers setup as AD integrated for both Forward and all Reverse zones. In DNS the following was set: -Type AD Integrated -Replication All domain controllers in this domain -Dynamic Updates None (why that was like that who knows) -Scavenging is not in use yet I changed Dynamic updating to Secure and Non Secure since I was not sure how it would affect all the non windows servers currently in there.This means that any authenticated user or computer can create a new object in the zone.Also by default, the creator owns the new object and is given full control of it.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.The use of Name Protection in the Windows Server® 2008 R2 operating system prevents name squatting by non-Windows-based computers.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.