From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2@gmail.com Subject: bug#30613: 'avahi-resolve .local' works but 'ssh .local' fails w/ "Name or service not known" Date: Tue, 27 Feb 2018 14:23:01 -0500 Message-ID: <868tbefd9m.fsf@gmail.com> References: <86fu5nalm9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60059) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqkr8-0007Zx-My for bug-guix@gnu.org; Tue, 27 Feb 2018 14:24:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eqkr4-0007Z2-PF for bug-guix@gnu.org; Tue, 27 Feb 2018 14:24:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:56307) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eqkr4-0007Yw-Kn for bug-guix@gnu.org; Tue, 27 Feb 2018 14:24:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eqkr4-0006Wq-FG for bug-guix@gnu.org; Tue, 27 Feb 2018 14:24:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <86fu5nalm9.fsf@gmail.com> (George myglc's message of "Mon, 26 Feb 2018 09:09:18 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 30613@debbugs.gnu.org On 02/26/2018 at 09:09 George myglc2 Clemmer writes: > Running the attached config in a QEMU image, 'avahi-resolve > .local' works but 'ssh .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