From ead70c9ef340fd494e581073caf89ca5d06d4cbf Mon Sep 17 00:00:00 2001 From: "tom.jampen" Date: Tue, 21 Oct 2025 14:43:39 +0000 Subject: [PATCH 1/2] chore: Adding meeting attendees and background info --- infrastructure/acme.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/infrastructure/acme.md b/infrastructure/acme.md index 929f431..ef8357f 100644 --- a/infrastructure/acme.md +++ b/infrastructure/acme.md @@ -10,6 +10,18 @@ We agreed to use **ACME DNS-01 challenges** for issuing certificates for **both - Keep **low TTLs** (e.g., 60-120s) on both CNAME and TXT records to speed up renewals. - Restrict write access to the challenge zone to the ACME automation only. +## Meetings +- 05.08.2025: Bert-Jan Fikse, Tobias Schaller, Tobias Wüst, Tom Jampen (inital version) + +## Background +The following article explains how DNS-01 challenges can be effectively used to issue Let's Encrypt certificates for servers with internal IP addresses: + +- https://lists.bfh.science/pipermail/bfh-linux-announce/2021-September/000134.html + +The following manpage explains important implementation details for correctly handling DNS-01 challenges: + +- https://sources.debian.org/src/open-infrastructure-service-tools/20250626-2/dehydrated/share/man/dehydrated-nsupdate.1.rst#L20 + ## Reference Design **Dedicated zone:** `_acme.digitalboard.ch` From 4d5a1bc5ea018619d5f23a89f1020c38cfd2773b Mon Sep 17 00:00:00 2001 From: "tom.jampen" Date: Thu, 11 Dec 2025 14:25:40 +0000 Subject: [PATCH 2/2] Update infrastructure/ipv6.md --- infrastructure/ipv6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/infrastructure/ipv6.md b/infrastructure/ipv6.md index ef58ac9..1c80bd9 100644 --- a/infrastructure/ipv6.md +++ b/infrastructure/ipv6.md @@ -6,7 +6,7 @@ We agreed to setup dual stack by default as IPv6 is essential for modern IT infr ## Decisions - Use **Dual Stack** (IPv4 and IPv6 addresses) - Rely on **DNS names instead of raw IP addresses** -- **Each school is responsible for its DNS records** and must them for IPv4/IPv6 (including CNAME records for ACME) +- **Each school is responsible for its DNS records** and must manage them for IPv4/IPv6 (including CNAME records for ACME) - The Digitalboard provides an optional service (dynamic DNS zone for acme challenge responses) as described in the [ACME documentation](./acme.md) - The Digitalboard might act as a RIPE customer and provide a `/32` or `/48` IPv6 network for interested schools