DO Ideas 2

Configure new instance hostnames exactly from droplets name if set as FQDN

Created a droplet with the name host.domain.org -- the server's hostname was set as hostdomainorg instead of host.domain.org.

  • Anonymous
  • Sep 11 2018
  • Shipped
  • Sep 11, 2018

    Admin Response

    This has been fixed for a long while. Sorry for not updating sooner!
  • Attach files
  • The Digital Orchard commented
    September 11, 2018 20:10

    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"/

  • Guilherme Gondim commented
    September 11, 2018 20:10

    That would be great!

  • Moisey Uretsky commented
    September 11, 2018 20:10

    That is currently how its setup but we can overload the /etc/hosts file with the full fqdn.

  • Guilherme Gondim commented
    September 11, 2018 20:10

    Moisey,

    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?

  • Moisey Uretsky commented
    September 11, 2018 20:10

    Guilherme,

    To confirm: You are just getting the initial host set in the /etc/hosts not a fqdn?

  • Guilherme Gondim commented
    September 11, 2018 20:10

    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.

  • Moisey Uretsky commented
    September 11, 2018 20:10

    The hostname is now set to the Droplet name provided.

  • Moisey Uretsky commented
    September 11, 2018 20:10

    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.