Bes last contact time not updating dating03 ru tf
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 mentioned this and got 'Yeah, we know.'So I decided to do some poking around.
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.
I also read that a service account should be configured to carry out the zone updates - which I have now done. The Dns Update Proxy group should contain the computer accounts of your DHCP servers, so DC1 and DC2 in your case.
In DNS console, find an outdated record, go to the Security tab and take a look at the owner of the record.Thanks for the response DCs changed accordingly, as well as DHCP settings. I see what you mean about the scavenging, however scavenging doesn't even seem to be taking place, as there are lots of outdated records.