Dhcp clients not updating dns records
Hopefully in the next couple days it will begin to populate Do you have name protection enabled?
I'm working through an issue currently where certain records will not update, to the point where had I not disabled scavenging I would have lost a bunch of printers etc.
Additionally if you have a DHCP 2012 failover environment and credentials are not configured for those devices which do not have their own account in AD, each server will register those devices with it's own name as the owner of record so should the device renew it's lease on the alternate server that server will not have permission to update the record - hence I can't see a way around using credentials on both sides (and consequently scripting the setting of permission on the records already owned by the server)no, it seems the issue was that I had it set to secure updates only and for some reason none of these machines wanted to do it that way.
Microsoft themselves posted that it won't work that way you have to do secure and nonsecure so I did and it began working.
Lately, I was asked for advice about why DNS records in Active Directory were not updated with the current IP-address during the reinstallation of PC’s.
We could not reproduce the problem with this approach.
Also by default, the creator owns the new object and is given full control of it.
Tomorrow they want me to wipe out the entire DNS zone and start over from scratch :(I wonder if our problems are the same and due to some bug in 2012 R2 DNS and/or DHCP.
The ACL of an automatically set up DNS record always includes an entry like this: In the case of our customer however, the following happened: After the object is deleted, the SID cannot be dissolved anymore (picture 2).
When the object is set up anew, the “old” SID remains in the ACL of the DNS records and the new one is not included (picture 3). Computer objects will not be only reset and not deleted anymore.
Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.
In this mode, the DHCP server always performs updates of the client’s FQDN, leased IP address information, and both its host (A) and pointer (PTR) resource records, regardless of whether the client has requested to perform its own updates.” “With secure dynamic update, only the computers and users you specify in an ACL can create or modify dns Node objects within the zone.