Static records have a timestamp of 0 indicating do not scavenge.
The record appeared in the reverse DNS zone as expected. I do think you can use the GPO if you want to fine-tune the registration behavior as it contains 3 options. I haven’t found a way to do this by GPO, I might have missed it though.
I thought GPO preferences would be the easiest way, but this setting is located below HKEY_LOCAL_MACHINE\SYSTEM\Current Control Set\services\Tcpip\Parameters\Interfaces\\Register Adapter Name and the GUID is different for each system… The following command can be executed in order the check the required option: netsh interface ipv4 set dnsservers name="Local Area Connection" source=dhcp register=both In our environment we deploy all workstations using SCCM so the above is definitely a reasonable solution.
Windows clients will attempt to dynamically update DNS every 24 hours. When a record is first created by a client that has no existing record it is considered an “Update” and the timestamp is set.
If the client has an existing host record and changes the IP of the host record this is also considered an “Update” and the timestamp is set.
Because deletion is involved there are quite a few safety valves built into scavenging that take a long time to pop. To see the scavenging setting on a record hit View | Advanced in the DNS MMC then bring up properties on a record.