Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to use IP instead of hostname? #8

Open
wmamills opened this issue Jun 2, 2019 · 0 comments
Open

Add an option to use IP instead of hostname? #8

wmamills opened this issue Jun 2, 2019 · 0 comments
Assignees

Comments

@wmamills
Copy link

wmamills commented Jun 2, 2019

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.

@jeefy jeefy self-assigned this Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants