Vezpi/Blog
1
0
Fork 0
Code Issues Pull Requests Actions Wiki Activity

Auto-update blog content from Obsidian: 2025-05-20 09:54:36
All checks were successful
Deploy / Deploy (push) Successful in 4s
Details

Browse Source
This commit is contained in:
Gitea Actions 2025-05-20 09:54:36 +00:00
parent a9ee82130a
commit ffcf6974a3
1 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
content/page/homelab/index.md
View File

@ -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.