[Bug 1830531] Re: .local domain look ups do not trigger name publication

[Dan Kortschak]

Before I get a chance to look into this later today, I'd like to note
that the network device is not firewalling those packets since a few
days ago before I installed 18.04 on this machine it was behaving as
expected and the 16.04 machine mentioned in the OP is not being blocked
(it is on a slightly more restrictive policy than this one, but neither
block that port). As for the possibility of blocking outbound packets
from the machine itself, this seems most likely, however, as mentioned,
this is a new install and I have not added any firewalling policy that
would block them, suggesting that it's an out of the box setting.

I'll report back on these and the other tests when I am at that
location.

-- 
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/1830531

Title:
  .local domain look ups do not trigger name publication

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  On my local network I find that with 18.04 network name lookups using
  .local domains no not work unless stimulated by a non-18.04 machine
  first. This is observed for ssh, http, https and ping, but probably
  not limited to those.

  To demonstrate this here is a ping example.

  ~ $ ping pi.local
  ping: pi.local: Name or service not known
  ~ $ ping pi.local
  ping: pi.local: Name or service not known

  # At this point head to another machine running 16.04.6 and execute ping pi.local.
  # This is immediately successful. Then head back to the 18.04 machine.

  ~ $ ping pi.local
  PING pi.local (192.168.108.28) 56(84) bytes of data.
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
  ^C
  --- pi.local ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 7018ms
  rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

  After a couple of minutes, the name resolution fails again, but can be
  brought back again by following the procedure above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:04:58 2019
  InstallationDate: Installed on 2019-05-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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