This bug was fixed in the package systemd - 242-7ubuntu3
---------------
systemd (242-7ubuntu3) eoan; urgency=medium
* Fix using domain set by DHCP as search domain (LP: #1846509)
File:
debian/patches/network-do-not-use-ordered_set_printf-for-DOMAINS-or-ROUT.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=210e1f979d27c7eeaff87c0f16240ec415d0a043
* Add test for UseDomains=true default setting
File:
debian/patches/debian/Ubuntu-test-UseDomains-true-default-setting.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a2c01a848969d3c5cbe67b3c26ff641e367edba7
* Refresh patches
-- Balint Reczey <[email protected]> Fri, 11 Oct 2019 16:19:01 +0200
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1846509
Title:
networkd doesn't take into account search domain received by DHCP
Status in systemd package in Ubuntu:
Fix Released
Bug description:
Hi,
When starting a virtual machine with the following command line :
qemu-system-x86_64 -k fr -m 1024 -smp 1 -display none \
-rtc base=utc -daemonize \
-drive if=none,file="my.qcow2",id=hd0 \
-device virtio-blk,drive=hd0 \
-netdev
user,id=user.0,hostfwd=tcp::32768-:22,dnssearch=dns.companyname.com \
-device virtio-net,netdev=user.0,mac=de:ad:de:01:02:03 \
-vga none
The system-network doesn't take into account search domain and then
search fail.
The same setup does work when using NetworkManager.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846509/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
