Am Tue, 16 Feb 2016 15:35:24 +0100 schrieb Lennart Poettering <lenn...@poettering.net>:
> On Mon, 15.02.16 21:32, Kai Krakow (hurikha...@gmail.com) wrote: > > > Am Mon, 15 Feb 2016 14:28:19 +0100 > > schrieb Lennart Poettering <lenn...@poettering.net>: > > > > > On Sun, 14.02.16 13:49, Kai Krakow (hurikha...@gmail.com) wrote: > > > > > > > Hello! > > > > > > > > I've followed the man page guide to setup mymachines name > > > > resolution in nsswitch.conf. It works. But it takes around 4-5 > > > > seconds to resolve a name. This is unexpected and cannot be > > > > used in production. > > > > > > This sounds like the LLMNR timeout done. I figure we should fix > > > the docs to suggest that "mymachines" appears before "resolve" in > > > nsswitch.conf. That should fix your issue... > > > > Apparently it doesn't fix it - although I will leave it in this > > order according to your recommendation. > > > > Is there a way to globally disable LLMNR altogether to nail it > > down? I tried setting LLMNR=false in *.network - didn't help. > > Use the LLMNR= setting in /etc/systemd/resolved.conf Yeah! *thumbsup* You da man, Lennart! Setting LLMNR to "resolve" or to "no" globally solves the problem which proves your first suspicion. Now, how can I figure out which interface is the problematic one? Do I actually need LLMNR in a simple home network? The long term is to use this in a container based hosting environment. I'm pretty sure I actually don't need LLMNR there. So I'm just curious how to "optimize" my home setup. -- Regards, Kai Replies to list-only preferred. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
