Dns pointer record not updating
In the case of using the DHCP service to register client's DNS records, you need to add the DHCP server's computer account to the DNSUpdate Proxy Security group and set the appropriate settings on the DHCP server's properties.
In this case, the DNS client registers the host (A) resource record.
Also, the more experience you have, the more likely you are to make your DNS infrastructure complex, inviting the attention of Mr.
Murphy and other elements of chaotic cosmic calamity.
Finally, the DHCP server adds the DHCP_Computer_Name$ account together with Full Control permissions for the DNS record.
In this case, the DHCP server registers both the host (A) resource record and the pointer (PTR) resource record.
But even the most highly trained and savvy administrator can get in a hurry and make a mistake.I liken it to the days when automobiles had carburetors; a mechanic could fix most engine performance problems by fiddling with the choke—spritz a little WD-40 into the throttle body, charge and retire in the suburbs after a few years. Check the TCP/IP settings, run a few utilities to verify the zone records, charge 0 (correcting for inflation) and retire to Arizona.You’ll learn to identify the most common domain name system issues that cause problems for AD and Exchange and how to avoid them in the first place or isolate and resolve them if they occur in production.When the client dynamically updates its DNS information in this situation, the client's DNS time stamp is not updated until the Refresh interval takes effect.
This behavior controls and manages DNS and Active Directory replication (for AD Integrated Zones).If the TCP/IP settings for a member computer specify the IP address of a public DNS server—perhaps at an ISP or DNS vendor or the company’s public-facing name server—the TCP/IP resolver won’t find Service Locator (SRV) records that advertise domain controller services, LDAP, Kerberos and Global Catalog.