Dhcp clients not updating dns records
Technet says something about setting option 81 but I don't even have an option 81. I assume this is set, but on the client network adapter under your ipv4 or 6 properties and then advanced, under the dns tab you have the option "Register this connections address in DNS" checked correct? We are experiencing the same thing in our environment. It seems to occur once every couple of days and only on our 2012 R2 DC not on the other 2003 DCs in the forest.
On the server that has a 'missing' DNS record - if I do ipconfig /registerdns - then it is put back in. Obviously that only band-aids that one server and doesn't fix the root problem.
(Why this was the case, you can read below.) I asked the customer to describe the imaging process to me a little more detailed..
The customer checks, if a computer object with the PC’s name already exists, before joining the PC into the domain.
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.Let me know if you want the script(s) I seems to go back to about October of 2014, it never effected anything because we're such a small network and our most network intense software doesn't use resolution you have to actually enter an IP address for it.It seems to be up and running now but I can certainly let you know on Monday if it's stopped again Check out this article: is what I did: add dhcp servers to Dns Proxy Update group in AD,run dnscmd /config /Open Acl On Proxy Updates 0 on all DHCP servers, Enable Name protection, Use DHCP service accounts, Convert DCHP leases on workstations to staticit appeared to be using the proper credentials but I reentered the password anyway, at least one record has updated but I'm still not seeing a bunch of records that should be coming through shortly.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.