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?
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.×