IIRC what could be happening is that the additional timeout introduced by systemd-resolved first doing the newly implemented LLMNR lookup (which fails if not implemented by any device) causes some network tools to not even try doing a DNS lookup using the DHCP- or user-supplied DNS search domain suffixes.
The second invocation then maybe finds a cached result which is however invalidated after some time - thus the varying or seemingly random results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699660 Title: systemd-resolve breaks resolution of local network hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
