This DNS issue is driving me crazy!

m.donelon1

Prominent
Jan 11, 2018
6
0
510
My computer is the only one suffering from the DNS just dropping randomly. I have a laptop, phone, and desktop downstairs that all work on my network whenever the DNS drops on my computer upstairs. My computer is connected via wifi and so are the rest of my computers. I have my preferred DNS set to 8.8.8.8 and my secondary DNS set to 8.8.4.4.

Whenever it disconnects, I can not access any websites and Google Chrome says that the DNS can not be resolved. I can still play online video games and watch streams whenever it is down, so I know that my internet is not out completely. If I am talking to my friends on Discord, my Discord will time out and I won't be able to hear them or speak to them until my DNS comes up.

I have replaced my NIC and this didn't solve the issue, I have flushed my DNS and that didn't work, I have manually set my DNS to Google's, I have manually set my IP address, and I made sure that all my BIOs are up to date and set back to default.

This only lasts for 10 - 15 seconds before it comes back online, but it happens enough to drive me insane. I have no clue what else I can do to resolve this so any help is very appreciated.
 
Solution
1) On each computer on your network, open the Chrome browser.

2) Cut and paste this link into address bar:
chrome://flags/#load-media-router-component-extension

3) Next to the entry "Load Media Router Component Extension", change the setting to 'Disable'

4) Click relaunch at bottom of page. (Chrome should re-launch with flag showing 'Disabled').

5) Reboot your router (and any bridge).

That's it... hope this works.
Very strange. Only losing DNS packets would point to a firewall type issue, but then you would lose all your DNS packets. Not just a couple here and a couple there. I think you might be having brief periods of high packet loss not enough to mess with your game or video stream (games are built to have brief interruptions and video buffers), but enough to mess with other stuff. I would like you to some ping tests to check.

Open a command prompt.

type "tracert google.com"

type "ping "x.x.x.x -n 100" where the x.x is the IP address of the first thing listed on the tracert. This should be your router or wifi AP. You should see a very small time (1ms ish) and no lost packets. Since this is an intermittent problem, you might have to up the -n or keep running it until you experience an issue. If you go though an episode dis-connectivity, but the pings are steady, then you can be sure it's not a wifi problem.

type ping "x.x.x.x -n 100" where the x.x is the IP address of the 2nd thing listed on the tracert. This should be your ISP. Keep doing it until the issue pops up. Again, if you don't see any packet loss (less than 1% is ok) then this is really, really wacky.

Let us know what results you get.

BTW ... you manually set your IP address ... are you sure it is outside the address range used by DHCP on your router? Weird things happen when 2 machines have the same IP address.
 

m.donelon1

Prominent
Jan 11, 2018
6
0
510


Hi anotherdrew, thank you for your response. When I set my IP address, I made sure it was in the address range used by DHCP. Doing some more troubleshooting, I figured out that the driver that my NIC was using was actually out of date (thanks disc that came with my NIC). So I went onto the website and downloaded the latest driver for my NIC and so far, have not had any DNS issues. I'm not calling it yet, but I think it has fixed my issue. If it hasn't, I will let you know and follow your troubleshooting steps and see where it goes from there.
 

m.donelon1

Prominent
Jan 11, 2018
6
0
510
Hi anotherdrew,

I'm experiencing those issues again and I have tried your troubleshooting steps. With the first IP address from the tracert, it does time out when my DNS goes down.
 
The first address should be your router (starting with 192, 172, or 10?). If you get a timeout while trying to ping that, then you have lost the connection to your router. Since you are connect by wifi, my guess is some kind of interference.

If possible, I would log into the router (I assume that is what is providing the wifi) and change the channel it's on. See if that helps. If you are connecting on 5Ghz, try switching to 2.4Ghz ... it might be slower, but the connection should be more stable.
 

m.donelon1

Prominent
Jan 11, 2018
6
0
510
Alright, I think I'm noticing a trend here. I have set both my 5Ghz and 2.4Ghz to channels that are not being used and left the ping test running while I go and visit other websites. I launched a game called "League of Legends" and noticed that as soon as I did that, my requests started to time out. Thinking it was League of Legends that was causing the issue, I waited until my pings started to reply again and I clicked on google chrome, as soon as I did that, my requests started to time out again. It seems like every time I try to get information, it will time out my connection.
 

m.donelon1

Prominent
Jan 11, 2018
6
0
510
No dice on that one either. I'm digging through my Event Logs and noticed something else:

This error:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user DESKTOP-DHDRTL1\mount SID (S-1-5-21-1259708388-4038667164-718768099-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


Seems to occur either before or after my DNS issue. This is also the log for my DNS when it happens:

Name resolution for the name storeedgefd.dsx.mp.microsoft.com timed out after none of the configured DNS servers responded.


 
storeedgefd.dsx.mp.microsoft.com is part of the Windows 10 store. If you are running any "Don't track me" type software, that is what is probably blocking it.

If I open a command prompt and enter "nslookup storeedgefd.dsx.mp.microsoft.com"

This is the response I get:

Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: e1898.dspg.akamaiedge.net
Addresses: 2600:1404:b:184::76a
2600:1404:b:196::76a
23.72.143.14
Aliases: storeedgefd.dsx.mp.microsoft.com
storeedgefd.dsx.mp.microsoft.com.akadns.net
storeedgefd.dsx.mp.microsoft.com.edgekey.net
storeedgefd.dsx.mp.microsoft.com.edgekey.net.globalredir.akadns.net
e1898.dspg.akamaiedge.net

That is from OpenDNS servers ... I tried it with google (8.8.8.8) and AT&T DNS servers and got the same response.

If you google "SID S-1-5-21" ... you will find enough to keep you up all night. A real mess. Microsoft says just ignore it or fix it by giving this unknown user full permission. I went with ignore.

https://support.microsoft.com/en-us/help/4022522/dcom-event-id-10016-is-logged-in-windows-10-and-windows-server-2016

I'm experiencing those issues again and I have tried your troubleshooting steps. With the first IP address from the tracert, it does time out when my DNS goes down.

Ping is about the simplest form of internet communication. One machine says hi and another machine says hi back. If you can't ping, you can't do anything. That's why I am saying it's not your DNS that is going down, but instead your connection. The connection is made up of your machine, the router and stuff in between. The router seems fine (noone else has a problem). The stuff in between (WiFi) is probably ok. That leaves your machine. It is either software or hardware.
Did you try to reload your drivers? Settings->Network Status->Network Reset
Do you have a spare WiFi adapter (USB or card) around that you could test with?
Can you temporarily run a cable to the router?
 

mattwinnj

Prominent
Jan 23, 2018
1
0
520
1) On each computer on your network, open the Chrome browser.

2) Cut and paste this link into address bar:
chrome://flags/#load-media-router-component-extension

3) Next to the entry "Load Media Router Component Extension", change the setting to 'Disable'

4) Click relaunch at bottom of page. (Chrome should re-launch with flag showing 'Disabled').

5) Reboot your router (and any bridge).

That's it... hope this works.
 
Solution