From 8922c8099516a4e33e8a8833fd63cf0afa6a3d25 Mon Sep 17 00:00:00 2001
From: jester <admin@zerolaghub.com>
Date: Sun, 28 Dec 2025 00:39:05 +0000
Subject: [PATCH] Clarify bastion issue affects both IP and hostname from
 external networks

---
 OPEN_THREADS.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/OPEN_THREADS.md b/OPEN_THREADS.md
index 0a0ee5b..609479f 100644
--- a/OPEN_THREADS.md
+++ b/OPEN_THREADS.md
@@ -8,7 +8,7 @@ This file tracks items that are unresolved, under investigation, or explicitly d
 
 ### Bastion public SSH access (BLOCKER)
 - **Status:** ACTIVE - blocking external user access
-- Public SSH to `zlh-bastion.zerolaghub.dev` fails with `kex_exchange_identification: Connection closed`
+- External SSH to bastion (both IP and hostname) fails with `kex_exchange_identification: Connection closed`
 - TCP connection succeeds but SSH handshake never proceeds
 - Internal SSH works perfectly; issue is specific to WAN→bastion path
 - Action required: