With the help of DNS integration with the DHCP, you can simplify this task and can remarkably reduce the administrative overhead.
Just like other DHCP administration configurations, even this one requires that you should use the Enterprise Admin or Domain Admin account credentials to make the changes.
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. If DHCP is on a Windows 2008 R2 DC, to protect the DC when using the Dns Update Proxy group, you must secure the group by running: dnscmd /config /Open Acl On Proxy Updates 0 Using “DHCP Name Protection.” will register A and PTR record on behalf of a client, and will prevent a workstation (non-Windows) Name Squatting, meaning using a name that another machine (non-Windows or Windows) client that DHCP already registered , from registering it’s name.
To configure DHCP Option 081, you must look at the DHCP server properties, under the DNS Tab in DHCP properties. After configuring the above provedure, the credentials and Dns Update Proxy group configuratuion will not update current or delete duplicate records. DHCP will give that duplicate named client an IP, but it will not register it into DNS.
What this means in practice is the following: This means the DHCP server computer account will own certain records in DNS, such as the PTR records and even some A records for older hosts.
(However, it's unlikely that you would have many NT 4.0 hosts in your environment.) This can cause the following two problems: For this reason, DHCP servers could be added to a group called Dns Update Proxy.
I can do a reverse lookup on the IP and that works but not name to IP. In case your DHCP server is a standalone Windows Server 2012 server, you can use the local administrator account credentials to log on while making the above configurations in the DHCP server.Here is how you can enable the DNS integration with the Windows Server 2012 DHCP server: Once done, click OK to save the changes that you have made.Q: Does setting DNS dynamic update credentials on DHCP achieve the same result as adding a DHCP server to the Dns Update Proxy group?A: The short answer is no; however, it's important to step back and understand how DNS interacts with DHCP regarding dynamic updates, then look at what each of the two actions mentioned in the title actually does—namely, setting DNS dynamic update credentials on DHCP and adding a DHCP server to the Dns Update Proxy group.