[Bug 1888047] Re: libnss-mdns slow response
Rumen
1888047 at bugs.launchpad.net
Thu Jul 23 09:29:42 UTC 2020
It is auto generated.
On thisnetwork where I am now there is no such entry:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 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-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
but the problem is the same.
On the bright side this changed the client and now it caches the
resolved ip and connects with ip not the name... but this is an ugly
patch and it fixes only one service. All other services are slow. That
is interesting is that using mdns4 with mdns.allow fixes the issue
sometimes not always. and sometimes it is even slower...
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nss-mdns in Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow response
Status in nss-mdns package in Ubuntu:
New
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 at sirius:~/indigo.git$ time nslookup sirius.local
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:484a:7307:cf6
real 0m5,224s
user 0m0,008s
sys 0m0,008s
rumen at sirius:~/indigo.git$ time nslookup dir.bg
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 at sirius:~/indigo.git$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 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-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
search www.tendawifi.com
rumen at sirius:~/indigo.git$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `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 at sirius:~/indigo.git$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1888047/+subscriptions
More information about the foundations-bugs
mailing list