Public bug reported:
(See also libnss-resolve:amd64 231-9ubuntu1 amd64 nss module to
resolve names via systemd-resolved)
# fresh install of yakkety
mtearle@liberation:/etc$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.10
Release: 16.10
Codename: yakkety
# package details
mtearle@liberation:~$ apt-cache policy libnss-resolve
libnss-resolve:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
*** 231-9ubuntu1 500
500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64
Packages
100 /var/lib/dpkg/status
231-9git1 500
500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages
mtearle@liberation:~$ apt-cache policy systemd
systemd:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
*** 231-9ubuntu1 500
500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64
Packages
100 /var/lib/dpkg/status
231-9git1 500
500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages
# attempt to ping VM elsewhere on network with mDNS hostname
mtearle@liberation:/etc$ ping bazzavan.local
ping: bazzavan.local: Name or service not known
# can find both ipv4 and ipv6 addresses for the host
mtearle@liberation:/etc$ avahi-resolve-host-name bazzavan.local
bazzavan.local fe80::a00:27ff:fea5:3f51
mtearle@liberation:/etc$ avahi-resolve-host-name -4 bazzavan.local
bazzavan.local 172.16.44.48
# can ping it
mtearle@liberation:/etc$ ping -c 1 172.16.44.48
PING 172.16.44.48 (172.16.44.48) 56(84) bytes of data.
64 bytes from 172.16.44.48: icmp_seq=1 ttl=64 time=0.265 ms
--- 172.16.44.48 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.265/0.265/0.265/0.000 ms
# original ordering
mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf
hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return]
dns
# go away and edit /etc/nsswitch.conf
# change ordering of resolve and mdns4_minimal
mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return]
dns
# check mdns lookups now work, and it now pings
mtearle@liberation:/etc$ ping -c 1 bazzavan.local
PING bazzavan.local (172.16.44.48) 56(84) bytes of data.
64 bytes from 172.16.44.48 (172.16.44.48): icmp_seq=1 ttl=64 time=0.161 ms
--- bazzavan.local ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.161/0.161/0.161/0.000 ms
# check libnss-resolve is still doing its thing
mtearle@liberation:/etc$ ping -c 1 localhost.localdomain
PING localhost.localdomain(localhost (::1%1)) 56 data bytes
64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.016 ms
--- localhost.localdomain ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.016/0.016/0.016/0.000 ms
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1641328
Title:
Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes
mDNS lookups to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641328/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
