hostname routing

[Brian Candler]

On 16/06/2026 10:34, snek wrote:
> Thanks for your reply. I'm aware of the workarounds, I guess to be 
> explicit, by asking this mailing list I was hoping more for a 
> discussion about possible changes/extensions/features/etc to the SSH 
> protocol itself that could improve the experience here. If I could 
> just run `git clone snek at git.example.com/repo.git` without having to 
> configure a vpn or jump proxy, and even better if I could give that 
> clone url to other people without them having to know about the 
> details of my server setup, that would be ideal.

I suspect the answer you'll get is "yes we've thought of it, and no were 
not going to do it because <reasons>".  Ditto for looking up SRV records.

Although "git clone ssh://snek@git.example.com:22001/repo.git" is a bit 
uglier that what you'd like, I think it more or less meets your 
requirements. Bind to port 22001 on the host itself, publish AAAA record 
pointing directly at the host, and A record pointing at the port forwarder.

If you want access from the inside network over IPv4 (on private IPs) 
without relaying via the gateway then you'd need split DNS. But if IPv6 
is working, that won't be needed.