• Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
5 years ago
We are seeing the following:

Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 17/05/2019 12:42:53
Event ID: 8018
Task Category: (1028)
Level: Warning
Computer: %computername%.domain.local
The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

Adapter Name : {C65AFE69-A06D-4FDF-B9A2-45656D966F4A}
Host Name : %computername%
Primary Domain Suffix : domain.local
DNS server list :,
Sent update to server :
IP Address(es) :

The reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.

To register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<Provider Name="Microsoft-Windows-DNS-Client" Guid="{1c95126e-7eea-49a9-a3fe-a378b03ddb4d}" />
<TimeCreated SystemTime="2019-05-17T11:42:53.150403200Z" />
<Correlation />
<Execution ProcessID="1676" ThreadID="9984" />
<Security UserID="S-1-5-20" />
<Data Name="AdapterName">{C65AFE69-A06D-4FDF-B9A2-45656D966F4A}</Data>
<Data Name="HostName">%computername%</Data>
<Data Name="AdapterSuffixName">domain.local</Data>
<Data Name="DnsServerList">,</Data>
<Data Name="Sent UpdateServer"></Data>
<Data Name="Ipaddress"></Data>
<Data Name="ErrorCode">9005</Data>


Want to thank us? Use: Patreon or PayPal or Bitcoins: bc1q4whppe29dw77rm4kv4pln0gqae4yjnxly0dny0hky6yhnafukzjsyrsqhk

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.

  • Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
4 years ago
I found that unjoining the domain and restarting the system before rejoining solved this,. It was a permission mismatch of some kind.