Update DNS to Quad9 DoH, add port utilization diagrams
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful

- Both AdGuard instances now use Quad9 DoH (dns.quad9.net)
- Bootstrap DNS: 9.9.9.9, 149.112.112.112
- New 02-PORT-UTILIZATION.md with ASCII diagrams for all devices
- Fixed Tailscale container DNS and route configuration

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-25 19:12:35 +02:00
parent 4f5f9e786d
commit ec75bee323
3 changed files with 217 additions and 8 deletions

View File

@@ -43,9 +43,9 @@ Single DNS endpoint for both internal and external clients with ad blocking and
│ ▼ │
│ Upstream DNS │
│ ┌──────────────────┐ │
│ │ 192.168.31.4 │ ◄── Unraid AdGuard (primary)
│ │ 8.8.8.8 │ ◄── Google (fallback)
│ │ 1.1.1.1 │ ◄── Cloudflare (fallback)
│ │ Quad9 DoH │ ◄── dns.quad9.net/dns-query
│ │ 9.9.9.9 │ ◄── Quad9 bootstrap
│ │ 149.112.112.112 │ ◄── Quad9 secondary
│ └──────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
@@ -189,13 +189,13 @@ chain=forward action=accept src-address=172.17.0.0/24
- **Web UI:** http://192.168.31.1:3000
### Upstream DNS
1. 192.168.31.4 (Unraid AdGuard - primary, has filter lists)
2. 8.8.8.8 (Google - fallback)
3. 1.1.1.1 (Cloudflare - fallback)
1. https://dns.quad9.net/dns-query (Quad9 DoH - malware blocking)
2. 9.9.9.9 (Quad9 bootstrap)
3. 149.112.112.112 (Quad9 bootstrap secondary)
### Bootstrap DNS
- 8.8.8.8
- 1.1.1.1
- 9.9.9.9
- 149.112.112.112
## Usage