Droplet naming scheme and FQDN

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?

Submit an answer

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!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

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 is my domain name.