let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: include tailnetDns in wide-area beacons

Browse Source
This commit is contained in:
Peter Steinberger
2025-12-20 15:02:23 +01:00
parent 554d9bc6ce
commit 044f525eb8
5 changed files with 23 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/bonjour.md
View File

@@ -60,6 +60,7 @@ In the Tailscale admin console:
- Add split DNS so the domain `clawdis.internal` uses that nameserver.
Once clients accept tailnet DNS, iOS nodes can browse `_clawdis-bridge._tcp` in `clawdis.internal.` without multicast.
Wide-area beacons also include `tailnetDns` (when available) so the macOS app can auto-fill SSH targets off-LAN.
### Bridge listener security (recommended)

2
docs/discovery.md
View File

@@ -70,7 +70,7 @@ Disable/override:
For London/Vienna style setups, Bonjour won’t help. The recommended “direct” target is:
- Tailscale MagicDNS name (preferred) or a stable tailnet IP.
If the gateway can detect it is running under Tailscale, it publishes `tailnetDns` as an optional hint for clients.
If the gateway can detect it is running under Tailscale, it publishes `tailnetDns` as an optional hint for clients (including wide-area beacons).
### 3) Manual / SSH target