On Sat, Jan 27, 2018 at 01:55:07PM -0000, Jonathan Kamens wrote: > I uninstalled libnss-resolve and the problem persists: > > $ sudo apt-get remove libnss-resolve > ... > $ sudo systemd-resolve --flush-caches > $ host jik5 > Host jik5.quantopian.com not found: 2(SERVFAIL) > $ cat /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > # 127.0.0.53 is the systemd-resolved stub resolver. > # run "systemd-resolve --status" to see details about the actual nameservers.
> nameserver 127.0.0.53 > search quantopian.com kamens.us > $ Ok, then I will need some help understanding how to reproduce this problem, since simply inserting quantopian.com in the search list in /etc/resolv.conf on an Ubuntu 17.10 system with default settings is insufficient to reproduce the problem you describe. Have you also changed the default DNSSEC settings for systemd-resolved in /etc/systemd/resolved.conf ? What is the complete output of 'systemd-resolve --status'? > Note that "Just don't use libnss-resolve" wouldn't be a very good answer > to this problem even if it worked, because things like openvpn-systemd- > resolved, which I use, depend on it. Well, that's a bug in the openvpn-systemd-resolved package, it should not depend on libnss-resolve for what it does. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717015 Title: libc resolver stops searching domain search list after getting back NSEC record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717015/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
