Dhcp lease not updating dns

Interestingly, I picked another one which I believe to be in-date, and the service account was present.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? I've picked two records that are out of date - the owner is SYSTEM.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 did a bit of reading and discovered that the group should have DNS computer accounts in, if the zones are configured to only be updated securely - which they were. I am forever getting incorrect / outdated lookups when connecting to machines.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.At the same time, I'm combing through AD and rationalizing group memberships.

I also noted a staggering amount of old, outdated DNS records.

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.

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.

Our DHCP was set to lease addresses for 1 day, for reasons which were never explained to me.

Please or register to post comments
If spammers comment on your content, only you can see and manage such comments Delete all
DHCP dynamic updates of DNS registrations are delayed or not processed. Additionally, a fountain pen icon appears next to the lease record in DHCP. 
12-Jan-2019 10:10
Reply
For some reason DHCP leases are not registered in either DNS. DHCP not updating DNS. Discard A and PTR when lease is deleted. I can try to change DNS to. 
12-Jan-2019 10:15
Reply
DHCP fails to update DNS. When DHCP tries to update/delete a manually created DNS record it is not allowed to. and lowering the DHCP lease. 
12-Jan-2019 10:21
Reply
This was not an issue when I first built the server so I'm not sure why it is now. I have dynamic updates enabled inside DHCP with the option set. 
12-Jan-2019 10:24
Reply
DHCP is not updating the DNS. some believe that the DNS servers or other DCs not running DHCP should. to be equal or greater than the DHCP Lease. 
12-Jan-2019 10:28
Reply
Ryadical wrote I believe it is up to the DHCP clients to renew the lease before it expires, not the DHCP server. Is it possible you have 2 separate DHCP servers on. 
12-Jan-2019 10:31
Reply
Re DHCP not updating DNS? Normally it is the client which updates DNS -- unless it is old enough that it will not, in which case the DHCP server will do so 
12-Jan-2019 10:34
Reply
As far as my understanding goes which is clearly not far enough, DHCP should update DNS as soon as it itself updates. Our DHCP was set to lease addresses for 1 day. 
12-Jan-2019 10:38
Reply

Dhcp lease not updating dns introduction

Dhcp lease not updating dns