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.
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 ".
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?
As the DHCP servers in this environment are Linux based we would like the clients to update their PTR records themselves.
The reverse lookup zone exists, and I can add entries to it manually, but it doesn't automatically populate.so i manually tried to add it using "ipconfig /registerdns". I was also reading something on scavenging, but that will only fix the old entries that will deleting but I'm not sure about actually getting the correct entries to begin with. 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.There should be a flag set to "1" if the client is supposed to update both the A record and PTR record.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.