Dhcp not updating dns server 2016

So in your case, DHCP update would renew it's lease every 3.5 days, triggering a DNS refresh.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?Still having problems with outdated records :-/I increased the lease time from 1 day to 7 days as mentioned in the OP, but we're still getting an issue when the clients receive a new IP, they are not updating DNS with the new record and removing the old.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.

At the same time, I'm combing through AD and rationalizing group memberships.We've been having an issue for a while now where clients are not updating their DNS records, despite automatic updates in DHCP being turned on.The first I hear of it usually is people moaning they can't get on Youtube, since the filter doesn't know what the computer is and thus who is logged in.I also read that a service account should be configured to carry out the zone updates - which I have now done. Our domain's zone is configured as an AD-Integrated zone with replication to all DNS servers in the forest.Dynamic updates are set to Secure Only, and Aging is 2 hours no-refresh, 6 hours refresh intervals.

Leave a Reply