Server 2016 dns timestamp not updating

I have opened up a support case with Microsoft on August 17th. So far they've enabled all auditing and logging functions and the problem happened again - it was not shown at all what deleted the DNS record even with maximum logging turned on.

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.

For example, some folks believe that the DNS servers or other DCs not be running DHCP should be in it. Make sure that NO user accounts are in that group, either.

(I hope that’s crystal clear – you would be surprised on the number of responses I get asking if the DHCP credentials should be in this group.) You Just to be crystal clear, this means that if the lease is an 8 day lease, than NOREFRESH should be 4 (four) and REFRESH should be 4 (four) so when you add them together, they are not greater than the lease length.

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.

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.

A quick Facebook read the first line and click “Like,” seems to be the norm. And yea, I had to state Windows 2000 and newer, because this stuff doesn’t apply to older Windows versions.

Well, I will also offer the nitty gritty below the summary for those who want to read. But DHCP will register its PTR (reverse entry) record.

By default, the ACL gives Create permission to all members of the Authenticated User group, the group of all authenticated computers and users in an Active Directory forest.

This means that any authenticated user or computer can create a new object in the zone.

Leave a Reply