What can cause `ERR_NAME_NOT_RESOLVED` DNS resolution errors in Chrome (Win 7 x64) that are eliminated by proxying through Fiddler2?

Question

Suddenly after updating Chrome (from v36 => v41 I think) I started having persistent DNS resolution errors in Chrome. Eventually after using Chrome for an indeterminate amount of time, when I try to visit an HTTP(S) URL Chrome will Display:

(In viewport:)

This webpage is not available

ERR_NAME_NOT_RESOLVED

(In console:)

net::ERR_NAME_NOT_RESOLVED

(In chrome://net-internals/#dns:)

error: -105 (ERR_NAME_NOT_RESOLVED)

The requests show up in Developer tools > Network as status: (failed).

Sometimes after displaying the error, sometime later it automatically "refreshes" and actually loads the page. Me refreshing the page multiple times sometimes gets it to load, but eventually becomes useless. At least sometimes it'll work fine for a while after being restarted, before eventually becoming unusable due to the errors. However, even after the problem has started it's intermittent: some requests still work after others haven't, with no apparent rhyme or reason. Onset of the error is perhaps linked to the number of windows / tabs that are open or the length of time Chrome has been running.

I suspect that Chrome may be exhausting some internal resource of which it's allocated an abritrarily low amount.

Premise

• Chrome 41-45 Win 7 x64 ("installed" via PortableApps, in case it matters).
• Prefetch resources to load pages more quickly / Predict network actions to improve page load performance was & is disabled
• Windows' DNS Client service (Dnscache) is stopped & disabled.
• There's no persistent antivirus running.
• Windows Firewall is running and has always been configured to allow Chrome access.
• When the problem happens in Chrome, other applications such as Firefox work with no problem. (I'm posting this with Firefox right now because Chrome refuses to load the site.)
• There's no proxy running (normally, see below).
• On chrome://net-internals/#dns, under Async DNS Configuration, there's Internal DNS client enabled: false. Clicking Host resolver cache Clear host cache doesn't help.
• None of the following had any effect:
  • Running in incognito mode with no extensions enabled.
  • Disabling hardware acceleration
  • Clearing cookies.
  • Creating and running under a new profile with no extensions except the defaults.
  • Resetting Chrome's settings.
  • Uninstalling and reinstalling (such as it is via PortableApps).

Proxy (Fiddler2)

This point is so special that I want to single it out: Running Fiddler2 (HTTP debugging proxy) and proxying Chrome through it eliminates the problem while Fiddler2 is running.

Questions

1. What could cause this problem?
2. What can be done about it?
3. What could explain the problem going away when proxying Chrome through Fiddler2?

Answer 1

The answer can be briefed as follows :

How does fiddler work in chrome :

If you notice the proxy setting while using fiddler ,it would be set as <loopback>

Now getting back to the problem :

Your settings would depend upon the internal browser settings,mostly it would depend upon the ie or firefox

1) flush and renew your DNS, you can do this with msprompt:

net stop dnscache
net start dnscache
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns

Now as you have mentioned that Windows DNS Client service (Dnscache) is stopped & disabled,Inorder to mitgate this try to start the DNS service as mentioned over here

Alternatively you could try to Repair/Reset Winsock settings using this command:

netsh winsock reset catalog

the above command will reset the catalog and you’ll need to restart your computer.you can check/see the data saved in DNS Cache through following command :

ipconfig /displaydns

Another solution might be ensure you have checked "Use the following DNS server addresses" and you could use the following dns

Preferred:  8 . 8 . 4 . 4
Alternate:   8 . 8 . 8 . 8
Check  "OK"

Ensure you doesnt use ipv6 if you use IPV6 address ,make sure that DNS is set back to automatic and IPv6 has been disabled.

Also you didnt mentioned about whether your ie or firefox working fine ,the last solution would be resetting chrome to defaults and import settings from default browser[ie/firefox]

if all the above solutions doesnt work ,do the following and edit the question : Re-enable the windows firewall connect to the router/modem per usual get a command prompt (start->run->cmd) and enter ipconfig /all >test.txt now copy the entire contents of test.txt

Answer 2

Try to flush and renew your DNS, you can do this with msprompt:

ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns

Other methods I'm seeing are adding DNS addresses manually and restarting your modem for 5 minutes.