Ptr records not updating
so we are not able to push domain policies to there machines.
We are using non-Microsoft DHCP server with Microsoft DNS.
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.
Well, I thought it’s time for an update and to just offer a summary in the beginning, because in this day and age, no one wants to read!
Another option is to do PTR synchronization directly from clients.
Despite it being a DHCP Option, it’s not found in a DHCP server, scope or class option. After configuring the above provedure, the credentials and Dns Update Proxy group configuratuion will not update current or delete duplicate records. 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.
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.
This means that any authenticated user or computer can create a new object in the zone.
This is because DHCP doesn’t own the record, the client does, even though DHCP registered it.
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.
Search for ptr records not updating:
This is because the client will not update itself due to the current record in DNS is beyond the lease period.