[xenial] search domains in networkd do not get propagated to resolvconf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Search domains specified in networkd do not get propagated to /etc/resolv.conf via resolved in xenial, as systemd-
This was uncovered while working on adding nameserver support to netplan, in bug 1626617. To fully support netplan/networkd in xenial we should fix this.
SRU TEST CASE:
* Start a xenial VM or container, and create a networkd interface with a DNS server and search domain:
$ cat /etc/systemd/
[NetDev]
Name=foo
Kind=dummy
$ cat /etc/systemd/
[Match]
Name=foo
[Network]
DNS=1.2.3.4
Domains=kitchen cellar
* sudo systemctl restart systemd-networkd
* cat /etc/resolv.conf
resolv.conf should have "nameserver 1.2.3.4" (unless there already are three nameservers), but with the current xenial version it lacks "search kitchen cellar". With the -proposed version, both entries should be there.
REGRESSION POTENTIAL: This makes the shell hack of systemd-
Changed in systemd (Ubuntu): | |
status: | New → Invalid |
Changed in systemd (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Martin Pitt (pitti) |
description: | updated |
Fixed in https:/ /anonscm. debian. org/cgit/ pkg-systemd/ systemd. git/commit/ ?h=ubuntu- xenial& id=7168785fb155