News for hackers. Stuff that matters.
Re:A Server Naming Scheme by peterwwillis on Wednesday July 09, 2014 @02:26PM (#8011387)
He didn't say to use a functional name, he said descriptive. If the machine is an hp bladecenter 7000 series, reflect that in the name. The functions may change but the silicon will not. If you're paranoid about security, create class names that refer to classes of hardware and number identical/similar ones.

Also it's useful to put the dc and rack number in subnets after the hostname (hpbl7x0001.r55.la.example.com). The next time you're running around the cage reading every single 1U's tag name going "AARRRGHFHH WHERE THE FUCK IS SLIMSHADY.EXAMPLE.COM??", you'll thank me.

(i have no idea why, but it's much easier to get a dns admin to create a new A record than it is to get a NOC employee to update the network inventory database)

(also: good luck using your network inventory db to look up a rack location when the rack/switch that's hosting the network inventory db is down...)

Re:A Server Naming Scheme by lmm on Thursday July 10, 2014 @06:30AM (#8014463)
Just tell the real server to please stand up.

> (i have no idea why, but it's much easier to get a dns admin to create a new A record than it is to get a NOC employee to update the network inventory database)

Well yeah, if parts of your organization are dysfunctional then you find ways to hack their functions into the more functional parts of your organization. But that doesn't make it the right approach in general.

Re:A Server Naming Scheme by Pxtl on Thursday July 10, 2014 @11:19AM (#8015243)
So do blades have internal speakers?

    apt-get install beep
then play some marco polo