*** This bug is a duplicate of bug 1641328 ***
https://bugs.launchpad.net/bugs/1641328
** This bug has been marked a duplicate of bug 1641328
Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS
lookups to fail -- breaks network printing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1650555
Title:
nsswitch.conf configuration doesn't work with mdns hosts
Status in systemd package in Ubuntu:
Confirmed
Bug description:
On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts
doesn't work anymore (it used to in xenial)
I can resolve names with avahi-resolve but ssh,ping,etc. fail to
resolve.
After some digging I found out that what's causing it is the "resolve"
option in /etc/nsswitch.conf:
hosts: files resolve [!UNAVAIL=return] mdns4_minimal
[NOTFOUND=return] dns
Changing it to
hosts: files mdns4_minimal [NOTFOUND=return] dns
(as it was on xenial) makes mDNS work again.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libnss-resolve 231-9ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Dec 16 15:16:38 2016
InstallationDate: Installed on 2016-10-22 (54 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650555/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
