"This site can’t be reached" "DNS_PROBE_FINISHED_NXDOMAIN"
Reported by
akash.bn...@gmail.com,
Nov 10 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Open any website on a new tab 2. Change the tab focus to any other tab 3. newly opened tab becomes in grey colour and displays "This site can’t be reached" "DNS_PROBE_FINISHED_NXDOMAIN" error What is the expected behavior? What went wrong? DNS_PROBE_FINISHED_NXDOMAIN Tried DNS clearing Flushing Adapter reset Clearing data Everything! Did this work before? N/A Chrome version: 56.0.2914.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Nov 10 2016
,
Nov 12 2016
At first, I was on 56.0.2915.0 Just updated lately and now I didn't see the error as of till now. I'll definitely ping if it happens to see again with the dump data.
,
Nov 19 2016
Thank you for providing more feedback. Adding requester "rdsmith@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 19 2016
,
Dec 2 2016
I'm almost having the exact same issue on various websites when I first open Chrome Canary (Version 57.0.2938.1 canary SyzyASan). 1. Open Chrome, and open just about any website in my bookmarks. 2. It'll flash the 'DNS address could not be found', 'this site cannot be reached' error, and refreshes itself after about 1-2 seconds, and the site appears to load without issue. the latter is not constant. so there are some instances where i cannot access the website at all.
,
Dec 19 2016
We can ignore my previous comment, it appears my issue has been resolved (no longer seeing it in the last two builds. currently on 57.0.2955.0). Not entirely sure if it was indeed the same issue op was having, but it was a similar DNS error.
,
Dec 21 2016
akash.bnarayan@: Could you please update the thread as per C#1 if such issues are encountered frequently on the latest chrome versions.
,
Dec 28 2016
Going to close this issue - both reporters indicated the issue went away. If either of you encounter the problem again within the next week, comment here and I'll re-open. If it appears again after that, please file a new bug. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rdsmith@chromium.org
, Nov 10 2016