touch-packages team mailing list archive

[Sami Haahtinen <ressu@xxxxxxxxxxxx>]

The 3rd level is a good indicator that we really want a proper DNS name.
I did investigate this very briefly back when this problem first
occurred.

I also think that the nsswitch alteration is a good solution in the
short term. The issue on the long term is that people with .local domain
will see a decrease in performance in name resolution. I'm not sure how
the nss module works internally, as in how fast it returns after an
invalid request, so I don't know what the actual effect is.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1441008

Title:
  under systemd avahi-daemon doesn't stay disabled when .local is
  detected

Status in avahi package in Ubuntu:
  Triaged

Bug description:
  When avahi daemon detects .local unicast domain, the daemon is
  disabled. When a user tries to resolve a domain name through nss, the
  daemon starts up.

  The root cause is most likely in systemd that starts the daemon when
  an application tries to access the socket through the systemd managed
  socket file.

  This behavior wasn't observed in 14.10 or earlier releases, thus the
  assumption towards systemd socket activation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: avahi-daemon 0.6.31-4ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 09:51:43 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-16 (506 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to vivid on 2015-03-18 (19 days ago)

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