1) one should not manually adjust search domains in /etc/resolv.conf
2) systemd-resolved should learn about search domains
- for example, set search domains in /etc/systemd/resolved.conf if
nothing sets them on per link basis vai resolved dbus api or
networkd.network files.
3) /etc/resolv.conf should be a symlink to
../run/systemd/resolve/stub-resolv.conf
4) ../run/systemd/resolve/stub-resolv.conf should be dynamically updated by
resolved to contain the correct search domains
5) resolved does not send DNSSEC info to clients that do not support DNSSEC nor
requested a DNSSEC response
6) if you expect DNSSEC validation from responses resolved provides, please
manually enable DNSSEC in /etc/systemd/resolved.conf and all the relevant links
via systemd-resolve cmdline tool (if not managed vai networkd.network units)
** 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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
