Windows 10: DNS error / unexpected disconnections
SolvedPeterPettigrow Posted messages 9 Status Membre -
Good evening/Hello,
For the past few days, I've been bothered by a disconnect/reconnect issue (lasting a few seconds), occurring randomly and frequently (every 5/10 minutes).
I noticed the creation of logs during these events (see capture_01), and I haven't found a solution despite my searches.
I'm connected via Ethernet and the issue is not with the cable. Having a dual-boot Linux-Windows, the problem appears only under Windows.
Error messages:
- The system could not register the host resource records (RR) (A or AAAA).
- Failed to update and delete host resource records (RR) (A or AAAA) from the network adapter.
What I've attempted:
- "ipconfig /registerdns"
- restarting the computer
My research leads me to believe it is a DNS configuration issue, but my knowledge is limited...
Thank you in advance for your help!
5 réponses
Hello,
- No, no VPN.
- In the network adapter properties, everything is set to automatic.
- No server or AD in place.
I checked the logs under "Applications and Services Logs/Microsoft/Windows/NetworkProfile" and here are the event IDs that appear during a disconnection: 10001 - 4004 - 20002 - 10000 - 4002.
I don’t know if this can help understand the origin.
I also noticed that the orange LED on the port receiving the RJ45 turns off during the disconnection, then everything returns to normal 2-3 seconds later.
Thank you for your time.
Hello
I had the same problem as you a few weeks ago.
I think you have a hardware issue, and the problem is probably due to a faulty connection in the ethernet cable you are using.
The message in the event viewer about "DNS" is misleading because when you have a network interruption, it will automatically try several connection attempts to the DNS server.
Can you try changing the network cable to see if there's any change, please?
Hello,
I came to think the same thing before going to sleep.
And while doing a test of unplugging/replugging the cable, these DNS errors also appear.
I am misled by the fact that under Ubuntu (Dual Boot) I don't have (or haven't noticed) any internet interruption like under Windows ...
I will monitor the Ubuntu logs all day and retest by changing the cable under Windows.
I will come back to confirm this here afterwards,
Thank you.
Good evening everyone,
The issue seems to be resolved this evening. No disconnections or error logs after leaving the machine running for 3 hours.
The cause: a faulty driver...
The steps:
- Device Manager -> Network adapters -> uninstall all (making sure to check the box "delete the associated drivers" if present).
- Device Manager -> "Action" tab -> "Scan for hardware changes".
- Not installing the optional update for the network adapter (see photo) allows me to no longer have disconnection issues.
One hypothesis is that the act of unplugging/replugging my motherboard caused the reinstallation of these drivers.
Another more likely hypothesis is that I messed up at some point.
I'm surprised that a 2015 driver offered would crash my network card to this extent.
The latest Realtek drivers also caused my network card to crash; perhaps my motherboard is too old (Asus p8p67le).
Thank you for your tips and ideas that helped me find the root of the issue.
Hello,
Thank you for your response. Unfortunately, 15 minutes after resetting the network, a disconnection occurred, and here are the logs:
"The system could not register the resource records (RR) hosts (A or AAAA)
of the network card.
The system could not register these resource records because the DNS server could not process the update request. The most likely cause is that the reference DNS server required for handling this update request has a lock on the zone, probably due to an ongoing zone transfer.
You can manually retry the DNS registration of the network card and its settings by typing "ipconfig /registerdns" at the command prompt. If the problem persists, contact the DNS server administrator or the network servers administrator."
The proposed solution "ipconfig /registerdns" has no effect either...