From: Nick Rosbrook Date: Fri, 24 Apr 2026 13:38:42 +0000 (-0400) Subject: units: order networkd resolve hook After=network-pre.target X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=37adb410a2b62716b666dbf8359edf8a6546ff94;p=thirdparty%2Fsystemd.git units: order networkd resolve hook After=network-pre.target Without this, the socket is available well before systemd-networkd.service is able to start, because of its own After=network-pre.target ordering. Then, if resolved handles queries before network-pre.target, it will hang waiting for networkd to reply to hook queries. This is currently happening in the wild with cloud-init. --- diff --git a/units/systemd-networkd-resolve-hook.socket b/units/systemd-networkd-resolve-hook.socket index 3c11b8e8de1..8a724bbc0c0 100644 --- a/units/systemd-networkd-resolve-hook.socket +++ b/units/systemd-networkd-resolve-hook.socket @@ -12,6 +12,7 @@ Description=Network Management Resolve Hook Socket Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no +After=network-pre.target Before=sockets.target shutdown.target Conflicts=shutdown.target