mirror of
https://github.com/Crosse/sshsrv.git
synced 2026-04-25 03:45:55 +03:00
[GH-ISSUE #8] Support jump hosts? #7
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sshsrv#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dragonpaw on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/Crosse/sshsrv/issues/8
Currently, I have a bunch of hosts that I reach via various different jump hosts at different sites, and would love a way to encode the correct jump host into the record somehow.
@Crosse commented on GitHub (Jul 17, 2025):
This is an interesting idea. I'm on the fence about whether putting jumphost information in public DNS is a good or bad idea, but ultimately that's a question for the user—not me. I'm open to proposals! I don't use jump hosts anywhere, which means I don't have a good feel for how best to format the DNS record.
(Hm, I guess it doesn't have to reside in the same
SRVrecord, though…ah, see, I think you just successfully nerd-sniped me!)@dragonpaw commented on GitHub (Jul 17, 2025):
I would actually use a SVCB record (the successor to SRV) as that has the ability for application-specific data, in addition to a specific port field. "alpn=jh=..." "port=..." would do the job and be optional.
P.S. Some entities have private dns zones that are not internet-visible and could more safely contain such data.
@Crosse commented on GitHub (Jul 18, 2025):
I'll check that out.
Heh, yeah. As soon as I wrote my original statement I had the same thought, but left it anyway. 🙂
I'll try to look at this over the weekend!