From ffcf6974a31d38963ecfeaeaf14b6fd59a17a0a3 Mon Sep 17 00:00:00 2001 From: Gitea Actions Date: Tue, 20 May 2025 09:54:36 +0000 Subject: [PATCH] Auto-update blog content from Obsidian: 2025-05-20 09:54:36 --- content/page/homelab/index.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/content/page/homelab/index.md b/content/page/homelab/index.md index 873b2e5..f6bdead 100644 --- a/content/page/homelab/index.md +++ b/content/page/homelab/index.md @@ -160,15 +160,10 @@ Each VLAN has its own DHCP pool managed by OPNsense, excepted the Heartbeat and DNS is structured in two layers within OPNsense: - ADguard Home: ads and trackers filters, serves every client on the network over plain DNS on port 53 -- Unbound DNS: recursive DNS, serves only the ADguard Home DNS service locally +- Unbound DNS: recursive DNS, serves only the ADguard Home DNS service locally +#### Reverse Proxy -This setup balances privacy, performance, and control over DNS traffic. - ---- - -#### **Reverse Proxy: Caddy and Traefik** - -**Caddy** is installed as an OPNsense plugin to handle external requests and SSL termination. It forwards traffic to a main VM running **Traefik**, which routes requests internally to various services. +**Caddy** is installed as an OPNsense plugin to handle web requests. It forwards traffic to **Traefik**, which routes requests internally to various services. This two-layer proxy setup keeps SSL management centralized in Caddy while maintaining flexible internal routing through Traefik.