geotag-srvtype[#]-prod-[pokemon_name_or_whatever]
That way, if your environment is completely fluid, it becomes obvious when a node has re-deployed, and if it's not, you can just re-use the old name when re-deploying instead of generating a new one.
You can of course include hash-looking things in hostnames as well, but I'm a strong believer that hashes are for computers, not for humans to read (most of the time).
Then you can truthfull say you deleted/sunk the Bismark.
Anyway I think there is nothing wrong with naming classes of things after known things - so you are deploying two more Victor class frontend servers or Dreadnaught monitoring services.
The trouble becomes when you care about Dreadnaught-oux3z and treat it as not disposable.
As an example, in cloud environments not much time is spent investigating issues. When something fails the solution is often to just wipe and redeploy. I prefer fully understanding the problem and having the tools to troubleshoot. Especially because in my work the servers still have different roles.
> Astronomers estimate there are about 100 thousand million stars in the Milky Way alone. Outside that, there are millions upon millions of other galaxies
https://www.esa.int/Science_Exploration/Space_Science/Hersch...
https://www.nationalgeographic.com/science/article/factors-a...
Seriously though, has anyone considered the big-O complexity of the "vaccine per virus" approach to improving immunity?