Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
Created a droplet with the name host.domain.org -- the server's hostname was set as hostdomainorg instead of host.domain.org.
This is something we discussed internally and we were split on whether it should follow a FQDN model or not. We'll have to see if other users chime in and request it, or we may make it a toggle (on/off) feature.
The hostname is now set to the Droplet name provided.
Hi Moisey, I suppose the Droplet's /etc/hostname and /etc/hosts should use a FQDN as well, what you think? Every Droplet I create I have to change that to follow the hostname I chose during its creation.
To confirm: You are just getting the initial host set in the /etc/hosts not a fqdn?
Yes! I chose the Debian x64 image and in both files /etc/hostname and /etc/hosts I didn't get the FQDN, just the short name. Is it shouldn't happens?
That is currently how its setup but we can overload the /etc/hosts file with the full fqdn.
That would be great!
I'm not sure if I've observed this behaviour... has this item been finished? It's been nearly two years since this was marked as "Started"/
You won't be notified about changes to this idea.