I followed this thread but this is a new issue:
https://social.technet.microsoft.com/Forums/office/en-US/37b8b6b3-6cb1-496c-8492-09ded13bab18/dns-problem?forum=winserverNIS
I'm not seeing this on Windows 7 client machines. We have Win 7 or Win 10 deployed. Mostly 7 at this point, but almost all laptops are 10 (thanks for including Bitlocker in Win 10 Pro!).
On the Win 10 machines I get Event ID 8018 from DNS Client Events in the SYSTEM event log that is repeated for each network interface on the machine (2 if there is a wired and wireless for example). Basically says
The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings:
Adapter name: {GUID}
Host name: computername
Primary Domain Suffix: domainname.com
DNS Server list:
10.1.1.1, 10.1.1.2, 10.30.1.1
Sent update to server: <?>
IP Address(es):
10.5.3.4
The reason the system could not register these RRs was because the DNS server contacted refused the update request.
But if I ping the PC by name from another machine or do an nslookup, or heck even check the DNS RSAT tool, I get a valid and correct name to IP mapping. Since DHCP has a user account setup that updates DNS, name resolution is working. So is this just a benign thing and I can just ignore it?
10.1.1.1 (2012 R2 DC, DNS, DHCP)
10.1.1.2 (2008 R2 DC, DNS, DHCP) - slated to be replaced with 2012 R2 DC, DNS, DHCP this weekend)
10.30.1.1 (2008 R2 DC, DNS) - slated to be replaced with 2012 R2 DC, DNS in the next 60 days).
Domain Functional Level: 2008 R2 until the last two DC's can be replaced (on our timeline).