To resolve this issue, create a reverse lookup zone for the subnet that hosts the client computer in DNS.Configure it to allow dynamic updates by using the DNS tab of the Scope Properties of DHCP Manager and setting one or both of the following: Dynamically update DNS A and PTR records for DHCP clients that do not request updates.
If you want more information you may find the following useful:
When either type of client (static or DHCP client) initiates an A record update with its authoritative DNS server, it will first start by performing an SOA query for the FQDN of the client in question: The client then receives a response from the authoritative DNS server containing information about the server that is to process the dynamic update.
From there, the client continues communicating with the primary DNS server that accepted the A record update.
If there are missing entries, you likely have your DHCP missing one of two settings: This is required if you have DHCP installed on a Domain Controller.
It is an issue on Server 2000, 2003, 2008, 2008R2, Server 2012, Server 2012 R2 and will likely be an issue in the newer builds.