Ms dhcp not updating dns

17-Nov-2017 01:07

Secure Dynamic Update Updating DNS Resource Records to configure DNS dynamic updates in Windows Server 2003. Using DNS servers with DHCP (Contains information on the Dns Update Proxy group and its usage) (WS.10)=============================================================== The credentials only need to be a plain-Jane, non-administrator, user account. Make sure ALL other non-DHCP servers are NOT in the Dns Update Proxy group.For example, some folks believe that the DNS servers or other DCs not be running DHCP should be in it. Make sure that NO user accounts are in that group, either.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.

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

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.

To configure DHCP Option 081, you must look at the DHCP server properties, under the DNS Tab in DHCP properties. If you have Windows 2008 R2 or Windows 2012 R2, in addition to configuring the DNS tab to force registration, you still must configure credentials and add the server to the Dns Update Proxy group.

As long as the Internal Domains are correctly populated, then any SOA queries for any internal-facing domains will be sent to the local DNS server.

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.

Statically-set clients (static clients) that perform dynamic updates will send updates for both its A record (forward lookup record) and its PTR record (reverse lookup record) to the authoritative DNS server.