I've stumbled upon a strange behaviour with Windows machines, which seems to be fairly consistent between all Windows versions from Vista/2008 to 8.1/2012 R2; it doesn't happen instead when using Windows XP or Windows Server 2003.The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then A friend not on SF said: "That's normal, PTR is only updated by DHCP in Win2K ".A flag of "0" means the client updates the A record and requests that the server update the PTR record on its behalf. Also in the DHCP scope make sure == Click the DNS tab, click Properties, and then click to select the Dynamically update DNS A and PTR records only if requested by the DHCP clients check box == is set.This would mean when the default flag of "0" comes in the server will then try to register the PTR record with the DNS server(s) it is configured to update.And make sure the DNS dynamic update credentials are correct and appropriate permissions are applied for this to work As I said in the question, configuring the DHCP server is not an option. It won't register DNS records for its clients, period.They should be able to handle it, since all of them are domain members.
By default, all computers register records based on their fully qualified domain name (FQDN).That configuration should be just fine - it just means that you shouldn't be worrying about a system failing to update until the timestamp on its record is over 8 days old.In other words, don't stress about those timestamps; only stress about the refresh failing if scavenging actually kills a record for a system that's running.This is designed so that if a change to the IP address information occurs, corresponding updates in DNS are performed to synchronize name-to-address mappings for the computer.The DNS Client service performs this function for all network connections on the system, including connections that are not configured to use DHCP.in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record. sends option 81 and its fully qualified domain name to the DHCP server and requests the DHCP server to register a pointer resource record (PTR RR) on its behalf.The dynamic update client registers an address resource record (A RR). the DHCP server can be configured to instruct the client to allow the server to register both records with the DNS.Configured my brand new laptop with same computer name (PC1) and joined to domain 3.Got a DHCP address from the server Now my issue is as follow.If I log on to the server and reboot, or run ipconfig /registerdns, it will update the timestamp just fine.The computer account has full control in the security settings of its respective record. I tried configuring it to update DNS, which is working for workstations that have DHCP addresses, but I do not think tha these updates work for servers that have static IPs. The objects for the DNS records are stored in either the normal directory partition (if the zone's in 2000-compatible replication mode), the Domain DNSZones partition (if the zone is set to replicate to all DNS servers in the domain), or the Forest DNSZones partition (if the zone is set to replicate to all DNS servers in the forest) -- you probably need to have ADSIEdit connect to the DNS partition.Domain Name System (DNS) client computers can use dynamic update to register and dynamically update their resource records with a DNS server whenever changes occur.This reduces the need for manual administration of zone records, especially for clients that frequently move or change locations and use Dynamic Host Configuration Protocol (DHCP) to obtain an IP address.But since the no-refresh interval is set where it is, the lack of updates should be expected - see my answer.