bug#30613: 'avahi-resolve <host>.local' works but 'ssh <host>.local' fails w/ "Name or service not known"

[myglc2@gmail.com]

On 02/26/2018 at 09:09 George myglc2 Clemmer writes:

> Running the attached config in a QEMU image, 'avahi-resolve
> <host>.local' works but 'ssh <host>.local' fails w/ "Name or service not
> known".
>
> E.g, ...
>
> g1@server02 ~$ avahi-resolve --name nemo.local
> nemo.local      fe80::1ccf:c589:7e5f:a21f
>
> g1@server02 ~$ ssh -vvv nemo.local
> OpenSSH_7.6p1, OpenSSL 1.0.2n  7 Dec 2017
> debug2: resolving "nemo.local" port 22
> ssh: Could not resolve hostname nemo.local: Name or service not known
>
> g1@server02 ~$ guix --version
> guix (GNU Guix) 0.14.0-9.bdf0c64
>
> TIA - George

FWIW, I notice irratic reports about starting avahi-daemon in
shepherd.log ...

g1@g1 ~/bug/30613-avahi-resolve.works.ssh.doesnt/log$ grep avahi shepherd.log 
2018-02-25 22:08:26 Service avahi-daemon has been started.
2018-02-25 22:09:42 Service avahi-daemon has been started.
2018-02-27 08:27:15 Service avahi-daemon has been stopped.
2018-02-27 08:30:53 Service avahi-daemon has been started.
2018-02-27 08:55:23 Service avahi-daemon could not be started.
2018-02-27 11:26:12 Service avahi-daemon has been started.

... and when it does start, a warning about no NSS support in
/var/log/messages:

g1@g1 ~/bug/30613-avahi-resolve.works.ssh.doesnt/log$ grep avahi debug
Feb 25 22:08:24 localhost avahi-daemon[346]: Found user 'avahi' (UID 998) and group 'avahi' (GID 983).
Feb 25 22:08:25 localhost avahi-daemon[346]: Successfully dropped root privileges.
Feb 25 22:08:25 localhost avahi-daemon[346]: avahi-daemon 0.7 starting up.
Feb 25 22:08:26 localhost avahi-daemon[346]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb 25 22:08:27 localhost avahi-daemon[346]: Successfully called chroot().
Binary file debug matches
g1@g1 ~/bug/30613-avahi-resolve.works.ssh.doesnt/log$ 

HTH - George