DNS suffix search is incorrect one
Reported by
paulddra...@gmail.com,
Dec 20 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Example URL: Steps to reproduce the problem: /etc/resolv.conf nameserver 10.12.0.42 nameserver 10.12.64.42 nameserver 209.244.0.3 What is the expected behavior? Suffix search is not enabled. What went wrong? Suffix search is enabled. chrome://net-internals#dns Async DNS Configuration Internal DNS client enabled: true nameservers 10.12.0.42:53 10.12.64.42:53 209.244.0.3:53 append_to_multi_label_name true attempts 2 edns0 false ndots 1 num_hosts 73 rotate false search office.lucidchart.com timeout 1 unhandled_options false Did this work before? N/A Chrome version: 53.0.2785.116 Channel: n/a OS Version: Ubuntu 16.04 Flash Version: Shockwave Flash 24.0 r0 DNS suffix search causes problems for me with erroneous successes. I have it disabled for my system DNS. How can I disable it for Chrome?
,
Dec 21 2016
> Have you tried to restart the browser and see if the settings were updated? Yes, this is a persistent condition. I should mention that /etc/networking doesn't have dns-search configured either. (Not sure which Chrome uses on my system.)
,
Dec 21 2016
Can you upload your resolv.conf from while the issue is happening? I'm wondering if maybe you're using DHCP and that's setting a suffix search. As far as I know, Chromium uses the "search" option from /etc/resolv.conf. There's no way to disable suffix search if that's specified; you'd just need to remove it, or ask your DHCP client to stop setting it.
,
Dec 21 2016
,
Dec 22 2016
> Can you upload your resolv.conf from while the issue is happening? See first part of "Steps to reproduce problem".
,
Dec 22 2016
After some testing, it seems that I can change the search option by changing /etc/resolv.conf search example.com But there doesn't see to be a way to disable it. Though looking at resolv.conf documentation, maybe there isn't http://manpages.ubuntu.com/manpages/trusty/man5/resolv.conf.5.html
,
Dec 22 2016
Oh gosh, sorry, I didn't see that. That is indeed strange. So, we don't actually read /etc/resolv.conf directly; we construct a "resolver state" object using libc and then read the config out of the various fields. As such, I *think* the beef is between you and your libc, but I'm honestly curious where it's getting the value from, if not resolv.conf.
,
Dec 22 2016
> As such, I *think* the beef is between you and your libc Yeah, I think it is too. The resolv.conf documentation I link says > The search list is normally determined from the local domain name; by default, it contains only the local domain name. So it uses my hostname. I think this can be closed.
,
Dec 28 2016
Closing, per comment 8. Thanks for the followup! |
|||
►
Sign in to add a comment |
|||
Comment 1 by kapishnikov@chromium.org
, Dec 20 2016Components: -Internals>Network Internals>Network>DNS