The Windows e2e on real vpnbot nodes (2026-11-16) showed one provider machine as five
entries with their own host names (VLESS gRPC x4 + Hysteria2, one address). The slots
counted them as five servers, so a slot could sit on a sibling entry of the main
server's machine and a YouTube move could go to the same machine (same address, same
cache cluster).
- ServerAddressMemory (network-bootstrap): addresses the DNS transport answered for
server names (trusted and system paths), noBackupFilesDir, device only, 512 names,
an A answer replaces only IPv4 and an AAAA answer only IPv6; no new lookups
- SlotMachines.of: tag -> host keys (server name or address plus remembered answers),
read once at session start into SlotPlan.machines
- SlotServerAssigner counts use per machine; SlotCandidates first leaves out sibling
entries of the current and busy machines, then the old soft steps
- tests and docs/SERVICE_SLOTS.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>