Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40682 - systemd-resolved (in 213) does not keep the domain name of dhcp reply
Attached to Project:
Arch Linux
Opened by Radek Podgorny (rpodgorny) - Wednesday, 04 June 2014, 12:40 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 12:56 GMT
Opened by Radek Podgorny (rpodgorny) - Wednesday, 04 June 2014, 12:40 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 12:56 GMT
|
Detailsin new systemd (212 -> 213), part of the functionality has been moved from systemd-networkd to systemd-resolved.
unfortunately, it seems something got lost along the way since the domain part of dhcp reply is not being honored and does not get written to /run/systemd/network/resolv.conf. the nameserver part works correctly. this is probably an upstream bug but trying here first to be sure. p.s.: the sources indicate there really is no support for domain part in systemd-resolved. -> http://cgit.freedesktop.org/systemd/systemd/tree/src/resolve/resolved-manager.c |
This task depends upon
Closed by Dave Reisner (falconindy)
Wednesday, 04 June 2014, 12:56 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#40681
Wednesday, 04 June 2014, 12:56 GMT
Reason for closing: Duplicate
Additional comments about closing: