Ошибка 8018 dns client events

Win10 — DNS Client Events 8018 — The system failed to register host

• Question

• 

  

  0

  
  Sign in to vote
  

  On all Windows 10 Machines I recieve the following event log error:
  

  On all Windows 7 devices I do not recieve error like this.

  Thank you in advance

  Tuesday, May 3, 2016 8:49 AM

Windows 2012 R2 Member server
Windows 2012 R2 DC AD DNS DHCP
Windows 2012 R2 DC AD DNS DHCP

Just added a static IPV6 address to my Windows 2012 R2 DC

When it tries to register to DNs I get this error

Log Name:      System
Source:        Microsoft-Windows-DNS-Client
Date:          8/18/2015 10:30:05 PM
Event ID:      8018
Task Category: (1028)
Level:         Warning
Keywords:      
User:          NETWORK SERVICE
Computer:      SERV013.fqdn.com
Description:
The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

           Adapter Name : {525E4535-4128-42D5-B950-B7C2AB802B44}
           Host Name : SERV013
           Primary Domain Suffix : fqdn.com
           DNS server list :
                   fd99:aa4e:8286:a08d:0:ffff:a02:81e, fd99:aa4e:8286:a08d:0:ffff:a02:818, 10.2.8.30, 10.2.8.24
           Sent update to server : <?>
           IP Address(es) :
             fd99:aa4e:8286:a08d:0:ffff:a02:817, 10.2.8.23

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»>
  <System>
    <Provider Name=»Microsoft-Windows-DNS-Client» Guid=»{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}» />
    <EventID>8018</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>1028</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=»2015-08-19T02:30:05.479220200Z» />
    <EventRecordID>43735</EventRecordID>
    <Correlation />
    <Execution ProcessID=»924″ ThreadID=»336″ />
    <Channel>System</Channel>
    <Computer>SERV013.fqdn.com</Computer>
    <Security UserID=»S-1-5-20″ />
  </System>
  <EventData>
    <Data Name=»AdapterName»>{525E4535-4128-42D5-B950-B7C2AB802B44}</Data>
    <Data Name=»HostName»>SERV013</Data>
    <Data Name=»AdapterSuffixName»>fqdn.com</Data>
    <Data Name=»DnsServerList»>      fd99:aa4e:8286:a08d:0:ffff:a02:81e, fd99:aa4e:8286:a08d:0:ffff:a02:818, 10.2.8.30, 10.2.8.24</Data>
    <Data Name=»Sent UpdateServer»>&lt;?&gt;</Data>
    <Data Name=»Ipaddress»>fd99:aa4e:8286:a08d:0:ffff:a02:817, 10.2.8.23</Data>
    <Data Name=»ErrorCode»>9005</Data>
  </EventData>
</Event>

I ran  get-dnsserverzone | fl    and the DynamicUpdate  is Secure

I read somewhere this

DNS Server may have been busy placing a lock on the zone try this

ipconfig /registerdns  

Still event id 8018

In DNS the IPV6 address is not appearing.

I have two Windows 2008 Servers and added a static IPV6 address to them also and they registered to DNS

I can ping -6 serv011  as an example which is one of the DC’s no problem I get back the IPV6 address

Just this one Windows 2012 Server is not registering

Thoughts

With the majority of our users now working from home, we’ve run into an odd issue with some users’ VPN connectivity. We currently use Meraki with client VPN configured on each machine via a startup script.

We receive the following error on some client machines:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

          Adapter Name : {627771DA-5FD4-4B1F-8989-5C08C7ED351E}
          Host Name : company-001091
          Primary Domain Suffix : fqdn.com
          DNS server list :
              64.233.217.2, 64.233.217.3
          Sent update to server : 192.185.86.158:53
          IP Address(es) :
            192.168.0.120

The reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.

You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

This is followed by event ID 789 in RasClient. According to Meraki documentation, this should be troubleshooted by:

1. checking the PSK

2. ensure UDP ports 500 and 4500 are forwarded to the MX

3. Ensure AuthIP service is running

I have tried all to no avail. I have also tried:

• setting DNS servers manually (using 1.1.1.1 and 1.0.0.1)

• disabling IPv6

• using the built-in network reset utility

• changing networks, from wi-fi to mobile hotspot. This is successful for some users, who cannot use wi-fi with the VPN for some reason

• wiping the associated DNS entry and DHCP lease from the DC

The only solution that we have had 100% success with is reimaging the affected machine. Prior to using Meraki, we used SonicWall. We rolled a script to remove the old SonicWall client, so I would not be totally surprised if it had a part on some machines due to not completely removing the adapter or something else. However, this has occurred on several freshly imaged machines that never had SonicWall installed.

Any ideas?

So the situation is as follows.

We have rolled out Windows 10 laptops that auto-connect to the wireless.
The clients are Windows 10 and the DNS and DHCP server are Windows.
When they are docked, they detect the wired connection and disable wifi.

So far so good..

The problem:

We boot a laptop that has a wired connection, the machine will receive 2 IP addresses. 1 wired, 1 wireless.

> At this moment the DNS record on the DNS server has the Wifi address listed.

Windows will auto-deactivate the wireless connection and only the wired connection is listed as active.

> At this moment the DNS record on the DNS server still has the Wifi address listed. So there is no longer a way to connect to the machine through their hostname.

When I check eventlogs I get:

Log Name:      System
Source:        Microsoft-Windows-DNS-Client
Date:          25/05/2020 16:03:13
Event ID:      8018
Task Category: (1028)
Level:         Warning
Keywords:      
User:          NETWORK SERVICE
Computer:      .............
Description:
The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings: ....

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.

When I unplug the UTP cable and plug it back in, it registers fine and updates the DNS server. So I don’t understand why it would not work on boot.

I have found a solution that works, but is not the most secure:

When I go to our DNS server and I set Dynamic Updates to accept «Nonsecure and secure» and reboot the laptop, everything works without problem.

But since this is a major security risk I have set it back to «Secure only».

In short: For an unknown reason (and only at system startup) the wired IP is seen as insecure and the DNS server will not accept the request to register.