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 -- 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: https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1888047/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
