Windows reverse dns not updating
Ideally you set this to a low value - say 60 seconds, several hours (a length of time greater than the current ttl value) before making a change, then put the TTL back to a higher value (to avoid unnecessary taxing of the DNS system) after the change.This is what people are referring to when they talk about "DNS propagation", only it isn't propagation at all, it is just cache values timing out.I do not understand what I need to check, as I have never had this problem. We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions.Updating the PTR records means a client registers his name and IP in the reverse lookup zone.As we noticed that only Windows 7 workstations with a static IP were being registered we started troubleshooting.DNS servers provide domain name resolution for network resources.They associate the TCP/IP address assigned by DHCP to a client with its fully qualified domain name (FQDN).
I pinged it using online tracerouting tools and it always shows the new IP.
To facilitate this interaction, servers running Windows Server® 2008 and DHCP and clients running DHCP can register with DNS, allowing cooperation between the two.
When DHCP changes IP address information, corresponding DNS updates synchronize name-to-address associations for the computer.
This association, or mapping, of an IP address to a domain name requires that a change in either the address or the name necessitates an update of the information in DNS.
The DHCP protocol does not automatically update DNS in the event that the DHCP server changes the IP address of a client.