On 10 October 2017 at 15:39, Matthias Fratz <[email protected]> wrote: > Our DHCP server delivers a search domain (inf.uni-konstanz.de) as well. > This isn't enough to trigger the bug for me, though, at least on 17.04. > (systemd-resolve doesn't actually USE the search path, so merkur236.inf > .uni-konstanz.de works but merkur236 doesn't, but that's a different > problem.) > > What does trigger the bug on 17.04 is manually configuring a search > path, like it seems the original reporter did: > > $ cat /etc/resolvconf/resolv.conf.d/base > search disy.inf.uni-konstanz.de inf.uni-konstanz.de uni-konstanz.de > > At some point this gets copied to /etc/resolv.conf. After a "service > systemd-resolved restart", resolution is broken for those domains until > I remove the search path and restart systemd-resolved again. > > I couldn't yet reproduce this on 17.10 because restarting systemd- > resolved overwrites /etc/resolv.conf. Where is the right place to > configure a search path on 17.10? I don't see it anywhere in the GUI and > I'm not sure whether /etc/systemd/resolved.conf is the right place. >
The really correct way on 17.10 is to stop using ifupdown and stop using resolvconf and stop using libnss-resolve $ upgrade to 17.10 $ sudo netplan ifupdown-migrate $ sudo apt remove --purge ifupdown $ sudo apt remove --purge resolvconf $ sudo apt remove --purge libnss-resolve $ sudo reboot At this point, /etc/resolv.conf will start pointing at a resolved managed stub-resolv.conf file which will automatically pick up and use DHCP provided domains. Further domains configuration can be provided by adjusting /etc/netplan/*.yaml file, or by adjusting systemd-networkd drop-ins, or by adjusting /etc/systemd/resolved.conf. It's best for the search domains to be provided over DHCP instead of hardcoding the config in files on disk. You may also choose to use networks: backend: network-manager in the netplan.yaml file, if you wish to use NetworkManager instead of the networkd as the networking management backend. Search domains specified in resolvconf syntax / directly in the /etc/resolv.conf will not be read/used by resolved stub resolver, and will not be used by libnss-resolve, thus if you wish to keep using resolvconf/ifupdown one will need to provide the search domain to resolved separately. Best way to do that would be via /etc/systemd/resolved.conf. -- Regards, Dimitri. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
