Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Folks - what naming conventions are used in your organization when creating DLs in the GAL? Thanks.


locked by HopelessN00b Dec 5 '14 at 8:31

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

up vote 3 down vote accepted

Currently we use the following conventions. They sort very nice in the GAL.

For system Alerts

  • alert.yyy

For inter department communications


We have the generics that are exposed to the outside world

  • netops
  • accounting
  • abuse
  • security

For service accounts

  • svc_sql_cluster
  • svc_ops_mgr

For locations or offices

  • CompanyHQ
  • CompanySFO
  • CompanyRemoties
  • CompanyDallas
Thomas, thanks for the answer. Why do you have system alerts and service accounts in the GAL or are they hidden? – eft May 15 '09 at 3:57
They are all hidden from the GAL, but I wanted to expand further what system has worked for me over and over. – Thomas Denton May 15 '09 at 15:09
ok thanks for the clarification – eft May 16 '09 at 15:41

I like to start with a prefix of some sort so they sort nicely in the GAL perhaps '_GRP'. Then I try and work from the least specific to the most specific.

  • _GRP_Administration
  • _GRP_Fiscal
  • _GRP_IT
  • _GRP_IT_Operations
  • _GRP_IT_Web
Thanks for the answer – eft May 12 '09 at 14:16
We do the prefix too gr_ops-project-dev (for dev) and gr_ops-project (for users) often gr_logs-project too – reconbot Dec 3 '10 at 13:20

Not the answer you're looking for? Browse other questions tagged or ask your own question.