| Property | Value |
|---|---|
| Host VM | — (currently NOT in place anywhere) |
| Compose path | — (no active deployment) |
| Image | — (no active deployment) |
| Container name(s) | — (no active container) |
| External URL | <— (DNS mechanism, not a UI)> |
| Networks | — (n/a) |
| DB / state | — (n/a) |
| Auth | — (n/a) |
| Backup | n/a — nothing deployed. |
For Lancache to actually intercept game-CDN traffic, the CDN hostnames (e.g. *.steamcontent.com, level3.blizzard.com, epicgames-download1.akamaized.net, etc.) must resolve to 10.100.100.161 from any LAN client. The bundled lancachenet/lancache-dns container on VM-SL-61 was the intended mechanism, but it has been stopped (Exited 128) since late 2024 and was removed during the 2026-04-29 cleanup.
Status (user confirmed 2026-04-29): no redirection is in place anywhere. The active LAN resolvers are 10.100.0.10 / 1.1.1.1 / 8.8.8.8 (all unencrypted) and none of them rewrite CDN hostnames to 10.100.100.161. As a result the Lancache service on VM-SL-61 receives no traffic and the 797 GB of cached content is historical leftover from a previous setup.
If/when Lancache should be reactivated, the redirection would be implemented at one of:
Services → DNS Resolver → Host Overrides or Domain Overrideslancachenet/lancache-dns container on VM-SL-61 and point clients at it as a primary resolverxio.bio PDC (single AD DC since VM-DC-02 retired)Mit Abschluss der DC-Migration (Target-IP 10.100.100.10, siehe migration/2026-05-03-night-recovery) ist der DC der zukünftige BIND-Host für Lancache-DNS-Overrides — Cross-Link einplanen sobald DC up ist.