Microsoft dns reverse lookup not updating

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!

This is because the client will not update itself due to the current record in DNS is beyond the lease period.

This happens even though DHCP registered the record.

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.

The following list illustrates a typical example of how a private DNS update leaks out to the global Internet. The DHCP client first sends a query to its local domain name server (LDNS) and asks for the authoritative server for the zone of its domain name (step 3).

Once the DHCP client receives a response (step 4), it sends the update to the indicated server (step 5).

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.

Leave a Reply