|
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.
|
- [ActiveDir] Domain Naming Best Practices Morley, Scott
- RE: [ActiveDir] Domain Naming Best Practices Glenn Corbett
- RE: [ActiveDir] Domain Naming Best Practices Roger Seielstad
- RE: [ActiveDir] Domain Naming Best Practices Bryan Schlegel
- Re: [ActiveDir] Domain Naming Best Practices DAVID S. CARTER
- RE: [ActiveDir] Domain Naming Best Practices Morley, Scott
- RE: [ActiveDir] Domain Naming Best Practices Morley, Scott
- RE: [ActiveDir] Domain Naming Best Practices Roger Seielstad
