In your case, geographic domain names are probably easier to work with, since its unlikely that the world regions will actually change anytime soon (but dont quote me on that).
 
It really comes down to management of the network, and what your admins feel more comfortable dealing with.
 
Domain/Forest names are really only an issue in the case where things change, its a real pain to move these things around.
 
I guess the question it what do they hope to acomplish with generic names ? If there will be some domain consolidation in the future (eg combining AMER and EAME) it could be confusing for users / management, or if you migrate part of a region into another region due to increases / optimisation of links / link speeds.
 
For geographic domains, I normally stick with naming the regions after their geographic boundary, but always resist including the company / organisation name as part of the forest / domain names, as this is more likely to change than anything else.
 
Theres really no hard-and-fast rule for domain names, its left up to the organisation to make the best determination for their environment.
 
G.
 
 
----- Original Message -----
Sent: Thursday, July 24, 2003 12:21 AM
Subject: [ActiveDir] Domain Naming Best Practices

All,
 
I have been asked by managment to defend my domain naming standard.  I am using geographical locations such as AMER (N&S America), EAME (Europe, Africa, & Middle East), and APAC (Asia Pacific & Australia).  I am being asked why can't we use generic names such as Region1, Region2, and so forth.  I can say all I want, but I need some outside evidence to back me up or if I am totally off base, I'll take some recommendations.
 
Thanks for the anticipated help.
 

Scott Morley

MCSE 2000/4.0, Exchange 2000/5.5, MCT, CCNA, CNE, CNI
Senior Systems Engineer/Architect
Global Messaging Services, Starwood Technology Center
Starwood Hotels and Resorts, Worldwide

Phone: 781-348-7120

Learning is not compulsory... neither is survival.
- W. Edwards Deming
 

 

 
This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged.
The information is intended only for the use of the individual(s) or entity named above.  If you are not the intended recipient, be
aware that any disclosure, copying or distribution or use of the contents of this information is prohibited.  If you have received
this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.

Reply via email to