On Mo, 06.08.18 17:53, Sergey Zolotorev (sergey.zolotorev@xxxxxxxxx) wrote: > I'm trying to understand what is wrong (or is there a bug in > systemd-resolved) with my systemd-resolved configuration (I use > NetworkManager to set up interfaces). systemd-resolved does not resolve > .local names and always forwards them to external DNS. > > Build: > > $ systemctl --version > systemd 239 > +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP > +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN > +PCRE2 default-hierarchy=hybrid > > Settings: > > $ resolvectl > Global > ... > MulticastDNS setting: yes > ... > > Link 3 (wlp4s0) > Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6 > LLMNR setting: yes > MulticastDNS setting: resolve > DNSOverTLS setting: no > DNSSEC setting: no > DNSSEC supported: no > Current DNS Server: 192.168.1.1 > DNS Servers: 192.168.1.1 > DNS Domain: ~. This last line is key: it means all names are passed to this dns server, including .local. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel