add: Internal DNS for kavcorp.com domains via Pi-hole
- Added *.kavcorp.com DNS entries pointing to Traefik (10.4.2.10) - Internal clients can use https://jellyfin.kavcorp.com with valid certs - Same URLs work internally and externally, no port numbers needed - Also added Traefik internal entrypoint on :8080 for .kav HTTP access 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -4,12 +4,11 @@
|
||||
|
||||
## 2025-12-28
|
||||
|
||||
### Internal .kav Routing via Traefik
|
||||
- Added Traefik `internal` entrypoint on port 8080 for .kav domain routing
|
||||
- Created `/etc/traefik/conf.d/internal-kav.yaml` with routes for all services
|
||||
- Updated Pi-hole DNS to point service .kav domains to Traefik (10.4.2.10)
|
||||
- Services now accessible at `http://<service>.kav:8080/` without per-service ports
|
||||
- Direct access retained for: Proxmox nodes, kavnas, docker hosts, mqtt, zwave
|
||||
### Internal DNS for kavcorp.com Domains
|
||||
- Added Pi-hole DNS entries for `*.kavcorp.com` pointing to Traefik (10.4.2.10)
|
||||
- Internal clients can now access `https://jellyfin.kavcorp.com` etc. with valid Let's Encrypt certs
|
||||
- No port numbers needed, same URLs work internally and externally
|
||||
- Also added Traefik `internal` entrypoint on port 8080 for .kav HTTP access (optional)
|
||||
|
||||
### Guest VLAN Media Access
|
||||
- Added firewall rules allowing Guest VLAN to access Jellyseerr (10.4.2.25) and Jellyfin (10.4.2.26)
|
||||
|
||||
Reference in New Issue
Block a user