libnss-mdns slow response
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Avahi |
New
|
Unknown
|
|||
nss-mdns (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
mdns responses are very slow which degrades the preformance of some services in my lan due to this long delay. Please see the log below:
rumen@sirius:
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: sirius.local
Address: 192.168.11.109
Name: sirius.local
Address: 172.17.0.1
Name: sirius.local
Address: fe80::7afb:
real 0m5,224s
user 0m0,008s
sys 0m0,008s
rumen@sirius:
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: dir.bg
Address: 194.145.63.12
real 0m0,035s
user 0m0,012s
sys 0m0,006s
rumen@sirius:
# This file is managed by man:systemd-
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
search www.tendawifi.com
rumen@sirius:
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-
# `info libc "Name Service Switch"' for information about this file.
passwd: files systemd
group: files systemd
shadow: files
gshadow: files
hosts: files mdns4_minimal [NOTFOUND=return] dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
rumen@sirius:
affects: | launchpad → nss-mdns (Ubuntu) |
tags: | removed: libnss-mdns |
Changed in avahi: | |
status: | Unknown → New |
Rumen,
When you use 'nslookup' it should go directly to using the DNS server (127.0.0.53 [which is systemd-resolved]) which typically bypasses libnss-mdns but also typically doesn't have this 5 second delay (which avahi can have in some configurations). Seems most likely the 5 second delay is coming from inside systemd-resolved for some reason.
The best way to test with "NSS" is to use "getent hosts DOMAIN"
Could you please confirm the output of the following commands:
lsb_release -a
dpkg -l libnss-mdns
systemctl status avahi-daemon
time getent hosts sirius.local
time nslookup sirius.local # just to verify the problem still exists at the same time we do the above test
systemd-resolve --status --no-pager
- attach the file /etc/systemd/ resolved. conf