viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: Technitium DNS IP — 10.0.20.101 → 10.0.20.201

Browse source 
Stragglers from the same drift as commit b288a59 (monorepo) / the
2026-05-22 viktorbarzin.me apex incident — the `.101` references were
left over from the NodePort exposure era. Technitium's actual MetalLB LB
IP is `.201` (in pool 10.0.20.200-220).

- architecture/vpn.md — Technitium component cell + AdGuard forwarder
  example + nslookup troubleshooting hint
- architecture/networking.md — 502 ingress troubleshooting snippet
- plans/2026-02-22-talos-linux-migration-evaluation.md — nameservers
  example
This commit is contained in:
Viktor Barzin 2026-05-23 08:53:52 +00:00
parent 68a503e29f
commit 0025511b6a
3 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/architecture/networking.md
View file

@ -416,7 +416,7 @@ Containerd on all K8s nodes uses `hosts.toml` to redirect pulls to the local cac
### Ingress Returns 502 Bad Gateway
**Symptoms**: Cloudflared tunnel is up, Traefik logs show `dial tcp: lookup <service> on 10.0.20.101:53: no such host`.
**Symptoms**: Cloudflared tunnel is up, Traefik logs show `dial tcp: lookup <service> on 10.0.20.201:53: no such host`.
**Diagnosis**: DNS resolution failed. Check:
1. Is Technitium pod running? `kubectl get pod -n technitium`

6
docs/architecture/vpn.md
View file

@ -86,7 +86,7 @@ sequenceDiagram
| Authentik | OIDC provider | K8s | SSO authentication for Headscale |
| DERP Relay | Embedded in Headscale | K8s (region 999) | Relay for NAT traversal |
| AdGuard DNS | Container | K8s | Global DNS resolver with ad-blocking |
| Technitium DNS | Container | K8s (10.0.20.101) | Internal .lan domain resolver |
| Technitium DNS | Container | K8s (10.0.20.201) | Internal .lan domain resolver |
## How It Works
@ -224,7 +224,7 @@ dns_config:
- Google: `8.8.8.8`, `8.8.4.4`
**Conditional forwarding**:
- `viktorbarzin.lan` → `10.0.20.101` (Technitium)
- `viktorbarzin.lan` → `10.0.20.201` (Technitium)
**Ad-blocking lists**:
- AdGuard DNS filter
@ -377,7 +377,7 @@ dns_config:
**Steps**:
1. Verify AdGuard is running: `kubectl get pod -n adguard`
2. Check AdGuard conditional forwarding: Query AdGuard directly: `nslookup nextcloud.viktorbarzin.lan <adguard-ip>`
3. Check Technitium: `nslookup nextcloud.viktorbarzin.lan 10.0.20.101`
3. Check Technitium: `nslookup nextcloud.viktorbarzin.lan 10.0.20.201`
**Common causes**:
1. **AdGuard not forwarding .lan**: Conditional forwarding rule missing or misconfigured.

2
docs/plans/2026-02-22-talos-linux-migration-evaluation.md
View file

@ -106,7 +106,7 @@ machine:
- network: 0.0.0.0/0
gateway: 10.0.20.1
nameservers:
- 10.0.20.101 # Technitium
- 10.0.20.201 # Technitium
- 1.1.1.1
registries:
mirrors: