Arch Linux

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!
Tasklist

FS#54477 - [systemd] systemd-resolved.service should start before network-online.target and nss-lookup.target

Attached to Project: Arch Linux
Opened by Pascal Ernster (hardfalcon) - Friday, 16 June 2017, 14:56 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 02 December 2017, 16:35 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Please backport the following bugfix from upstream for both systemd 232 and 233:

https://github.com/systemd/systemd/commit/3e06055500755053050620a45236ef606507e1bd

This would allow units requiring a working DNS resolver to use After=nss-lookup.target as specified in the systemd documentation:

https://www.freedesktop.org/software/systemd/man/systemd.special.html#nss-lookup.target

A common example would be nginx, where the shoddy OCSP stapling support fails when DNS is not working at the time the nginx daemon is started (I'll file a separate bug for this).
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 02 December 2017, 16:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd v234
Comment by Stefan (steinwanderer) - Friday, 07 July 2017, 13:37 GMT
systemd-resolved defaults to "linux", if not connected to a network and with no static hostname set. Determining the hostname of the machine will then result always in "linux", until the service is restarted (after connected to a network). I'm facing this problem with NetworkManager currently.

Loading...