Clients not registering in DNS

[ICTICJTilson]

Hi all

 

A primary school I support reported issues with users logging in this morning. I came in and to my surprise the clients are getting an IP address but are not registering in DNS.

I'm getting 8015 errors on my clients: "The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings"

 

I've ran DCDiag on the server and picked up that there was no credentials for dynamic DNS registration so I configured that but still no joy. As you can imagine this is causing several headaches as users cannot login and some of them where I have logged in locally I am having to reconfigure their DNS settings to the schools forwarder.

 

To confirm DHCP appears to be fine and ping tests are succesful so I dont believe its network.

 

I've also noticed Internet has stopped working on the server. There is obviously something very wrong here with DNS but I cannot get to the bottom of it especially as no changes have been made to the network/server as far as I am aware.

 

I would really appreciate any help on this.

[Chockster]

Sorry - not much help here from me I'm afraid, just a note that we're suffering a similar thing at the mo. The most obvious symptom for us is the inability to contact our proxy because of it, so no internet.

 

Obviously with it just popping up, a windows 10 update may be the cuplrit. We're on still on 1709 at the moment, deploying cumulative updates via SCCM, so it's harder to say what's changed.

 

I'm also nosing around this as a possible cause, but we're scratching our heads.

[ICTICJTilson]

Thanks Chockster, we have mostly got 1703 domain clients (looking to update soon) but my laptop is 1803 and I have the same issue. Like you say it has just 'popped up', currently this is the only site currently I have seen this issue (touch wood).

[ICTICJTilson]

All fixed, I simply recreated the virtual switch on the host. Not to sure how or why that worked but I knew it was a communication issue as dsdiag looked good when I ran it and on the server everything looked healthy in the logs and general networking tests. Hope this helps you Chockster and certainly one to remember.