Issue metadata
Sign in to add a comment
|
Async resolver: cases where only the first configured nameserver can handle certain resolutions
Reported by
wdm...@gmail.com,
Jun 4 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 7978.74.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.103 Safari/537.36 Platform: 7978.74.0 (Official Build) stable-channel panther Example URL: Any URL on the local LAN. Steps to reproduce the problem: 1. Set up a web server on the local LAN. 2. Set up a DNS server on the local LAN. 3. Change the settings in Chrome: Settings/Internet connection/Ethernet or WiFi network/Network tab/Custom name servers/192.168.2.7 and 8.8.8.8 and 8.8.4.4 4. Type a local URL into the address bar. What is the expected behavior? Display the page. What went wrong? DNS_PROBE_FINISHED_NXDOMAIN shown in the window. Did this work before? Yes Previous to 50. Chrome version: 50.0.2661.103 Channel: stable OS Version: 7978.74.0 Flash Version: Shockwave Flash 21.0 r0 Local DNS reolution FAILS on two other Chromebooks on dev channel (version 52). Local DNS resolution FAILS on Android Chrome Beta (version 51) with DNS_PROBE_FINISHED_BAD_ERROR so I may have done something wrong. Local DNS resolution SUCCEEDS on Linux (version 49 32 bit). Local DNS resolution SUCCEEDS on Windows (version 50). I do not have access to a Mac. I do not have access to an iOS device.
,
Jun 8 2016
That first log file was from: Google Chrome 50.0.2661.103 (Official Build) (64-bit) Revision 0 Platform 7978.74.0 (Official Build) stable-channel panther
,
Jun 8 2016
Thank you for providing more feedback. Adding requester "rsleevi@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
,
Jun 13 2016
I can confirm that local DNS no longer works after updating Chrome OS on our corporate Chromeboxes to version: 51.0.2704.79, stable-channel. Before this update today (6/13/2016) everything worked fine but none of the company intranet sites no longer work. Everything still fine on Windows workstations.
,
Jun 13 2016
Julia: Could you look into this? I see via the NetLog that 192.168.2.7 is selected, the internal DNS server is enabled, but resolutions for the internal names are going through the second DNS resolver, not the first. Presumably, the correct client config is to specify only a single nameserver - that is, I'm guessing the code assumes all nameservers specified are equally capable of resolving, and this is clearly not the case.
,
Jun 13 2016
,
Jun 14 2016
Update: Looks like the problem is isolated only to .local domain names using local DNS servers. I have set up another private domain for our intranet using a different private .domain address and it works just fine.
,
Jun 14 2016
Note: Using private gTLDs like that is a recipe for issues, pursuant to the ICANN's SSAC report. I would strongly encourage you to make use of domains within a registered gTLD (for example, 'mycompany.com' or 'internal.mycompany.com') to avoid issues. .local is tricky because it triggers multicast DNS (RFC 6762), so I'm surprised it worked at all.
,
Jun 25 2016
Changing the TLD makes no difference for me.
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
May 8 2017
,
May 9 2017
,
Mar 2 2018
,
Mar 2 2018
,
Mar 22 2018
,
Jan 15
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rsleevi@chromium.org
, Jun 7 2016Components: -Internals>Network Internals>Network>DNS
Labels: Needs-Feedback