** Changed in: avahi
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow response
To manage notifications about this bug go to:
** Bug watch added: Debian Bug tracker #905894
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905894
** Also affects: avahi via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905894
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
The problem still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow response
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nss-mdns (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
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
This output is generally quite confusing.
Can you try remove the "search www.tendawifi.com" and see how it
differs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow
ideally using mdns4_minimal specifically (or i guess, both, but
generally not recommended to use mdns4 in most cases)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow
And here is the output with the default config:
# 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:
Here is the output, it does not work again even with the new config i am
totally confused:
rumen@sirius:~$ time getent hosts indigosky.local
192.168.235.1 indigosky.local
real0m10,121s
user0m0,004s
sys 0m0,000s
rumen@sirius:~$ time host indigosky.local
indigosky.local has address
Can you please confirm
(1) The timing of "getent hosts indigosky.local", "host indigosky.local",
"nslookup indigosky.local" and "nslookup indigosky.local 192.168.235.1" all
done at the same time (mainly adding the direct lookup through the server,
wondering if nslookup is doing something weird
Hi again,
This changes to the system config seems to partially fix the problem:
rumen@sirius:~/indigo_imager.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,
Hi, here is the information you need. By the way today the timeouts are
much worse but still multiple of 5s...
rumen@sirius:~/indigo_imager.git$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
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
** Project changed: launchpad => nss-mdns (Ubuntu)
** Tags removed: libnss-mdns
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow response
To manage notifications
14 matches
Mail list logo
