Issue 617738 has been merged into this issue.

Raising priority to P1 as this issue may impact many EDU/Enterprise customers that have .local Windows domains.

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 everything worked fine but none of the company intranet sites that end with .local no longer work. Everything still fine on Windows workstations.

ReleaseBlock-Stable as this is a regression and needs to be fixed.

Whom is the right person to look at this? (not sure if Chrome side or OS side)

We are doing another stable test round on Thursday so if we can get a quick fix for this in the next 24 hours we can make the next stable push.

Brian, could you take a look?

For the record, plenty of people (including Microsoft now, I believe) discourage use of .local TLD for unicast DNS. But we deal with the real world, so...

I guess we'll want to just back out  issue 199397  for stable (it's not currently a critical feature, so we can easily delay/modify it), and look at options like adding an "off" switch for Avahi.

If it is a revert of https://chromium-review.googlesource.com/#/c/330199/ and you feel it is safe please feel free to merge it into R51 to unblock this.

For a more comprehensive fix, is there any chance we would have something in the next couple weeks (if not we may also need to merge this revert to R52). 

Also note, we want to kick off a build for the next R51 this afternoon, so if we want this in 51 we probably want it soon.

Uploaded:

https://chromium-review.googlesource.com/#/c/355120/

We'll probably want to just revert this on R52 as well.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/0a5f971f118791d7737a14679fb58bb13a395518

commit 0a5f971f118791d7737a14679fb58bb13a395518
Author: Brian Norris <briannorris@chromium.org>
Date: Wed Jun 22 20:11:54 2016

disable mDNS resolution for glibc

This conflicts with resolution of the non-standard .local TLD used in
some enterprises. It isn't yet critical to any other major launched
features, so let's disable it for now while we figure out a more robust
plan for when/if we want to turn this back on.

This is a partial revert of commit 194e3fbc9b6d ("turn on mDNS
resolution in ChromeOS").

BUG= chromium:611631 
TEST=check that mDNS names can no longer be resolved (e.g., find nearby
     device via `avahi-browse -atr` and try to `ping foo.local`)
TEST=resolve foo.local hosts from a local DNS server

Change-Id: I25b67f9554aeb6ffd95746068dd9f776c32fb3d1
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/355120
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/0a5f971f118791d7737a14679fb58bb13a395518/profiles/targets/chromeos/package.use

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/37999ce4fe8725f04f15f317eb08af28da730d30

commit 37999ce4fe8725f04f15f317eb08af28da730d30
Author: Brian Norris <briannorris@chromium.org>
Date: Wed Jun 22 20:11:54 2016

disable mDNS resolution for glibc

This conflicts with resolution of the non-standard .local TLD used in
some enterprises. It isn't yet critical to any other major launched
features, so let's disable it for now while we figure out a more robust
plan for when/if we want to turn this back on.

This is a partial revert of commit 194e3fbc9b6d ("turn on mDNS
resolution in ChromeOS").

BUG= chromium:611631 
TEST=check that mDNS names can no longer be resolved (e.g., find nearby
     device via `avahi-browse -atr` and try to `ping foo.local`)
TEST=resolve foo.local hosts from a local DNS server

Change-Id: I25b67f9554aeb6ffd95746068dd9f776c32fb3d1
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/355130
Reviewed-by: Andrew de los Reyes <adlr@chromium.org>

[modify] https://crrev.com/37999ce4fe8725f04f15f317eb08af28da730d30/profiles/targets/chromeos/package.use

[Automated comment] Reverts referenced in bugdroid comments, after merge request, needs manual review.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/90d73bd671f5c9b3cd4a487cce4bd49b7c084dc1

commit 90d73bd671f5c9b3cd4a487cce4bd49b7c084dc1
Author: Brian Norris <briannorris@chromium.org>
Date: Wed Jun 22 20:11:54 2016

disable mDNS resolution for glibc

This conflicts with resolution of the non-standard .local TLD used in
some enterprises. It isn't yet critical to any other major launched
features, so let's disable it for now while we figure out a more robust
plan for when/if we want to turn this back on.

This is a partial revert of commit 194e3fbc9b6d ("turn on mDNS
resolution in ChromeOS").

BUG= chromium:611631 
TEST=check that mDNS names can no longer be resolved (e.g., find nearby
     device via `avahi-browse -atr` and try to `ping foo.local`)
TEST=resolve foo.local hosts from a local DNS server

Change-Id: I25b67f9554aeb6ffd95746068dd9f776c32fb3d1
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/355140
Reviewed-by: Andrew de los Reyes <adlr@chromium.org>

[modify] https://crrev.com/90d73bd671f5c9b3cd4a487cce4bd49b7c084dc1/profiles/targets/chromeos/package.use

I think the 'Merge-Review-52' labels got applied because @15 added Merge-Approved-52 but didn't remove Merge-Request-52?

Anyway, this should be fixed on the R51, R52, and ToT branches.

Ver 49.0.2633.112 works fine. I can access all .local sites. 
As soon as the Chromebook is updated to 51.0.2704.103 (updated 2016-06-23 2:50 est), .local sites become inaccessible again.

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I think I'm moving the correct labels. Feel free to relabel as appropriate.

This should be fixed on M51 if you're using image 8172.60.0 or higher, an image that was built on 6/22/16 and has made it out to several (but not all) devices.

@ adecusati, If you no longer see this issue on latest 54 build. Can you close this as verified?

I am currently on 55.0.2858.0 and can verify the issue is resolved.

Thanks!