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
The plugin always seems to use the hostname for SSH which requires that the machine be reachable by DNS. I would like to see an option to use the public IP instead.
If I don't supply a hostname then packet.com assigns a unique one in their DNS name space and hooks the machine and the DNS together. It also sets the machine to report that hostname and FQDN.
However, If I supply any hostname in the configuration (plain or FQDN) then packet does not do any DNS registration (they don't have credentials to add to my DNS name space and even in the case of a plain hostname they can't rely on my name being unique in their name space. ) The machine is still set to report the right hostname.
I would like to use meaningful hostnames and sometimes hook them into my DNS space after they are up. If I could configure the plug in to use the public IP for SSH this would be much simpler.
The text was updated successfully, but these errors were encountered:
The plugin always seems to use the hostname for SSH which requires that the machine be reachable by DNS. I would like to see an option to use the public IP instead.
If I don't supply a hostname then packet.com assigns a unique one in their DNS name space and hooks the machine and the DNS together. It also sets the machine to report that hostname and FQDN.
However, If I supply any hostname in the configuration (plain or FQDN) then packet does not do any DNS registration (they don't have credentials to add to my DNS name space and even in the case of a plain hostname they can't rely on my name being unique in their name space. ) The machine is still set to report the right hostname.
I would like to use meaningful hostnames and sometimes hook them into my DNS space after they are up. If I could configure the plug in to use the public IP for SSH this would be much simpler.
The text was updated successfully, but these errors were encountered: