| Server IP : 185.11.201.71 / Your IP : 192.168.7.18 Web Server : Apache/2.4.29 (Ubuntu) System : Linux tech-virtual-machine 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 User : tech ( 1000) PHP Version : 7.4.28 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/libnss-mdns/ |
Upload File : |
Packages automagically modifies /etc/nsswitch.conf
--------------------------------------------------
Previously the base-files package shipped /etc/nsswitch.conf and specified:
hosts: files dns mdns
However, due to bug#351990, this is no longer the case. /etc/nsswitch.conf
is now generated post-installation. Upon installation of nss-mdns, if the
strings 'mdns', 'mdns_minimal', 'mdns4', 'mdns4_minimal', 'mdns6' or
'mdns6_minimal' appear on the hosts line, your /etc/nsswitch.conf file
will not be updated, otherwise it will updated to match the upstream
recommended configuration which usually looks like:
hosts: files mdns4_minimal [NOTFOUND=return] dns
Other possible configurations
-----------------------------
In versions older than 0.10-4 we used this configuration:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
This looks in mDNS whenever a non-link-local address does not have a PTR
(reverse DNS) record in DNS. If the host with that address is local
and available in mDNS, this means it becomes reverse-resolvable, but if
the host with that address is not local, it causes a 5 second delay,
so this is no longer enabled by default. If a local administrator wishes
to reinstate mdns4, they can do so.
Sites with a .local DNS zone
----------------------------
Making nss-mdns authoritative for .local breaks resolution on networks
where .local is a real domain name. To workaround this, avahi-daemon
should be restarted when the DNS settings change (for example via
resolvconf and dhclient hooks) and disable itself when a SOA for the
.local zone is found. This is not currently implemented at the time of
writing, but should soon be.
See also this excellent summary on the upstream website:
<http://avahi.org/wiki/AvahiAndUnicastDotLocal>