We do a mix of things here at Gonzaga. Some well-known servers such as DNS have common server names such as ns1 and ns2. Primarily internal servers have names that relate to the university, the Catholic faith, or something else that doesn't readily identify its purpose but makes it memorable to the end-user. I don't really do this for security purposes; it's more for end-user use and reducing the likelihood that the name of the server doesn't become obsolete by altering the services that it provides. Servers that are internal infrastructure that are not normally accessed by users by name (e.g., Active Directory DCs) get names that are semi-obtuse but clear enough to identify what they are for. Test servers can have really bizarre names.
Greg Greg Francis, Sr. System Administrator Central Computing and Network Support Services Gonzaga University -- Spokane, Washington 509-323-6896 [EMAIL PROTECTED] > -----BEGIN PGP SIGNED MESSAGE----- > > On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote: > > > What is the security communities recommendation on naming servers? Is > > it safe to name a server by the function the server provides?
