Tried that, and it started using the DHCP-provided search path (yay!). Setting the search path in NetworkManager (which is responsible for the interface in question) works, ie. honors the search path and doesn't break resolving for those domains, with both single and multiple search paths:
[ipv4] dns-search=disy.inf.uni-konstanz.de;inf.uni-konstanz.de;uni-konstanz.de method=auto [ipv6] addr-gen-mode=stable-privacy dns-search=disy.inf.uni-konstanz.de;inf.uni-konstanz.de;uni-konstanz.de method=auto Having to do this for each connection and for both IPv4 and IPv6 sucks, but it's better than not having a search path. Trying to set the search path to Domains=ubuntu.com globally in resolved.conf still breaks ubuntu.com, of course. Out of curiosity, I then put this in resolved.conf: Domains=uni-konstanz.de inf.uni-konstanz.de disy.inf.uni-konstanz.de ubuntu.com This works for the domains listed in the interface, honoring the search path and correctly resolving both short (git) and long (git.uni- konstanz.de) domains. But it breaks resolution completely for ubuntu.com and subdomains. So: Does systemd-resolved need to have a network interface "associated" with each search domain?? This is very much not how DNS works but it's a boundary case that might be easy to get wrong. (This is all on the 17.10 VM, and with resolved.conf empty apart from [Resolve] and the Domains= line, where mentioned.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714803 Title: Search list in resolv.conf breaks resolving for that domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs