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

Page 2 of 2 FirstFirst 12

  1. Posts : 470
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #11

    Hard-coding the DNS address is the not the solution, because it worked before on auto. Therefore, I cannot see how that suddenly became an issue. You should not have to hard code the DNS entires as a matter of standard operating procedure.
      My Computer

  2. Samuria's Avatar
    Posts : 6,065
    windows 10
       #12

    By default the router will be the DNS server which is very slow and doesnt offer the protection opendns does to bad sites changin it can speed up your interent
      My Computer


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

    The problem seems resolved when I updated the driver to the latest-greatest 2017 version from the 2015 base version. I haven't seen timeouts lately so I am hoping it's resolved. It's definitely something introduced by the latest patch as none of the other devices have it.

    The Windows update wiped out the driver in effect and when I reinstalled it, I didn't realize it had to be patched (or updated) as well.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 15:10.
Find Us




Windows 10 Forums