Issue metadata
Sign in to add a comment
|
Add option to disable built-in Async DNS resolver
Reported by
pa...@diovani.com,
Jul 3 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Example URL: http://example.dev Steps to reproduce the problem: 1. Configure DnsMasq (or other local resolver) to resolve .dev domains 2. Add "nameserver 127.0.0.1" to /etc/resolve.conf 3. Try to visit any .dev domain What is the expected behavior? Load local website served in .dev What went wrong? "This site can’t be reached This site on the company, organization or school intranet has the same URL as an external website. Try contacting your system administrator. ERR_ICANN_NAME_COLLISION" Did this work before? Yes There was a disable-async-dns chrome:flag, removed in commit eabf1f Chrome version: 59.0.3071.86 Channel: stable OS Version: Flash Version: The Built-in Async DNS bypass local (OS) DNS resolver and that a causes a series of problems: For Web Developers, for example, when adding a local domain to overrides a public one, for development purposes, Chromium often ignores it. A simple option in Advanced Settings to disable Async DNS resolver shall solve that problem. However, I don't think Chromium should resolve DNS anyway, since it's usually due to the OS.
,
Jul 5 2017
,
Jul 5 2017
+eroman, does your comment on https://bugs.chromium.org/p/chromium/issues/detail?id=702981#c3 also applies here? I don't know whether that's also expected to apply when configuring a local resolver.
,
Jul 6 2017
If system host resolution is returning 127.0.53.53, then this is a WontFix duplicate of issue 702981 . But from the user description it sounds like it could be an issue where the async DNS resolver is incorrectly obtaining 127.0.53.53 by not using the correct nameserver. @paulo: Can you include the result from the following commands: nslookup example.dev nslookup example.dev 127.0.0.1 ping -c 1 example.dev It looks like support for disabling async resolver was intentionally removed in issue 432236 , but bugs in applying system settings should be addressed.
,
Jul 6 2017
Here it goes: ➜ ~ nslookup example.dev Server: 127.0.0.1 Address: 127.0.0.1#53 Name: example.dev Address: 127.0.0.1 ** server can't find example.dev: NXDOMAIN ➜ ~ nslookup example.dev 127.0.0.1 Server: 127.0.0.1 Address: 127.0.0.1#53 Name: example.dev Address: 127.0.0.1 ** server can't find example.dev: NXDOMAIN ➜ ~ ping -c 1 example.dev PING example.dev (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms --- example.dev ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.032/0.032/0.032/0.000 ms And here my resolve.conf, dnsmasq and hosts configuration: ➜ ~ cat /etc/hosts # # /etc/hosts: static lookup table for host names # #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost paulodiovani-ideapad ::1 localhost.localdomain localhost paulodiovani-ideapad # End of file ➜ ~ cat /etc/dnsmasq.d/dev-tld local=/dev/ address=/dev/127.0.0.1 ➜ ~ cat /etc/resolv.conf # Generated by resolvconf # Local (dnsmasq) resolver nameserver 127.0.0.1 # ISP resolver nameserver 189.7.112.36 nameserver 189.7.112.31 # Google DNS serves nameserver 8.8.8.8 nameserver 8.8.4.4
,
Jul 6 2017
Thank you for providing more feedback. Adding requester "eroman@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 6 2017
What does chrome://net-internals/#dns show as the resolved IP for example.dev? Either way, punting this to DNS folks.
,
Jul 6 2017
Well, currently it points to 127.0.0.1. I forgot to mention on the issue that local .dev names sometimes (most of time, actually) works. But it randomly fails with ERR_ICANN_NAME_COLLISION error. I'll paste the chrome://net-internals/#dns as soon as it fails again (probably tomorrow)
,
Jul 6 2017
I see thanks. If it is only failing for certain .dev names and not the general case, then this is a duplicate of issue 702981 (and working as intended). By sporadic do you mean the same hostname fails only sometimes? Or is it consistent per hostname.
,
Jul 20 2017
Guys, I've recently (last Friday, to be exactly) migrated to Chromium (open source) and noticed that the problem happens only on Google Chrome (which I was using before).
,
Jul 20 2017
Please answer the questions in comment #9 and can you also please attach a net-internals log covering the failed resolution attempts?http://dev.chromium.org/for-testers/providing-network-details
,
Jul 20 2017
,
Aug 3 2017
Can you please respond to the question in comment 9 and 12. We can't make further progress without that information, and will have to close the bug otherwise.
,
Aug 3 2017
Oh, sorry for the delay. I'm currently unable to reproduce the bug. I'm not using local .dev domains for some time and as I said before it stopped happening since I've migrate to Chromium. It's ok if you want to close the bug for now.
,
Aug 3 2017
Thank you for providing more feedback. Adding requester "pauljensen@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 4 2017
This may be unreproducible presently due to fixing of Issue 747069 .
,
Mar 2 2018
Closing, see comment #17. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Jul 5 2017