Bes last contact time not updating
Our DHCP was set to lease addresses for 1 day, for reasons which were never explained to me.
I set this back to 7 days, in an attempt to give DNS a chance to 'catch up' before the addresses potentially changed again, but we're still getting incorrect DNS entries. Our settings are now an amalgam of what went before (which didn't work) and what I've gleaned from MS documentation.
DC1 has DNS servers setup as itself and DC2 (primary and secondary)DC2 has DNS servers setup as DC1 and itself (primary and secondary) Do you have an account set up as proxy for the DHCP server to register users?
The DHCP service needs some valid way to tell the DNS server to update the records.
Scavenging appeared to be configured, but not actually working.
I mentioned this and got 'Yeah, we know.'So I decided to do some poking around.
So in your case, DHCP update would renew it's lease every 3.5 days, triggering a DNS refresh.Discard A and PTR records when lease is deleted Dynamically update for DHCP clients that do not request updates Our domain's zone is configured as an AD-Integrated zone with replication to all DNS servers in the forest.As far as my understanding goes (which is clearly not far enough), DHCP should update DNS as soon as it itself updates.I'm wondering if I remove all records which don't have the service account present, will these then be regenerated correctly, and updated properly going forward? You can try deleting some of the outdated records, and then either let DHCP refresh the records or do an ipconfig /registerdns from the client. You still should be looking at why scavenging is not running in your environment.All records with a timestamp of today (specifically the two machines we just rebuilt) don't have the service account in the permissions - they do have their own computer account, and the owner is SYSTEM.