Auto-update blog content from Obsidian: 2025-05-20 09:54:36
All checks were successful
Deploy / Deploy (push) Successful in 4s
All checks were successful
Deploy / Deploy (push) Successful in 4s
This commit is contained in:
parent
a9ee82130a
commit
ffcf6974a3
@ -161,14 +161,9 @@ 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
|
||||
#### 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.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user