Certain sites won't load but others will

muffinsteeze

Honorable
Feb 18, 2013
10
0
10,520
Hello,

Certain sites won't load through my desktop's ethernet connection (Chrome error code DNS_PROBE_FINISHED_NXDOMAIN) while others work perfectly fine. I'm sure this is an issue with my computer, since the same sites aren't loading on both Chrome and Firefox, and my laptop and phone can access those sites through the same network just fine.

I've already tried ipconfig /flushdns in the command prompt (which didn't help) as well as tracert. When I try to use the tracert command with sites I can't reach, I get an immediate error message stating "Unable to resolve target system name (site name)," with no attempt of actually connecting being made.

JKoMmG9


I've searched through several threads and can't seem to find a fix that works for me, any help is appreciated!
 
Solution
That error means that your DNS servers are not able to resolve (look up) the IP address for the site you entered. This can happen for a number of reasons .. DNS servers crashed, DNS caching on your router/modem not working properly, VPN/proxy interfering, virus, etc. The easy fix is to go into your connection properties (control panel->Network and Sharing->click your connection->click properties->select Internet Protocol Version 4 and click properties) and manually enter new DNS servers (8.8.8.8 and 8.8.4.4 are free ones run by google).

If you want to find the root of the problem, I would do enter "ipconfig /all" from a command prompt. One of things listed will be your DNS servers. If the DNS server address matches your router address, then it is probably caching on your router that is messing up. Often a router restart will fix this. If the DNS servers belong to your ISP then they might be having an issue. If they are set to 127.0.0.1 then there is some software on your computer (good or bad) that intercepting the requested.
 

muffinsteeze

Honorable
Feb 18, 2013
10
0
10,520

Hello, thanks for your reply. I have tried manually entering those Google servers before, but it did not fix my issue.

I ended up going into the registry and manually disabling and re-enabling Dnsclient, which seems to have solved the problem. I followed the directions here, in case others stumble upon this issue in the future.
 
Solution