And make sure the DNS dynamic update credentials are correct and appropriate permissions are applied for this to work As I said in the question, configuring the DHCP server is not an option. It won't register DNS records for its clients, period.They should be able to handle it, since all of them are domain members.When a DHCP server is added to the Dns Update Proxy group, its records aren't secured, meaning that other DHCP servers can update the records.In additon, hosts can change the records and then become the owner of the record.in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record. sends option 81 and its fully qualified domain name to the DHCP server and requests the DHCP server to register a pointer resource record (PTR RR) on its behalf.The dynamic update client registers an address resource record (A RR). the DHCP server can be configured to instruct the client to allow the server to register both records with the DNS. Keep in mind with AD integrated zones the SOA rotates among the DCs because of the multimaster feature. For non-joined machines, it must be manually configured or scripted. If using DHCP Option 015 (Connection Specific Suffix), it must match the zone name and have "Use This Connection’s DNS Suffix in DNS Registration" along with "Register This Connection’s Addresses in DNS" checked in the NIC’s IPv4, Advanced, DNS tab. If the SOA is not available or resolvable, it won’t register.
If disabled, it will cause other problems: The Cable Guy – Support for IPv6 in Windows Server 2008 R2 and Windows 7, by Joseph Davies, Microsoft, Inc.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.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.Q: Does setting DNS dynamic update credentials on DHCP achieve the same result as adding a DHCP server to the Dns Update Proxy group?