New issue
Advanced search Search tips

Issue 871009 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Aug 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

random DNS_PROBE_FINISHED_NXDOMAIN problem

Reported by eppikga...@gmail.com, Aug 4

Issue description

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

Example URL:
https://www.youtube.com/

Steps to reproduce the problem:
1.open chromium
2. visits website for a random amount of time 
3. 

What is the expected behavior?
to open a web site 

What went wrong?
chromium gives DNS_PROBE_FINISHED_NXDOMAIN

Did this work before? Yes 67

Chrome version: 68.0.3440.75  Channel: stable
OS Version: 68.0.3440.75
Flash Version: 

this problem a curse on two different systems 
dye have bin tested with 3 different DNS servers 
and if domain is checked by using  dig, ping it works 

the system works when resting the DNS cash
 
os kde neon 5.13.4
when resting the DNS cash it workes some times
Labels: Needs-Triage-M68 Needs-Bisect
Cc: vamshi.kommuri@chromium.org
Components: -Internals>Network Internals>Network>DNS
Labels: -Needs-Bisect Needs-Feedback Triaged-ET
Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 68.0.3440.75 using Ubuntu 17.10 with the below mentioned steps.
1. Launched Chrome
2. Navigated to https://www.youtube.com/
3. Randomly visited few other websites.
We observed that all of them rendered properly without any errors. As this seems to be specific to Network removing Needs-Bisect label and adding appropriate component. 

@Reporter: Could you please attach the NetLog, which helps us to triage the issue further in a better way. Please find the below URL to get the NetLog.
https://www.chromium.org/for-testers/providing-network-details
Ping? Reporter, could you please answer the question in comment #3?

Status: Archived (was: Unconfirmed)
Closing due to lack of response. Feel free to file a new bug with the requested information if you're still having issues.

Sign in to add a comment