diff --git a/data/release-notes/enterprise-server/3-11/14.yml b/data/release-notes/enterprise-server/3-11/14.yml
index 51b639d76a2c..c738cc36025e 100644
--- a/data/release-notes/enterprise-server/3-11/14.yml
+++ b/data/release-notes/enterprise-server/3-11/14.yml
@@ -101,3 +101,7 @@ sections:
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
     - |
       Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
+    - |
+      {% data reusables.release-notes.2024-08-resolvconf-wont-start %}
+
+      [Updated: 2024-08-26]
diff --git a/data/release-notes/enterprise-server/3-12/8.yml b/data/release-notes/enterprise-server/3-12/8.yml
index 9d3ca60503e5..d3683b583e77 100644
--- a/data/release-notes/enterprise-server/3-12/8.yml
+++ b/data/release-notes/enterprise-server/3-12/8.yml
@@ -109,3 +109,7 @@ sections:
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
     - |
       Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
+    - |
+      {% data reusables.release-notes.2024-08-resolvconf-wont-start %}
+
+      [Updated: 2024-08-26]
diff --git a/data/release-notes/enterprise-server/3-13/3.yml b/data/release-notes/enterprise-server/3-13/3.yml
index 354bdb8c310c..621d65e59034 100644
--- a/data/release-notes/enterprise-server/3-13/3.yml
+++ b/data/release-notes/enterprise-server/3-13/3.yml
@@ -123,3 +123,7 @@ sections:
       Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
     - |
       Instance setup in AWS with IMDSv2 enforced fails if no public IP is present.
+    - |
+      {% data reusables.release-notes.2024-08-resolvconf-wont-start %}
+
+      [Updated: 2024-08-26]
diff --git a/data/reusables/release-notes/.2024-08-resolvconf-wont-start.md.swp b/data/reusables/release-notes/.2024-08-resolvconf-wont-start.md.swp
new file mode 100644
index 000000000000..ad1d97a73f96
Binary files /dev/null and b/data/reusables/release-notes/.2024-08-resolvconf-wont-start.md.swp differ
diff --git a/data/reusables/release-notes/2024-08-resolvconf-wont-start.md b/data/reusables/release-notes/2024-08-resolvconf-wont-start.md
new file mode 100644
index 000000000000..5b8a6540e1d0
--- /dev/null
+++ b/data/reusables/release-notes/2024-08-resolvconf-wont-start.md
@@ -0,0 +1,16 @@
+On boot, the `resolvconf` service may fail to start because the `/run/resolvconf` directory does not exist when the service attempts to `touch` a file there, with the error:
+
+```shell
+/bin/touch: cannot touch '/run/resolvconf/postponed-update': No such file or directory
+```
+
+If this occurs, workaround this issue with the following commands — this change will persist on reboots, but not upgrades:
+
+```shell
+sudo sed -i.bak \
+'/\[Service\]/a ExecStartPre\=\/bin\/mkdir \-p \/run\/resolvconf' \
+/etc/systemd/system/resolvconf.service.d/local.conf
+
+sudo systemctl daemon-reload
+sudo systemctl start resolvconf 
+```