Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I name our servers after the asset tag numbers. DNS can then be used to provide an inventory of our data centers. It also ensures we have a programatic and automatic way to name machines, and numbers are remarkably memorable after a while.


Any scheme based on a pool of names does not scale. If you have big plans, a sequence is the way to go.


There are lots of pools you could use that offer a vast amount of names, assuring that you never run out even if you have a very large number of hosts. Good examples in my opinion are names of things existing in real life, e.g. band names, names of famous (CS) people, ..., while fictional names (characters from some book) tend to run out too soon.

You could even partition hostnames, e.g. all workstations in room 1 are named after famous rock stars, all workstation in room 2 are named after famouse rappers, etc.


I get that there isn't a serious argument here, but how do you reconcile when the guy using 'megadeth' moves to a different cubicle?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: