Ipconfig registerdns not updating validating version wow
By default, the DNS Client service dynamically updates host (A) resource records in DNS when the service is configured for TCP/IP.By default, computers that are statically configured for TCP/IP attempt to dynamically register host (A) resource records and pointer (PTR) resource records for IP addresses that are configured and used by their installed network connections.That doesn't exactly seem to be the case from your experience, but might be close.... Massimo, are you able to pull a wireshark trace and check the DHCPREQUEST Packet?There should be a flag set to "1" if the client is supposed to update both the A record and PTR record.But since the no-refresh interval is set where it is, the lack of updates should be expected - see my answer.Having a "No-refresh" interval configured to 7 days is intentionally blocking the periodic (24 hour) refresh by the client systems, until their record is at least 7 days old. The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.
To check, right-click your DHCP scope and go to properties.If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).I have 2 Server 2008 R2 domain controllers with a AD integrated DNS zone for the domain. I enabled scavenging a week ago and now that I am seeing old stale records go away, I am also noticing that about 80% of my DNS record timestamps arent updating properly.From what I understand, the servers should update their own DNS records every 24 hours, but like I said, I have many that are over 24 hours old.