[Bug 1620567] [NEW] Avahi mistakenly detects a .local domain and disables itself

[Sulka Haro]

Public bug reported:

I have an issue where a mobile Intel Edison rig that uses Avahi switches
between WiFi hotspots using WPA Supplicant and the switch causing Avahi
to mistakenly detect the new network serves the .local domain when it
actually doesn't.

Steps to reproduce on in my case:

1) Configure a linux box to connect to the local wifi networks using
wpa_supplicant process, with multiple WPA networks being supported.

2) Shut down the primary network, so the box connects to the secondary
network (which is not connected to the primary and uses different DNS
servers).

3) Avahi randomly outputs the following following the switch and
requires the box to be rebooted. Following the reboot avahi has no issue
with the new network:

"Avahi detected that your currently configured local DNS server serves
a domain .local. This is inherently incompatible with Avahi and thus
Avahi disabled itself. If you want to use Avahi in this network, please
contact your administrator and convince him to use a different DNS domain,
since .local should be used exclusively for Zeroconf technology.
For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal"

The issue also occurs upon switching from the secondary to the primary
network without a full reboot.

** Affects: avahi (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  I have an issue where a mobile Intel Edison rig that uses Avahi switches
  between WiFi hotspots using WPA Supplicant and the switch causing Avahi
  to mistakenly detect the new network serves the .local domain when it
  actually doesn't.
  
  Steps to reproduce on in my case:
  
- 1) Configure a debian box to connect to the local wifi networks using
+ 1) Configure a linux box to connect to the local wifi networks using
  wpa_supplicant process, with multiple WPA networks being supported.
  
  2) Shut down the primary network, so the box connects to the secondary
  network (which is not connected to the primary and uses different DNS
  servers).
  
  3) Avahi randomly outputs the following following the switch and
  requires the box to be rebooted. Following the reboot avahi has no issue
  with the new network:
  
  "Avahi detected that your currently configured local DNS server serves
  a domain .local. This is inherently incompatible with Avahi and thus
  Avahi disabled itself. If you want to use Avahi in this network, please
  contact your administrator and convince him to use a different DNS domain,
  since .local should be used exclusively for Zeroconf technology.
  For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal"
  
  The issue also occurs upon switching from the secondary to the primary
  network without a full reboot.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1620567

Title:
  Avahi mistakenly detects a .local domain and disables itself

Status in avahi package in Ubuntu:
  New

Bug description:
  I have an issue where a mobile Intel Edison rig that uses Avahi
  switches between WiFi hotspots using WPA Supplicant and the switch
  causing Avahi to mistakenly detect the new network serves the .local
  domain when it actually doesn't.

  Steps to reproduce on in my case:

  1) Configure a linux box to connect to the local wifi networks using
  wpa_supplicant process, with multiple WPA networks being supported.

  2) Shut down the primary network, so the box connects to the secondary
  network (which is not connected to the primary and uses different DNS
  servers).

  3) Avahi randomly outputs the following following the switch and
  requires the box to be rebooted. Following the reboot avahi has no
  issue with the new network:

  "Avahi detected that your currently configured local DNS server serves
  a domain .local. This is inherently incompatible with Avahi and thus
  Avahi disabled itself. If you want to use Avahi in this network, please
  contact your administrator and convince him to use a different DNS domain,
  since .local should be used exclusively for Zeroconf technology.
  For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal"

  The issue also occurs upon switching from the secondary to the primary
  network without a full reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1620567/+subscriptions