2e6e0d6e80
Placing mdns after dns in the host database resolution can cause
unintuitive failures for users without nss-mdns or mDNSResponder. When
looking up an invalid host, having order "dns mdns" will cause a dns
"notfound" result to fall through to mdns, which will yield
"unavailable" for users without an mdns provider. This causes clients
like ssh to report "Device or resource busy" rather than a more
meaningful message to indicate that the hostname is not valid. Flipping
back to order "mdns dns" will case an "unavailable" mdns result to fall
through to dns, which then returns "notfound" that clients interpret as
expected.
Because both mDNSResponder and nss-mdns offer a generic mdns provider.
The mdns4 and mdns4_minimal providers offered by nss-mdns are subsets of
the generic mdns provider, so there is no value in restoring the
original "mdns mdns4_minimal mdns4" ordering (in fact, this may have
caused failed mdns lookups to be repeated three times). All have been
coalesced into the single mdns provider.
This (partially) reverts commit cc11e17fab.
15 lines
216 B
Text
15 lines
216 B
Text
# /etc/nsswitch.conf
|
|
#
|
|
# See nsswitch.conf(5) for information.
|
|
#
|
|
passwd: files
|
|
group: files
|
|
shadow: files
|
|
|
|
hosts: files mdns dns
|
|
networks: files
|
|
|
|
protocols: files
|
|
services: files
|
|
ethers: files
|
|
rpc: files
|