There are different philosophies for hostname conventions. In my experience, using a common theme and context adds logic to a potentially complicated network.
At home, I use spells from old Infocom interactive fiction games as my naming convention. While it may seem silly, my home network is small enough that I can remember the purpose of machines, and I've got a large corpus of potential names. I've also seen others use names of characters from television, movies or books. Use your imagination!
At work or in a shared environment, I use more descriptive names, such as web-dev-01 for a development web server. Security through obscurity causes more headaches than it's worth as it makes it more difficult for others to understand the layout, and the illusion of security that comes from giving a machine a wacky name will not protect you from malicious users.
Either way, once you've developed a schema, stick with it; mixing naming conventions just makes things more difficult.
3 comments:
We use a general naming convention for our Windows machines at work (WS01, AD1, AD2, etc.), but our Apple server and iMacs in the IT dept have developed X Men names. Our Xserve is ProfX, my bosses iMac is Logan...
It's fun for us and nobody else gets it!! :)
That's pretty clever :-) I've got another host naming story... In repairs, one of the servers wasn't that secure and kept getting hacked, so we renamed the host to broken, much to the chagrin of its administrator. Then broken was hacked and repaired, and the admin insisted it was secure, so it was renamed to fixed. I suppose you can see where this is going... fixed was hacked, and to this day (five years later!) it's still-not-fixed.
lampbox1, lampbox2, lampbox3. . . .
Post a Comment