Once you have these credentials set, restart your DHCP server service.
Before we delve any further, its time to check your DNS setup, ensure that DNSAdmin’s have full control over the entire DNS infrastructure, by going to properties and security tab on each DNS server.
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.
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.
By default, the ACL gives Create permission to all members of the Authenticated User group, the group of all authenticated computers and users in an Active Directory forest.
Most of you won’t be running Windows 2003 anymore, but if you are, this link may be of interest: DHCP setup primarily is the place to start with this, it is often overlooked that there needs to be a username entered into DHCP to allow for these Dynamic Updates to take place.This then causes duplicate names on the network and all hell breaks loose. I have found some notes about similar issues and made the suggested changes, but the problem has not gone away.riginally posted this in 4/2006, and updated throughout the years, but I still get questions from time to time asking why updates are not working, especially PTR.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.Also ensure that reverse lookups are in place, and that permissions are correct on these too.