New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 701256 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Random "This site can’t be reached" errors

Reported by michael....@gmail.com, Mar 14 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.90 Safari/537.36

Example URL:
N/A

Steps to reproduce the problem:
Hard to reproduce: sometimes when I try to load a site, I see "This site can’t be reached" (ERR_NAME_NOT_RESOLVED) page.

This on Linux, Ubuntu 16.10, and when I copy-paste the same URL to Firefox it works there.

Just few seconds ago I had this issue on that page https://www.handson.travel/

In most cases I have to wait a while until I can load it again. Very weird.

What is the expected behavior?
Chrome should be able to load any existing pages fine without that error.

What went wrong?
Random ERR_NAME_NOT_RESOLVED errors

Did this work before? Yes Do not remember but earlier Chrome versions didn't have this

Chrome version: 54.0.2840.90  Channel: n/a
OS Version: Ubuntu 16.10
Flash Version: Shockwave Flash 24.0 r0
 
Labels: Needs-Milestone

Comment 2 by mmenke@chromium.org, Mar 14 2017

Components: -Internals>Network Internals>Network>DNS
Status: Untriaged (was: Unconfirmed)
Could you please provide a net-internals log of this happening?  Instructions:  https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Comment 3 by mmenke@chromium.org, Mar 14 2017

Labels: Needs-Feedback
funnily, i just tried to load the notorious, most used web page ever,  www.facebook.com and that error happened again!

have captured all the net internals and attached here. hope this helps you to find the cause?!
net-internals-log.json
137 KB View Download

Comment 5 by mge...@chromium.org, Mar 16 2017

Labels: -Needs-Feedback
mmenke@ could you please take a look into the net-internals log attached in the comment #4

Thank You...

Comment 7 by mmenke@chromium.org, Mar 20 2017

Looks like both Chrome's stub resolver and the OS's DNS resolver failed to resolve the DNS address, so I don't think this is a Chrome bug.  That having been said, I don't own the DNS code, and haven't looked at it in years, so I can't say that's definitely the case.
Yes, this smells like a DNS issue to me. Happy to run some commands on my machine to narrow down the cause (Chrome's stub VS OS DNS resolver).

Or should I report this bug somewhere else? Suggestions very welcome.

Btw, I am on Ubuntu 16.10 if that helps.

Comment 9 by ajha@chromium.org, Mar 27 2017

Cc: juliatut...@chromium.org
Cc'ing 	juliatuttle@ for more inputs and help on triaging this further as per C#7 and C#8.
Owner: mge...@chromium.org
Owner: ----

Sign in to add a comment