I’ve always named my droplets as FQDN, it just seemed natural to do it that way. So most of the droplet I own are accessible from the web, since it was needed.
So here I am, wanting to create the first machine I need that doesn’t have to be accessible from the web. How should I name it? I know I could name it as FQDN and just not setup the DNS for it, but is there any other advantages to FQDN other than being a logical choice for internet accessibility? Does it change anything to name a machine that isn’t though to be accessible via the web as something else than FQDN?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
The name of the droplet is used in the PTR record, whether you have an A record or not for it… it should be an FQDN.
I pick a unique name for each of my servers, and use that as a subdomain for my domain. For example:
Where server7 is the name of the server, and ahrotahntee.ca is my domain name.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.