At the same time, I'm combing through AD and rationalizing group memberships.

dhcp not updating a records in dns-48dhcp not updating a records in dns-3dhcp not updating a records in dns-47

A DHCP lease should renew itself halfway through the lease.

So in your case, DHCP update would renew it's lease every 3.5 days, triggering a DNS refresh.

DHCP is set as follows: Enable DNS dynamic updates - always dynamically update DNS A and PTR records.

Discard A and PTR records when lease is deleted Dynamically update for DHCP clients that do not request updates As far as my understanding goes (which is clearly not far enough), DHCP should update DNS as soon as it itself updates.

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.

However in your aging settings, the record is able to be marked for scavenging after 8 hours (no-refresh refresh intervals). Under Server Manager, have you tried running the Best Practices Analyzer against DNS and DHCP, to see if that gleams any info?

So are the records being scavenged before DHCP has an opportunity to refresh them? Run a dcdiag on your DC as an overall health check?

Is it the computer account of the client (PC123$), the DHCP server, or the service account you configured?

Because secure updates are enabled, only the owner of the record can update it.

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.