As of Ubuntu 17.10, libnss-resolve is not installed by default. Is this
problem reproducible when libnss-resolve is removed, using the resolved
stub resolver instead of the NSS module?
I don't appear to be able to confirm the original behavior against the
quantopian.com domain (I don't get any NSEC responses), and don't have
another DNSSEC-enabled domain to hand that I can test with.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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