[26958] in North American Network Operators' Group
RE: SERVER NAMES
daemon@ATHENA.MIT.EDU (Roeland M.J. Meyer)
Wed Feb 2 18:05:47 2000
From: "Roeland M.J. Meyer" <rmeyer@mhsc.com>
To: "DeepBlue" <james@darkblue.net>, <nanog@merit.edu>
Date: Wed, 2 Feb 2000 15:01:02 -0800
Message-ID: <NDBBJKGADKGFDIKIHOBJAEIMCCAA.rmeyer@mhsc.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <31C101EA1371D31199ED005004DA956082C9@FOGHORN>
Errors-To: owner-nanog-outgoing@merit.edu
I can only say what we use here, at MHSC.
One group I haven't seen here yet are birds, crossed with type of use and
sub-domain. Condors are always main development machines, Ravens are data
servers, falcons are support/noc hosts, hawks are intranet *DCs, peregrin's
are management machines, owls are QA servers and source repositories, etc.
All workstations are DHCP'd so names need not be man-readable and follow
conventions like wksta1.dhcp.mhsc.com, with SMB names that are also the uuid
names of their assigned user.
-----Original Message-----
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
DeepBlue
Sent: Wednesday, February 02, 2000 11:05 AM
To: 'nanog@merit.edu'
Subject: SERVER NAMES
This is a little off of the normal lines of the list. But I am at a loss as
to what naming convention I should use with my new set of servers. I have
already used Southpark, Jet sons,and Warner brothers cartoons. Does any one
have any good suggestions other than the Super Friends?
I apologize ahead of time if this email seems useless to some of you.. but
humor me please.
James
james@iceblue.net
