From de93ccb0dac0fe27909fcd4c216757894e9867b1 Mon Sep 17 00:00:00 2001
From: "Dustin C. Hatch" <dustin@hatch.name>
Date: Fri, 12 Aug 2022 14:35:14 -0500
Subject: [PATCH] r/systemd-resolved: Manage systemd resolver daemon

The *systemd-resolved* role/playbook ensures the *systemd-resolved*
service is enabled and running, and ensures that the `/etc/resolv.conf`
file is a symlink to the appropriate managed configuration file.
---
 roles/systemd-resolved/defaults/main.yml |  3 +++
 roles/systemd-resolved/tasks/main.yml    | 20 ++++++++++++++++++++
 systemd-resolved.yml                     |  6 ++++++
 3 files changed, 29 insertions(+)
 create mode 100644 roles/systemd-resolved/defaults/main.yml
 create mode 100644 roles/systemd-resolved/tasks/main.yml
 create mode 100644 systemd-resolved.yml

diff --git a/roles/systemd-resolved/defaults/main.yml b/roles/systemd-resolved/defaults/main.yml
new file mode 100644
index 0000000..1a5ab61
--- /dev/null
+++ b/roles/systemd-resolved/defaults/main.yml
@@ -0,0 +1,3 @@
+resolved_stub_mode: false
+resolv_conf_symlink: >-
+  /run/systemd/resolve/{% if resolved_stub_mode %}stub-{% endif%}resolv.conf
diff --git a/roles/systemd-resolved/tasks/main.yml b/roles/systemd-resolved/tasks/main.yml
new file mode 100644
index 0000000..188f4e1
--- /dev/null
+++ b/roles/systemd-resolved/tasks/main.yml
@@ -0,0 +1,20 @@
+- name: ensure systemd-resolved starts at boot
+  service:
+    name: systemd-resolved
+    enabled: true
+  tags:
+  - service
+- name: ensure systemd-resolved is running
+  service:
+    name: systemd-resolved
+    state: started
+  tags:
+  - service
+- name: ensure resolv.conf symlink is set
+  file:
+    path: /etc/resolv.conf
+    src: '{{ resolv_conf_symlink }}'
+    force: true
+    state: link
+  tags:
+  - resolvconf
diff --git a/systemd-resolved.yml b/systemd-resolved.yml
new file mode 100644
index 0000000..f2f58e6
--- /dev/null
+++ b/systemd-resolved.yml
@@ -0,0 +1,6 @@
+- hosts: all
+  roles:
+  - role: systemd-resolved
+    tags:
+    - resolved
+    - netconfig