unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: George myglc2 Clemmer <myglc2@gmail.com>
To: 30613@debbugs.gnu.org
Subject: bug#30613: 'avahi-resolve <host>.local' works but 'ssh <host>.local' fails w/ "Name or service not known"
Date: Mon, 26 Feb 2018 09:09:18 -0500	[thread overview]
Message-ID: <86fu5nalm9.fsf@gmail.com> (raw)

[-- 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))

             reply	other threads:[~2018-02-26 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 14:09 George myglc2 Clemmer [this message]
2018-02-27 19:23 ` bug#30613: 'avahi-resolve <host>.local' works but 'ssh <host>.local' fails w/ "Name or service not known" myglc2
2018-03-17 23:23 ` Ludovic Courtès
2018-03-18  1:49   ` myglc2

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86fu5nalm9.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=30613@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).