From b8a7de0282ed299ec0897d00d0743bcf58492063 Mon Sep 17 00:00:00 2001 From: Yu Watanabe Date: Fri, 21 Apr 2017 18:21:17 +0900 Subject: [PATCH] units: systemd-resolved should start before network-online.target and nss-lookup.target (#5691) systemd-resolved provides 1. local API via NSS and D-Bus 2. kind of a local "DNS proxy" through its stub listener The 1st item should be started before nss-lookup.target. The 2nd item should be started before network-online.target, because if the networking works in general, then DNS (and DNS proxy) should too. Fixes #5650 (cherry picked from commit 3e06055500755053050620a45236ef606507e1bd) --- units/systemd-resolved.service.m4.in | 2 ++ 1 file changed, 2 insertions(+) diff --git a/units/systemd-resolved.service.m4.in b/units/systemd-resolved.service.m4.in index d3b8f81601..41f696abe5 100644 --- a/units/systemd-resolved.service.m4.in +++ b/units/systemd-resolved.service.m4.in @@ -12,6 +12,8 @@ Documentation=http://www.freedesktop.org/wiki/Software/systemd/resolved Documentation=http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers Documentation=http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients After=systemd-networkd.service network.target +Before=network-online.target nss-lookup.target +Wants=nss-lookup.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name.