From a1b51f97f5cb1b117951bc5ab9507474e41f53d8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Julian-Samuel=20Geb=C3=BChr?= <julian-samuel@gebuehr.net>
Date: Wed, 15 Mar 2023 11:39:36 +0100
Subject: [PATCH] docs: Add DNS documentation

---
 docs/configuring-dns.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 docs/configuring-dns.md

diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md
new file mode 100644
index 0000000..754d7b0
--- /dev/null
+++ b/docs/configuring-dns.md
@@ -0,0 +1,19 @@
+# Configuring DNS
+
+To reach your services, you'd need to do some DNS configuration.
+
+## DNS settings example
+
+The DNS setup is dependent on which services you want to activate. You need t oset the first entry and an entry for each
+service you activate that needs a (sub-)domain. Feel free to adjust the host to you liking (you can even use a separate domain).
+
+| Service     | Type  | Host                   | Target              |
+|-------------|-------|------------------------|---------------------|
+| -           | A     | `example.com`          | `IP of your server` |
+| Radicale    | CNAME | `calendar.example.com` | `example.com`       |
+| Miniflux    | CNAME | `feed.example.com`     | `example.com`       |
+| Uptime-kuma | CNAME | `status.example.com`   | `example.com`       |
+
+Be mindful as to how long it will take for the DNS records to propagate.
+
+When you're done configuring DNS, proceed to [Configuring the playbook](configuring-playbook.md).