New issue
Advanced search Search tips
Starred by 8 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows
Pri: 3
Type: Bug



Sign in to add a comment

When using system DNS resolver, local hostnames can't resolve to different loopback addresses from hosts file

Project Member Reported by est...@chromium.org, Jul 14 2015 Back to list

Issue description

Because we call ResolveHelper() which calls ServeLocalhost() before sending a DNS query to the system resolver, users can't use local hostnames in their hosts file if they are on a platform that uses the system resolver. For example, it would be nice if we respected this hosts file instead of bypassing it with ServeLocalhost():

127.0.0.1 foo1.localhost
127.0.0.2 foo2.localhost
 

Comment 1 by est...@chromium.org, Jul 14 2015

I'm not sure if there's much we can do here if we want to continue to avoid trusting the system resolver with local hostname queries.

rsleevi: you had previously advocated for ServeLocalhost() before ServeFromHosts() on the grounds of platform consistency; at the time I didn't understand what you meant because I thought ServeFromHosts() worked on all platforms. Now that I see that ServeFromHosts() is a noop when we're using the system resolver, I see what you mean. If we're going to break hosts files that contain non-127.0.0.1 loopback addresses, we should probably do it consistently on all platforms.
estark: I suppose an alternative would be that we could do filtering after handing off to the system resolver, and only allowing loopback addresses. That would have the effect of breaking something like

192.168.0.1 foo.localhost
but would allow
127.127.127.1 foo.localhost

Of course, we'd also have to figure out what filtering for IPv6 (since unlike IPv4, which has 127/8, IPv6 only has ::1)
Cc: -ttuttle@chromium.org juliatut...@chromium.org
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 3 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Comment 6 by est...@chromium.org, Apr 17 2017

Labels: -Pri-2 -Hotlist-Recharge-Cold Pri-3

Comment 7 by est...@chromium.org, Apr 17 2017

Labels: Hotlist-Recharge-Cold
Owner: mge...@chromium.org
Owner: ----

Sign in to add a comment