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

Page 1 of 2 12 LastLast

  1. Posts : 502
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
       #1

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


    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
    Last edited by dictum; 16 Oct 2018 at 19:43.
      My Computer


  2. Posts : 430
    Windows 10 Pro
       #2

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


  3. Posts : 502
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #3

    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.
      My Computer


  4. Posts : 13,930
    Windows 10 Pro X64 21H1 19043.1503
       #4

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

    -image.png
      My Computers


  5. Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #5

    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".
      My Computer


  6. Posts : 502
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #6

    Ztruker said:
    Check to see if IPV6 is enabled in Control Panel\All Control Panel Items\Network and Sharing Center
    IPV6 is enabled.
      My Computer


  7. Posts : 502
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #7

    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.
      My Computer


  8. Posts : 502
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #8

    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.
      My Computer


  9. Posts : 502
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #9

    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.
      My Computer


  10. Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #10

    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-
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:52.
Find Us




Windows 10 Forums