Some customers have reported issues with Microsoft Dynamic Updates after installing virtual appliances (VAs) in their environment or installing the Umbrella Roaming Client on some machines.The most commonly reported symptom is that clients cannot resolve A or PTR records for other client machines while using the VAs or the Roaming Client for DNS resolution.Hi Everyone, I have a 2003 AD DC running DNS services.I also have a 2008R2 as an additional DC also running DNS. When a computer or object is added to DNS, it only goes into Forward Lookup Zone, and does not create an associated PTR record. The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.
If you choose to participate, the online survey will be presented to you when you leave the Technet Web site. 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.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.