Windows 10 random DNS server isn't responding error.

OK, so for the past two weeks, I have gotten this random internet error (almost like once a week). Everything would be working fine and then just suddenly I have no internet, and having Windows troubleshoot it gives me the error "The DNS server isn't responding." The strange thing is though, my wifi was still working perfectly fine (tested on phone) and the other PC in the house that is wired had no issues, so that rules out my router/modem. Still to be on the safe side, I did my own troubleshooting and so I: 1) restarted the modem and router, 2) bought a new LAN cable just in case, 3) changed the DNS server manually to Googles' (8.8.8.8), 4) updated the LAN adapter drivers, 5) disabled and enabled the LAN adapter, 6) disabled IPv6, and 7) even flushed the DNS and renewed IP.

None of these solutions I read online worked, but you know what did? Restarting the PC. This led me to believe that this is a Windows issue, not any of my hardware. Considering it is only my PC which seems to be affected, and even if it lost the internet, everything else on the Network is working fine. And if the only fix seems to be to restart, then something in Windows is causing this. I just checked too when the last Windows update was, and wouldn't you believe it, 4/10/2019, update KB4493509. My issue only started happening on 4/14 ( I remember because Game of Thrones was starting soon). Never had an issue before, and that update is pretty close to cause me to wonder if it messed something up.

Also, the error seems to be pretty random, as it happened once, I restarted and all was good for the rest of the night. Then I left the PC on overnight to download a game and when I woke up, the game had finished and installed successfully but I lost internet again (this was on 4/14-15). After I restarted again and installed the new LAN drivers just in case, I didn't have this issue again until a week later, 4/23. Restarted and I was fine until today, 4/30. So I just wanted to ask if others have seen this issue, and if Microsoft is aware of any problems with the update or Windows 10 in general causing DNS errors that only a restart seems to fix. Thanks.

Its not a DNS error as such it gives that error as the internet is down and it cant connect DNS is this lan cable or wireless its not clear if its cable have you changed cable and tried a different port on the router? What is make model of router

Please download MINITOOLBOX and run it.

https://www.bleepingcomputer.com/dow...toolbox/dl/65/

Checkmark following boxes:



Flush DNS
Reset FF proxy Settings
Reset Ie Proxy Settings
Report IE Proxy Settings
Report FF Proxy Settings
List content of Hosts
List IP configuration
List Winsock Entries
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size
List Devices (problems only)



Click Go and post the result.

My IPS is Comcast, and it is a LAN cable, like I mentioned in my post. I even tried a new cable, and I tried a different port.

Try using google DNS which i believe to be 8.8.8.8 or 8.8.4.4.

bro67 said:

You never stated that you rebooted the Internet Gateway or cleared all devices to rule out a bad IP Table entry for that device. You can also clear out and reset the network with the following commands. https://support.microsoft.com/en-us/...nection-issues

By reboot Internet Gateway, you mean restart the modem and router, correct? I have tried that and it did not fix the problem (still, the PC restarting fixes it). I don't know how to clear all devices or clear the IP table, and would that mess up other things on my network?

Again, manually using the 8.8.8.8 DNS does not work, but I did just find an option in my router where it is checked to obtain DNS from ISP, or manually use whichever ones I want, making me wonder if changing my DNS on my PC is not working because the router is still attempting to get the DNS from ISP? I would assume the PC would override that. Again, I can still ping 8.8.8.8, just not an actual website (nor does nslookup work as it says DNS timed out).

bro67 said:

Go through the steps in the link. To clear devices on your Gateway, you will have to do a hard reset, by pressing and holding the reset button on the back of your gateway. You have to use a paperclip- to reset. If you want to use your own WIFI accesspoint/router, you can place the Gateway from Comcast in Bridge mode.

Your last sentence made me remember something: I currently have my own router connected to the ISP Modem/Router combo but I use my own to connect all my devices to it. Now, I usually do have it in bridge mode, but about a year ago there were some internet issues with Comcast and while troubleshooting with them, we left Bridge mode off. For whatever reason (maybe you can explain more) even though Bridge mode is off, all my devices are still able to connect to our own router, so I just never turned it back on since it was working (also due to fear of the network problems resurfacing).

My goal is for when this issue happens again, I will bypass my own Netgear router and plug into the modem itself (which in turn would also give me a completely different IP, 10.x.x.x) to see if that fixes anything. If it works, then I will renable Bridge mode to see if that was actually the cause. If plugging directly into the ISP modem though doesn't work, then I am at a loss at what is really causing the issue (besides, restarting both the modem and my router doesn't fix it either, so don't know what plugging into the modem would actually do except change my IP). Do you think Bridge mode not on could be causing the error, even though its only my one PC?