Every time I open the Iron Browser I get these randomly generated hostname requests under the "chrome://net-internals/#dns " tab. For example:
Hostname Family Addresses Expires
bwlplnkenn IPV4 error: -105 (ERR_NAME_NOT_RESOLVED) 2013-03-19 23:59:06.802 [Expired]
Hlhoiochum IPV4 error: -105 (ERR_NAME_NOT_RESOLVED) 2013-03-19 23:59:06.881 [Expired]
Jfzyuggjhc IPV4 error: -105 (ERR_NAME_NOT_RESOLVED) 2013-03-19 23:59:06.799 [Expired]
These requests for non-existent hostnames are produced by the browser only on startup.They always appear in sets of 3 and similarly appear in Google Chrome. Does anyone know what this implies?
Thanks
Random "error: -105 (ERR_NAME_NOT_RESOLVED)" entries
Re: Random "error: -105 (ERR_NAME_NOT_RESOLVED)" entries
From Nico Weber (Chromium developer):
http://groups.google.com/a/chromium.org ... 58e6015fc5
If you type in a single-word search query, chrome needs to send a DNS request to check if this might be a single-word host name: For example, "test" might be a search for "test" or a navigation to "http://test". If the query ends up being a host, chrome shows an infobar that asks "did you mean to go to 'test' instead". For perf reasons, the dns query needs to be asynchronous.
Now some ISPs started showing ads for non-existent domain names ( http://en.wikipedia.org/wiki/DNS_hijacking ), meaning chrome would always show that infobar for every single-word query. Since this is annoying, chrome now sends three random DNS requests at startup, and if they all resolve (to the same IP, I think), it now knows not to show the "did you mean" infobar for single-word queries that resolve to that IP.
http://groups.google.com/a/chromium.org ... 58e6015fc5
If you type in a single-word search query, chrome needs to send a DNS request to check if this might be a single-word host name: For example, "test" might be a search for "test" or a navigation to "http://test". If the query ends up being a host, chrome shows an infobar that asks "did you mean to go to 'test' instead". For perf reasons, the dns query needs to be asynchronous.
Now some ISPs started showing ads for non-existent domain names ( http://en.wikipedia.org/wiki/DNS_hijacking ), meaning chrome would always show that infobar for every single-word query. Since this is annoying, chrome now sends three random DNS requests at startup, and if they all resolve (to the same IP, I think), it now knows not to show the "did you mean" infobar for single-word queries that resolve to that IP.
-
- Posts: 1
- Joined: Mon May 21, 2018 2:32 am
Re: Random "error: -105 (ERR_NAME_NOT_RESOLVED)" entries
That is a common issue, you can try this: windowshelper.co/fix-err-name-not-resolved-this-webpage-is-not-available/