From 37adb410a2b62716b666dbf8359edf8a6546ff94 Mon Sep 17 00:00:00 2001 From: Nick Rosbrook Date: Fri, 24 Apr 2026 09:38:42 -0400 Subject: [PATCH] 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. --- units/systemd-networkd-resolve-hook.socket | 1 + 1 file changed, 1 insertion(+) diff --git a/units/systemd-networkd-resolve-hook.socket b/units/systemd-networkd-resolve-hook.socket index 3c11b8e8de..8a724bbc0c 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