Server 2016 r2 dns not updating
.================================================================= There are some misconceptions prompting fears that Scavenging will remove everything in your zone, includind servers.
Secure Dynamic Update Updating DNS Resource Recordshttps://technet.microsoft.com/en-us/library/ff631099(v=ws.10)How to configure DNS dynamic updates in Windows Server 2003. Using DNS servers with DHCP (Contains information on the Dns Update Proxy group and its usage) (WS.10)=============================================================== The credentials only need to be a plain-Jane, non-administrator, user account. Make sure ALL other non-DHCP servers are NOT in the Dns Update Proxy group.Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.In this mode, the DHCP server always performs updates of the client’s FQDN, leased IP address information, and both its host (A) and pointer (PTR) resource records, regardless of whether the client has requested to perform its own updates.” “With secure dynamic update, only the computers and users you specify in an ACL can create or modify dns Node objects within the zone.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.