You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This allows me to connect via the command line to subdomains of myservers.com without having to spell it out. For example:
ssh foo # connects to foo.myservers.com
Yet a connection to foo.bar.com will still go straight through as normal because OpenSSH will match the first Host *.* block and stop there. This isn't handled correctly by Cyberduck, though. Trying to connect via SFTP to foo.bar.com will return the following error:
DNS lookup for %h.myservers.com failed. DNS is the network service that translates a server name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing access to the network.
The text was updated successfully, but these errors were encountered:
Pull Requests are always welcome.
This isn’t something we are actively working on.
Only direct hostname matches are considered, as far as I can tell. If you want to give this a shot yourselves here are some entrypoints:
I have these rules set up in my
.ssh/config
:This allows me to connect via the command line to subdomains of myservers.com without having to spell it out. For example:
Yet a connection to foo.bar.com will still go straight through as normal because OpenSSH will match the first
Host *.*
block and stop there. This isn't handled correctly by Cyberduck, though. Trying to connect via SFTP to foo.bar.com will return the following error:The text was updated successfully, but these errors were encountered: