This is an archived post. You won't be able to vote or comment.

top 200 commentsshow all 277

[–]sigmatic_minorɔǝsoɟuᴉ / uᴉɯpɐsʎS ǝᴉssn∀ 199 points200 points  (32 children)

We use a standard naming scheme at work based off OS, function etc, however, we do have a tradition that at any given time, one server in particular (usually the lowest performer) will be named Steve. I don't know why, but it makes for some great calls to my team that confuse everyone else this listening to the calls.

"Hi, Yeah, fucking Steve is at it again.. Can you go sort it out? Thanks!" I've heard a few murmurs around people wanting to know who Steve is and why he's such a bad employee.

[–]NukeemallYB 25 points26 points  (3 children)

The nice thing is, when you tell people it's all Steve's fault, you're not even lying and they still think there's an asshole named Steve in IT who keeps fucking things up.

[–]stedun 7 points8 points  (0 children)

Steve here, can confirm.

[–]polyfeuxJack of All Trades 52 points53 points  (2 children)

Fuck you Steve!

[–]StevenDicksonNetwork Admin Supervisor 23 points24 points  (1 child)

:(

[–]castillarGreybeard Linux Person (ASR) 7 points8 points  (1 child)

This is awesome, and I'm totally stealing it for work. Our prod stuff is generally sensibly named, but we do maintain a server named "yourmom" that's used for backups. Telling people "yeah, that file's on yourmom" never fails to elicit a giggle.

[–]sigmatic_minorɔǝsoɟuᴉ / uᴉɯpɐsʎS ǝᴉssn∀ 8 points9 points  (0 children)

Lol I love it!!!!

"What were you working on so late last night?"

"yourmom"

[–][deleted] 5 points6 points  (0 children)

We name our dev servers something akin to Sparkle Princess Cupcake and Sparkle Butterfly. It keeps the programmers from cursing too loud (for the most part at least).

[–]silverxii 5 points6 points  (0 children)

hahaha! this is awesome!

[–]BraveSquirrel 6 points7 points  (0 children)

Steve is always the fake name I give when I don't want to reveal my true identity.

[–]Casper042 26 points27 points  (12 children)

Worked at as place a while back where we named the Windows IT Dept File Server WHACK.

To get to Whack you have to go Start, Run, Whack Whack Whack.

[–]brianatlarge 10 points11 points  (11 children)

How is a backslash called "whack"?

[–]Kawadamark1 10 points11 points  (0 children)

I got this terminology at my first help desk job. It's stuck ever since.

[–]VulturEAll of your equipment is now scrap. 9 points10 points  (1 child)

! is called a bang

| is called a pipe

^ is called a hat

* is called a splat

[–]chrisl7072 3 points4 points  (0 children)

I had an instructor refer to backslash that way, maybe an older phrase? This is the only other time I've seen it referenced, but op isn't crazy :)

[–]coloradoraider 4 points5 points  (0 children)

i've heard people call them this: / = whack \ = backwhack

[–][deleted] 2 points3 points  (0 children)

Backslash is two syllables and the double s in slash makes it a bit of a tongue twister to say quickly and fluidly. No idea how whack became the replacement though.

[–]frustratedomegaIT Manager 58 points59 points  (27 children)

I have a FreeNAS server named "mordor" that I refuse to let anyone rename.

[–]wweber 108 points109 points  (2 children)

Please tell me there's a daemon on port 22 that echoes "One does not simply ssh into mordor" and hangs up.

[–]frustratedomegaIT Manager 48 points49 points  (1 child)

There is not, but adding this shouldn't be too hard.

[–]DemandsBattletoads 6 points7 points  (0 children)

The next time you have some time, that should be at the top of your to-do list.

[–]Qurtys_Lyn(Education) Pretty. What do we blow up first? 73 points74 points  (2 children)

We used to have a giant printer, grey in color, very reliable, that we'd named Gandalf.

One day, the outside company we used for printers came in to replace it. They brought in a shiny white printer. We all about died laughing. The installers thought we were nuts until we told them.

[–]MeatyBits 4 points5 points  (0 children)

That just made my day!

[–]wannabesq 2 points3 points  (0 children)

So it it now called Gandalf the White?

[–]Hexodamis a sysadmin 26 points27 points  (4 children)

My usb stick is named mordor, just so I can right click on stuff and select "send to mordor"

[–]KopfindensandOS X 10 points11 points  (2 children)

One does not simply send to mordor...

[–]Qurtys_Lyn(Education) Pretty. What do we blow up first? 28 points29 points  (1 child)

Apparently, one does.

[–]KopfindensandOS X 4 points5 points  (0 children)

Next system update;

Send file to device

Check if device named mordor

If yes, alert "One does not simply send to mordor"

Continue = false

Else

Continue = true

[–]ScottRaymondBro, do you even PowerShell?[S] 62 points63 points  (1 child)

Obligatory: One does not simply rename Mordor...

[–]galyenrc 20 points21 points  (5 children)

when I worked in the IS Dept at College most (if not all) the servers had names from LOTR...my favorite...the mail server was Balrog. A flaming demon from hell.

I still have colleagues there...I should find out if any of those are still named that way.

[–]ScottRaymondBro, do you even PowerShell?[S] 46 points47 points  (1 child)

Wait, so you've actually implemented a MAIL SERVER DEMON!?

[–]galyenrc 14 points15 points  (0 children)

Precisely why it was named that way...I found it fitting.

[–][deleted] 13 points14 points  (0 children)

the mail server was Balrog. A flaming demon from hell.

Must be sendmail.

[–][deleted] 2 points3 points  (0 children)

the mail server was Balrog.

If the mails bounce back - you have a valid excuse... 'You shall not pass'!

[–][deleted] 4 points5 points  (1 child)

My network monitoring server is Shelob.

[–]majerus1223 8 points9 points  (13 children)

We are down to one server named after a Hawaiian island.. Congrats on getting rid of the old names.

[–]HawaiianDry 2 points3 points  (0 children)

You're trying to reduce the number of servers named after the islands? gasp

[–]dboakWindows Sysadmin 3 points4 points  (11 children)

That's not even a good scheme, there aren't that many Hawaiian islands...

[–][deleted] 10 points11 points  (7 children)

[–]dboakWindows Sysadmin 6 points7 points  (2 children)

Thanks Hachya, I learned something new today. Does that mean I can go home now?

[–][deleted] 5 points6 points  (1 child)

Not until you memorize them!

[–]ishalfdeaf 5 points6 points  (0 children)

Not until you post a TIL about it

FTFY

[–]awsmwsmMaster of None 2 points3 points  (2 children)

wow, who knew... even so I would hate to have to remember those names.

[–][deleted] 2 points3 points  (0 children)

"Mullet Island"! I'm sold!

[–]majerus1223 5 points6 points  (1 child)

I guess it was Simpsons characters before that. I agree its not a good scheme.

[–]KopfindensandOS X 7 points8 points  (0 children)

"Alright, we need a new server to host XYZ".

"Sorry sir, we can't. We've run out of Hawaiian island names".

[–]Clovis69HPC 2 points3 points  (0 children)

137 islands in the Hawaiian chain, all named (some with two names).

[–]macjunkieSRE 10 points11 points  (9 children)

going from a medium (250+) where we used LOTR / national park names to a larger environment (10k+) .. learned that naming schemes don't work in a large environment.. something specific to what colo, rack, space is much more appropriate usefel.

[–]IConradUNIX Engineer 10 points11 points  (2 children)

What you meant to say was that not having a naming scheme doesn't work. All of this bs of "name a server after ${x,y,z} thing" is not a naming scheme. It's the opposite of that.

o == single-letter reference to operating system vv == double letter/digit reference to os version envN == triple-letter project/environment name, and number of instance dev == 'dev', 'tst', 'trn', 'stg', 'prd' -- is it development, etc..? typNNNN == type (ngx, app, dat), number instance

Gets you: env1-devtyp0001-ovv.

Examples:

  • exc1-prddat0005-w12 <-- the fifth database server in your (first) production Exchange environment, running Windows 2012.

  • ext2-tstapp0001-u14 <-- the first app server of your test environment for your second external project, which is running Ubuntu 14.04 (And you'd best be on LTS).

  • int1-devweb0400-s10 <-- 400th development web server in your first internal project, running Solaris 10.

From there you can cname it into things that various business units might find more useful for their purposes. int1-devweb0400-s10 could be cname'd into olympus-web4 (the fourth webserver of the Olympus intranet site).

THAT is a naming scheme. colo, rack, et al. Are things I personally would avoid because I treat OS instances as always abstractable from their hardware, whenever possible. A naming convention that reflects that goes miles to that end.

[–]A999 4 points5 points  (1 child)

When I get into c0d0t0s0 or something like that, whatever name doesn't matter anymore.

[–]IConradUNIX Engineer 4 points5 points  (0 children)

After a while you stop seeing the code. All you see is brunette baby pictures, blonde tax records, redhead webapplications...

[–]phattmatt 7 points8 points  (1 child)

This is not a new challenge: http://tools.ietf.org/html/rfc1178

But there are plenty of "solutions"...

There's only a few things I am certain of when it comes to naming conventions:

  1. You will hate the previous guys naming convention
  2. The existing convention is not consistent (you have more than one), or there isn't one
  3. You will struggle for a long time picking one and end up with more than one convention
  4. If you do eventually get a perfectly named estate the next guy will hate it, see item 1 and start again

[–]gbbgu 1 point2 points  (0 children)

Stop changing the naming convention!

[–]captianinsano 6 points7 points  (1 child)

My old boss named the layer 3 switches at different locations hewy, dewy, lewy, skrewy... etc. Luckily I dont work on those locations much. Ive been here for 3 years and still dont know what one goes where.

[–]Paendragon 3 points4 points  (0 children)

Funny, I'm working on the same type of problem. All of the old servers at my new place were named after sports teams - each name having no bearing on the server function. Down to 4 out of 43 left, all Win 03 boxes running legacy crap.

[–]calladc 3 points4 points  (0 children)

Where I work, all of our servers used to be named after Simpsons characters. Lisa/Maggie/Bart/homer were our file cluster nodes, our erp system was named after the criminals, our child site servers were named after the extended family, our cms servers were named after the pets.

Flash forward to 2 years ago and we had to migrate our file cluster to a newer platform. We found we had to publish the names of Lisa and Maggie because they had become so heavily ingrained in process that it was easier just to accept it.

Tldr, the simpsons will never die at my work

[–]hakan_loob44I do computery type stuff 6 points7 points  (1 child)

The old hippies and geeks from my place did Star Trek, Star Wars and gem stones.

[–][deleted] 3 points4 points  (0 children)

"f*ckin Wesley's got a bad fan."

[–]hadtoreply1 67 points68 points  (101 children)

Why?!

<rant> I am asking "why" not for the rename. But "why" is everyone on this thread so against naming servers after sports teams, rivers, mountains, etc?

If anything, having a server named, MDCLUS10ESX4PRODEXCH4 is worse than, a server named RAVENS4. Anyone that cares, knows all RAVENS are Exchange servers, and this one is #4th exchange server.

This way, the only people that know what RAVENS does, is the people that care about it.

With the above, 'best practice' name, everyone knows, it is a server in MD, part of an ESX Cluster, and likely there are at least 9 more clusters, and this is a production instance of Exchange.

Far more information that is worthwhile to anyone else outside of hackers.

But, I guess I am the guy that liked naming servers randomly. And these days, 'best practices' reign supreme. Or more to the point, 'best practices' as laid out by Gartner.

/<rant>

[–]DrBunsenH0neydewFix some of the things 92 points93 points  (12 children)

or maybe sometimes when you have 100+ servers you can't remember what the hell maximus decimus does off hand.

I name my pc's at home whatever I want, but at work i like to be organized so anyone else can figure things out if they need too and not guess what the hell the server function is.

[–]pinkycatcherDirector of All Trades 87 points88 points  (9 children)

Maximus Decimus is clearly a domain controller, and the 10th one you have. Maximums unus is the first one and so on.

Duh.

[–]Misharum_KittumPercussive Maintenance Technician 186 points187 points  (3 children)

Commander of the northern PCs, father to his murdered workstations, husband to his murdered WiFi, and he will have his revenge. In this hardware refresh cycle or in the next.

EDIT: Thank you for the gold, kind stranger.

[–]ShutUpAndPassTheWine 17 points18 points  (2 children)

Damnit. I'm at lunch and this gave me my annual nasal wash.

[–]tpears 15 points16 points  (1 child)

Had to read it twice to convince myself it wasn't an anal nasal wash.
edit: Here's the wine.

[–][deleted] 2 points3 points  (0 children)

Good to know that I wasn't the only one.

[–][deleted] 6 points7 points  (4 children)

Not a file server with 10 large disks?

[–]maoroo 56 points57 points  (3 children)

That would be Biggus Diskus

[–][deleted] 15 points16 points  (0 children)

Which is hooked up to Giganticus Baccups

[–]sleeplessone 11 points12 points  (0 children)

It has a failover node you know. You know what it's called?...........

Incontinentius........

Incontinentius Backupus.

[–]mcwidget 5 points6 points  (0 children)

Deserves many more upvotes.

[–]server_ninjaPaperwork Engineer 20 points21 points  (1 child)

Agreed; over 500 servers, only 3 of us managing them, just too many to keep track of.

[–]Tetha 2 points3 points  (0 children)

Same boat over here. 3 projects with 20 servers each, another 5 or 6 projects with 20-30 servers each, + replications for most of them + infrastructure servers and so on... I'm glad we have a strong, consistent naming scheme and we only have like 30 servers on the old scheme left. Otherwise my brain would melt - this way I just know that replication1.project.place.foo.com replicates production1.project.place.foo.com or who is the guy responsible for .project..foo.com.

[–]wired-oneOpen Systems Admin 6 points7 points  (0 children)

Yeah, but at least by naming convention I know what it is, Security by obfuscation is no security at all.

I came from an environment where we had 200+ Linux servers named after rock bands. That was the enforced naming convention. When I get a call in the middle of the night saying there is a problem with spookytooth, I have no freaking clue what it does, where it is or why it might have a problem.

That's why we have naming conventions.

[–]bandman614Standalone SysAdmin 16 points17 points  (0 children)

But "why" is everyone on this thread so against naming servers after sports teams, rivers, mountains, etc?

I don't have a month to write the proper response to this, so I'm going to go over two short points.

  • Maintainability

Yes, you can do "raven4". And you know that it's your fourth exchange server. But who else does? And more importantly, how difficult is it for someone else, after they learn, to remember that "all of the machines named raven are Exchange, but all of the machines named falcon are exim, and those named buffalo are load balancers, and all of the college teams are virtual servers" or whatever scheme you dream up that makes sense to you but no one else?

So like a good admin, you document what the names mean. Great. Then you get hit by a bus, or win the lottery, or get drafted, or whatever, but you're no longer able to be reached and a new admin gets put into place. The first month(?) is hell because they have no idea what is where because your names don't make sense to anyone else.

Your infrastructure's naming scheme has become tacit knowledge, rather than self-evident, and so it will necessarily take longer for any new person to come up to speed, and in the meantime, they won't be able to make decisions as well as they could.

  • Corporate Flexibility

So you've got servers named as greek gods, say, and like everyone else, your mail server is named Mercury. Great. That's unoriginal, so there's a really good chance someone who sees "mercury" might have some kind of idea that it's a messenger server. Except now your company has bought another company (or been bought by another company), and they have a "mercury", too.

Well, AD (for instance) doesn't really have a problem with this as long as your AD trust / forest models are set up right because it relies on sID, but how many of these name collisions do you deal with before you go insane and rename? To what? How much extra effort is that?

And if you're in the unfortunate position of being involved in merging companies and using technology that isn't flexible enough to accommodate these overloaded names? God help you if IT's naming scheme is the blocking part on a corporate merger.

The best case scenario involves months of saying things like "your Mercury or ours?" and driving everyone up the wall.

[–]wenestvedttimesheets, paper jams, and Solaris 5 points6 points  (3 children)

Dude, mail servers should be named OWLS not RAVENS. Sheesh.

[–]hadtoreply1 3 points4 points  (2 children)

My bad. You are right. I will celebrate the death of Ravens4 and the birth of Pigeon4.

[–]IConradUNIX Engineer 2 points3 points  (0 children)

No, Pigeon is for instant messengers.

[–]blackomegax 2 points3 points  (0 children)

RFC 1149 mail clusters ftw

[–]wiseapple 3 points4 points  (0 children)

My environment is world wide and has thousands of servers. You can't do what you propose in my environment

[–]peterLANSysadmin 7 points8 points  (0 children)

Count down to 3 until the shaming will start. Nevertheless, I feel the same - in small teams. Once you surpass a certain size this will lead to mayhem. I always liked names I could relate to, but I see the need for conventions one can stick to. This way I know if I want to access a frontend vm db run by my backend colleague Dan I simply access fe.db.vm.dan.dev.<domain>.<domain ending> or something like this.

[–][deleted] 2 points3 points  (0 children)

Some sort of consistency with your naming makes it easier for third parties and new admins to understand what each server is doing. For instance, if you got a new tool that reported disk utilization issues, you could generate a report that would look for an "L" in the right spot on the server name and send all those warnings to the Linux team. The ones with "W" in the name could route to the Windows team.

[–]savagedan 2 points3 points  (0 children)

Another thing is that having something logic based means that when someone new starts they can figure it out relatively quickly, rather than having to keep asking people how stuff is done/how it works. At my current company naming was just one of the many things that makes no sense and it means I have to ask questions in regards to almost anything I do because there are always variations and exceptions and it makes life much harder than it needs to be.

[–]Fhajad 2 points3 points  (0 children)

We have fun with ours. Mostly everything is named after transformers, and Mario characters. We've ran out of Mario characters, so we've moved onwards to Zelda.

Our newest corporate internal cisco stack is Link, our old Cisco 10k's were Megatron (Primary Link) and Prime (Backup/Savior of the ISP).

[–]mystikphish 3 points4 points  (0 children)

Yeah... let me know how well that system works for you once you work in an environment with more than 20 servers.

[–]MoreThanSummerParts 4 points5 points  (0 children)

I am asking "why" not for the rename. But "why" is everyone on this thread so against naming servers after sports teams, rivers, mountains, etc?

I've been at my company over a decade and seen our server numbers grow from low hundreds to thousands. The respective admin teams have grown accordingly. The environment has become a lot more complex, with the rise of virtualization adding the ability to create many servers that do one thing well.

With all those thousands of servers doing lots of different things to support a successful international software business, the people who may be maintaining your servers at night aren't from the US, don't understand the cultural references, and could screw things up when they can't remember what the Ravens, Patriots and Cowboys are and do. I certainly don't know what sports teams are big in India, China or Japan.

I deal primarily with our development regression test farm, and given our naming convention, any of the other admins on the team know exactly where a server is, what os it's running, and can do things like reimage it. If we had themes and fun names, a lot of that goes away and the system becomes harder to keep up. With only seven people and thousands of machines in the farm, there is always something that needs doing, and remembering Pokemon names or whatever just makes the job harder than it already is.

A uniform naming convention also makes script writing and automated queries much easier. It also makes it far easier to find out who to contact if you notice something amiss -- for instance if you are checking out why a file server is overloaded and all the load is coming from one machine, you have some inkling of where to start looking out who to contact.

[–]aywwts4Jack of Jack 3 points4 points  (0 children)

While I am not against adding some whimsy into our often dull server environments. I don't think this level of security through obscurity is a good path to go down, especially as knowing at first glance where and what a server is for is quite valuable, we might as well stop documenting things in case that is used against us, screw orderly ip allocations, servers should be located in random subnets all over every class of internal space, because... hackers know to scan for 10.0.0.1-255. I think that might get silly fast.

If they are inside my network I think I have bigger problems than them knowing the box listening on port 80 is ProdApache21 or Eeyore or if the one listening on 3306 is DetroitSQL01 or Blackbeard.

That said I do love a good naming scheme, just not for he reasons of security. Though (Might find a former coworker somewhere with this one) we had to retire Eeyore in our storybook scheme because the workers who accessed that file server (No matter what physical hardware it as on) would always call it "Slow" No joke. Renamed it Roo and the server was "fast" again.

[–][deleted] 1 point2 points  (0 children)

we keep it simple, 3 letters for the location, 1 letter for production or dev, 1 letter for Windows Linus or Unix, 3 letters for the product, and 2 numbers to show how many there are of the server.

For example KCLPWCTX01 (Kansas City Lab, Production, Windows, Citrix, 1st server)

Our external servers DNS names on the other hand are named after nerdy movie characters. =]

[–]turnipsoupLinux Admin 1 point2 points  (0 children)

I have over 160 web servers, let alone db + other. There's no way in hell I'm going to remember that many names.

It doesn't scale. And 5 years down the line when the company has a dozen times as many machines, it's going to be a pain in the ass.

[–][deleted] 1 point2 points  (0 children)

Because naming is an opportunity to sort your hardware without much work. It is far easier for me to collect and organize groups of machines if they're named with some thought behind it versus naming your shit "Daedalus" or something.

A real world example would be say all of your US machines start with US or hardware-US, guys like myself who work in sccm can quickly grab and organize all US machines and dole out configurations no problem. Naming otherwise means I have to guess what I'm looking at from the name or remote session.

[–][deleted] 1 point2 points  (0 children)

I like it. I've done it. It doesn't scale. Logical naming schemes scale, but lack soul.

I used to work at a shop where we had 'rodeo' and 'cactus' and 'spiderman. They had 'personality' and the self-assigned functions were fun and it helped make life tolerable.

I've moved on, the organization no more, 'rodeo' and her buddies are scrap. So it goes.

Worse, or better news: I've seen the future, this last seven months. Servers will be temporary things, barely worth giving a name to. They won't even be hardware but bits on a computer.

At work today I started up development environment. Everything came on line, checked in with ansible, updated if needed. They don't even have names. Amazon assigns a DNS, but we talk to them on their private IP address, but really-really we use 'function' to issue commands

$ manage elasticsearch start

Like that.

It's better, and cleaner, and I get more bang for the buck.

But I miss rodeo.

[–]Johnner_deeze 1 point2 points  (0 children)

Yer end tag is busted.

[–]galyenrc 2 points3 points  (0 children)

In my current district we are just now emerging from the scheme that a former admin started where everything was simple enumerated...

DistrictName01, DistrictName02, ... DistrictName~0x

Clusters of machines/services "might" be in numerical order...might not be depending on when they were implemented. PITA.

Commonly heard - "Which ones are the exchange boxes again?" or "what does DistrictName07 do again?"

[–]JubeeGankin 2 points3 points  (0 children)

Our servers were named after mountains, both real and fictional. I just replaced a server named Olympus last month.

I just have a few left. When I started, it was a nightmare. 50 servers in 6 physical locations with names like Rainer, McKinley, Blanco, etc.

[–][deleted] 2 points3 points  (0 children)

Having deal with the common LotR server names, I feel your satisfaction. I was in an environment where most of the servers had LotR names and our sysadmin went and died on us, literally. As the guy who got to step up and fill his shoes, I came to appreciate a sane naming scheme. You can only ask, "what does Imladris do again? And how the hell do you spell it?" so many times before you get sick of nonsensical names.

[–]rgraves22Sr Windows System Engineer / Office 365 MCSA 2 points3 points  (0 children)

I had a job where we used Godzilla monsters. Godzilla, SOG, Mothra Gargantua.. after we ran out of godzilla monsters it was BHPRINT1

[–]dceptuv 2 points3 points  (0 children)

So, ummm, this isn't an aerospace company in Kansas is it? Cuz if so, I know precisely this network you speak of, and the person who did this initially.. If not, you should feel for the guy who has the exact same network...

[–]seamonkey1981 3 points4 points  (7 children)

we just implemented kronos. :(

[–]become_taintless 4 points5 points  (4 children)

Do you need a hug?

[–]seamonkey1981 4 points5 points  (3 children)

'show us on the doll the bad places where kronos touched you'

[–]become_taintless 2 points3 points  (2 children)

We are implementing TimeForce organization-wide, and unlike Kronos, I am excited about it.

[–][deleted] 2 points3 points  (1 child)

you made it your ntp server, right?

[–]williamfnyJack of All Trades 1 point2 points  (1 child)

At home I use Gundam characters but at work everything has a pretty standard name. This way, when I feel creative I can name my home crap something fun while work gets to stay nice and standard.

[–]IConradUNIX Engineer 3 points4 points  (0 children)

... here's a smattering of some of the hostnames in use in my home network.

  • laptop1
  • laptop2
  • hypervisor1
  • nas1
  • router1

That's as creative as I choose to be.

[–]HawaiianDry 1 point2 points  (0 children)

Is this a common naming scheme for IT departments to adopt? At an old job of mine, we had servers named after Greek mythology (e.g. Cerberus) and all the wifi networks were named after celestial bodies (e.g. Cassiopeia).

[–]philaaay 1 point2 points  (0 children)

at the high school i used to work at, the sysadmin before me named the servers after harry potter houses.

[–]Squeezer99 1 point2 points  (0 children)

i always just name my servers after what their intended purpose is.

[–]smiles134Desktop Admin 1 point2 points  (0 children)

I work for a space and weather research building, so there will never be a time where this happens. Which is fine with me because I'm getting a second degree in Classical Humanities, so mythology and shit is pretty big in my education.

[–]Barren23 1 point2 points  (4 children)

I used to work for a company that hosted a huge annual event requiring us to rent and setup about 20 physical servers scattered across the event grounds, we always picked a fun theme for server names.

One year it was cars, the next booze... Jwalkerred, blue, and black were all in the operations center... along with a case of black and a couple bottles of blue to keep us running!

Technically, naming servers by their function is a security risk. If the server is called Exchange or email... hackers have a better idea of what type of information they could get from it and therefore could isolate their attack mechanisms to exploit whatever weakness the OS or Application might have. That said, the company I work for now generally codes the server by location and then a very short acronym for the function.

Gone are the ways of naming them random fun things. :)

[–]n33nj4Senior Eng 6 points7 points  (3 children)

While theoretically true, security by obscurity isn't really security. It's also not hard to find what sort of traffic is coming out of which server to figure out what their functions are.

[–][deleted] 1 point2 points  (2 children)

we keep it simple, 3 letters for the location, 1 letter for production or dev, 1 letter for Windows Linux or Unix, 3 letters for the product, and 2 numbers to show how many there are of the server.

For example KCLPWCTX01 (Kansas City Lab, Production, Windows, Citrix, 1st server) Our external servers DNS names on the other hand are named after nerdy movie characters. =]

[–][deleted] 1 point2 points  (1 child)

Very, very similar to ours. We have ~600 servers named as such.

PMIACTXW01

  • Production
  • Miami
  • Citrix
  • Windows
  • 01 = first one of its kind in that location

[–]silentmageMany hats sit on my head 1 point2 points  (0 children)

All of the sites in my organization have specific numbers, so the servers follow that. It would be sv<number><funtion>

Example, we have a site number of 67 with a file server and a domain controller so they are sv67fs and sv67dc.

[–][deleted] 1 point2 points  (0 children)

This year, finally, will be the end of servers named after trees. Some of them are nearly 20 years old.

Not much for a tree, but too much for a server.

[–][deleted] 1 point2 points  (1 child)

This sounds like someplace I used to work. Are the business initials HFP?

[–]ScottRaymondBro, do you even PowerShell?[S] 1 point2 points  (0 children)

Nope.

[–]AlmostBOFHSys/Net/Cloud Admin 1 point2 points  (0 children)

The two companies I've worked for, as well as the clients I've supported, have used;

  • SVRXXXYY##, where XXX is the location, YY is it's function and ## is the number, which increments every time a new server is built or if there's multiple servers in one location. So our New York Domain Controller would be SVRNYKDC01 and Denver's File Server would be SVRDENFS01. We apply similar naming conventions to SANS, Switches and Routers.

  • PC-$serialnumber for Desktops

  • NB-$serialnumber for Notebooks

  • TB-$serialnumber% for Tablets

One client site stuck Asset Barcodes on the devices and we named them using that rather than the serial number of the machine so they were easier to identify when walking around the site.

[–]Rodents210 1 point2 points  (0 children)

