Ipconfig registerdns not updating dating encounters
The DNS Client service and the DNS Server service support the use of dynamic updates, as described in Request for Comments (RFC) 2136, "Dynamic Updates in the Domain Name System." The DNS Server service allows dynamic update to be enabled or disabled on a per-zone basis at each server that is configured to load either a standard primary or directory-integrated zone.
By default, the DNS Client service dynamically updates host (A) resource records in DNS when the service is configured for TCP/IP.
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.
Additional considerations: When one of the previous events triggers a dynamic update, the DNS Client service (not the DHCP Client service) sends updates.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.For further details on cookies, please see our cookies policy.Dynamic DNS is one of the most touted features of Windows 2000 (Win2K).
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.