If the client has moved to a new IP subnet, the the A record is registered using the old IP address.
To resolve this issue, create a reverse lookup zone for the subnet that hosts the client computer in DNS.
If you have the program already installed skip to the example section below and execute the commands shown (don’t forget to change the domain name according to your needs).
The host (A) records for one or more clients contain incorrect IP address, preventing name resolution, when a Windows Server 2003 DHCP (Dynamic Host Configuration Protocol) server is configured to update A records and PTR records in DNS.
This behavior can occur if there is no reverse lookup zone for the IP subnet, or if the reverse lookup zone is not configured to allow dynamic updates.
Since there is no dynamic reverse lookup zone, the registration fails, but the DHCP database cleanup, performed every 60 minutes, attempts the registrations that previously failed.
Computer networks use the Domain Name System (DNS) to determine the IP address associated with a domain name. Reverse DNS Troubleshooting The reverse DNS database of the Internet works with a hierarchical tree of servers, just like forward DNS.
This process is also known as forward DNS resolution. It is rooted in the Address and Routing Parameter Area (arpa) top-level domain of the Internet.
It is very important to note that this feature allows a server with a given IP address to update only it’s own PTR record and also that the updates must be sent over TCP.Usually the update of PTR records is a manual process where the user of a given IP address must send a request to the organization that manages the IP network, to add/remove/modify the PTR record for a given address.What we outline in this post is how you can create and update PTR records for yourself, without having to revert to us.This new functionality provides greater flexibility in setting up your applications in our cloud.We now accept dynamic updates of PTR records within our zones.