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

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

[George myglc2 Clemmer]

[-- Attachment #1: Type: text/plain, Size: 507 bytes --]

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


[-- Attachment #2: server --]
[-- Type: application/octet-stream, Size: 1533 bytes --]

;;; server v1 config
(use-modules (gnu))
(use-modules (gnu system nss))
(use-service-modules ssh) ; openssh-service-type
(use-service-modules avahi)
(use-service-modules networking) ; dhcp-client-service
(use-package-modules
 base                  ; glibc-utf8-locales
 certs                 ; nss-certs
 emacs
 gnome                 ; gvfs
 linux                 ; mdadm
 screen
 ssh                   ; openssh mosh
 xorg
 )
(operating-system
  (host-name "v1")
  (timezone "America/New_York")
  (locale "en_US.utf8")
  (bootloader (grub-configuration (target "/dev/sda")))
  (file-systems (cons (file-system
			(device "g1sd")
			(title 'label)
			(mount-point "/")
			(type "ext4"))
		      %base-file-systems))
  (users (cons*
	  (user-account
	   (name "g1")
	   (group "users")
	   (supplementary-groups '("wheel"))
	   (home-directory "/home/g1"))
	  %base-user-accounts))
  (packages
   (cons*
    emacs-no-x-toolkit
    emacs-guix
    glibc-utf8-locales
    gvfs              ;for user mounts
    nss-certs         ;for HTTPS access
    openssh
    screen
    xauth
    %base-packages))
  (services (cons*
  	     (dhcp-client-service)
	     (service openssh-service-type
		      (openssh-configuration
		       (x11-forwarding? #t)
		       (permit-root-login #t)
		       (authorized-keys
			`(
			  ("g1" ,(local-file "glc.pub"))
			  ("al" ,(local-file "glc.pub"))
			  ("root" ,(local-file "glc.pub"))))))
	     (avahi-service)
	     (ntp-service)
	     %base-services))
  (name-service-switch %mdns-host-lookup-nss))

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

[myglc2]

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

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

[Ludovic Courtès]

Hi,

George myglc2 Clemmer <myglc2@gmail.com> skribis:

> 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

I believe this is fixed by commit
b34ac8248205d64b4023412e61512dfefe44cb9e.

Thanks,
Ludo’.

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

[myglc2]

Hi  Ludo’,

On 03/18/2018 at 00:23 Ludovic Courtès writes:

> I believe this is fixed by commit
> b34ac8248205d64b4023412e61512dfefe44cb9e.

Yes thank you. That fixed it here too. - George