Setting up a standard naming convention for hostnames is more logical, efficient, and scalable. Include useful information in the hostname, so you don't have to

Setting up a standard naming convention for hostnames is more logical, efficient, and scalable. Include useful information in the hostname, so you don't have to map random lists of names to functions. "What does server 'Foo' do again? Oh, it is a database server. Was that production, dev, or test?" Do you (or one of your operations team) want to be figuring that out at 2AM when you get an alert? Depending on your setup, something like this may be appropriate: <location>-<notation of physical/virtual>-<function>-<#> (e.g. bos-xen-mysql-005, being a virtualized Xen-based MySQL server in Boston). If you have multiple environments (dev/test/prod), add that too.