Site can’t be reached because server DNS address could not be found

dictum · 16 Oct 2018

I am getting this right after the 1809 update which got pulled and I am back to 1803. My network card driver got wiped out with that disaster update, something got updated. I reinstalled the driver and now the networking is back but I frequently get this in chrome and all other networking activity is paused so it's not just Chrome. For example Netflix also malfunctions.
I never had this before.
There are no issues with other computers using the same wi-fi.

This site can’t be reached because server DNS address could not be found

Stitch194 · 16 Oct 2018

Have you attempted to run Troubleshoot Wifi problems in Settings > Update & Security > Troubleshoot and, or Ctrl. Panel > Troubleshooting > Network & Internet.

dictum · 16 Oct 2018

Stitch194 said:

Have you attempted to run Troubleshoot Wifi problems in Settings > Update & Security > Troubleshoot and, or Ctrl. Panel > Troubleshooting > Network & Internet.

I have and it's absolutely useless. It cannot find a problem. It's intermittent. It will work for 30-45 minutes then suddenly freeze for 3 minutes. Then start working again.

Ztruker · 16 Oct 2018

Check to see if IPV6 is enabled in Control Panel\All Control Panel Items\Network and Sharing Center

lehnerus2000 · 16 Oct 2018

Have you confirmed that your DNS settings didn't change?

I have had issues in the past where, for no obvious reason, my network settings changed to "auto-everything".

dictum · 16 Oct 2018

Ztruker said:

Check to see if IPV6 is enabled in Control Panel\All Control Panel Items\Network and Sharing Center

IPV6 is enabled.

dictum · 16 Oct 2018

I did update the driver. The card is:

Killer Wireless 1535 Network adapter

When the Win update wiped it out, I installed a fresh one. I just noticed that it defaulted to the 2015 version of the driver. Now I installed the 2017 version of the driver, driver version 12.0.0.448

I am hoping that will fix it.

dictum · 16 Oct 2018

I also clicked off "Allow the computer to turn off this device to save power".

Not sure if relevant or the cause here but it seems unnecessary.

dictum · 16 Oct 2018

lehnerus2000 said:

Have you confirmed that your DNS settings didn't change?
I have had issues in the past where, for no obvious reason, my network settings changed to "auto-everything".

I had my settings on 'auto-everything' since forever and it worked. And that's what they are now.

I reset the DNS servers from auto to this:

OpenDNS addresses: 208.67.222.222 and 208.67.220.220

It only took it for IPV4, for IPV6, said invalid entry.

lehnerus2000 · 18 Oct 2018

dictum said:

I had my settings on 'auto-everything' since forever and it worked. And that's what they are now.

Fair enough.

dictum said:

I reset the DNS servers from auto to this:

OpenDNS addresses: 208.67.222.222 and 208.67.220.220

It only took it for IPV4, for IPV6, said invalid entry.

IPv6 addresses use a different format to IPv4.

I've always hated IPv6 because the designers chose a confusing way of displaying the notation (when it is compacted).

You need to use something like:

compacted = 2620:0:ccc::2
actual = 2620:0000:0ccc:0000:0000:0000:0000:0002

Have a look at this page:
https://support.opendns.com/hc/en-us...s-for-OpenDNS-