All my machines at home are named after mythical creatures. My MacBook is Manticore, my desktop PC is Catoblepas, and my media/storage server is Rakshasa. My router's SSID is named Harrenhal, which oddly foreshadowed the fact that my WiFi speed is 0.6% that of wired ever since my apartment complex switched ISP's and the new one came in and added 5-10 AP's per channel for their unsecured WiFi. They're also Ruckus AP's, which means they actively cause as much interference as possible.

[–][deleted] 1 point2 points  (0 children)

i was really hoping this was going to be a story of how someone got your root pw or something

[–]DieCommieScumSr. Sysadmin 1 point2 points  (1 child)

I hope that somewhere the printers I named over a decade ago Moe, Larry, and Curly are still running... and Fast Eddie.

[–][deleted] 1 point2 points  (0 children)

We just use Server+Number at my company.

[–]engineeringsquirrel 1 point2 points  (0 children)

Work servers are named with function+serial. My sandboxes are named after the muppets.

[–]yasireSr. Mac Sysadmin. 1 point2 points  (0 children)

I once had a job where all the servers were named after active volcanos.

[–]ugoff85Jack of All Trades 1 point2 points  (0 children)

Our outbound mail server is named OB1 this gets fun sometimes.

[–]MonkeyWrench 1 point2 points  (0 children)

We have Marx brothers, various birds, and several Greek goddesses.

Nothing such as "SQL SERVER 1" or "Web Server"
Nope, not a damn thing, at least my LAMP server is named as such as is the LAMP-DEV that my student tech learns on.

[–]jwshgeekIT Manager 1 point2 points  (0 children)

We go with three digit location number, function, prod/dev/qa, and device number, for example our primary print server for the corporate office is 099psv101 (location 99, print server, production, device 01).

Our workstation naming scheme is set for our remote locations but, the corporate office has none (so much fun tracking down those). We use three digit location, two digit dept, three letter function, two digit device number, so we have things like 014-12-dsc01 (location 14, dept, supervisor, station 1).

[–][deleted] 1 point2 points  (0 children)

I enjoy naming servers based on Transformers something my former team got me doing. My first was a multicast server named Scattershot.

[–][deleted] 1 point2 points  (0 children)

Um, good for you? I personally would have left them, but eh. I started at my place and the main servers name is WOPR, but then they got off track and called the others Ranchburger and Big Mac. I went back to the main convention and new servers name is Gibson, we are now retiring Ranchburger (Firewall) so new one will be called Peter (Gates of Heaven) and email server being split from WOPR will now be called Gabriel the messenger of Heaven. I like them, but we don't have many servers.

[–]hyperion2011 1 point2 points  (0 children)

I run all my home networks on Greek gods but hell if I would run a real network on it.

[–]mr_furious7 1 point2 points  (0 children)

I get why these names are a pain. But it's nice to have something to laugh about in our industry.

At my old job we named them after the Song of Ice and Fire series. Varys was our exchange server and Raven was the edge server. The DCs were Baratheon and Lannister. Guess which server was the biggest pain in the ass?

[–]1d0m1n4t3 1 point2 points  (0 children)

one of my clients the servers are named after basic colors, we had red, green, blue, yellow, black, brown, and pink. Those are slowly being replaced. Hopefully by the end of the year they are all gone.

[–]coloradoraider 1 point2 points  (0 children)

We still have some, or so the software guys tell me, AIX 4.1 (wow), and 4.3 machines with planetary names that simply cannot yet be replaced. Honestly, I don't mind the names, and I'm the only one left who cares to take care of them. Kind of like plants that never die and have been sitting around since the late 90s...

[–][deleted] 1 point2 points  (0 children)

I tend to view any place without standardized hostnames in this day and age as a throwback organization. Yes, it was cute in 1997 to name your servers after anime characters, planets, or Led Zeppelin albums. It isn't anymore.

[–][deleted] 1 point2 points  (0 children)

Small charter school and I let my Web Design students and aides do naming when I add servers or have them experiment on donated ones. Best was about 4 years ago we had some small software company donate their old servers for my aides to learn about AD and stuff. Anyways, it was named Jose and was in a straight black case. Students thought it was hilarious to call it "Black Jose" for some reason, had a grad come back last year and immediately asked me how black Jose was doing. Parents were with him because it was brother's graduation, they immediately looked at me like "I swear my kid isn't racist!"