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

We are planning the following AD topology:


The main root domain controllers and domain controllers will exist in the same head office datacentre location: will be on a different subnet (and country) all together.

Do the head office domain controllers (the root and child domain) also need to be on a seperate subnet? I assume they do, unless we provide some kind of unique netbios names (and if so any recommendations for naming the above)?

share|improve this question
I see your issue when naming the DC's the same. Couldn't you just name them differently? – MichelZ Jul 18 '12 at 7:16
up vote 1 down vote accepted

This may not be a technical answer, but I personally always prefix server names with some form of site code. It can, admittedly, make the FQDN a little unweildy especially if the domain name is similar to the prefix, but perhaps something like this:

Head Office = HO-DC01 & HO-DC02

West Coast = WC-DC01 & W-DC02

East Coast = EC-DC01 & E-DC02

So, you end up with, along with and

With the added benefit that everything still makes perfect logical sense (And works!) even when not referencing using a FQDN.

share|improve this answer
this is nice, DCHO001, DCWC001, DCEC001. Thanks for pointing me in a direction i can work with, – g18c Jul 18 '12 at 11:35

they can coexist on the same network segment

share|improve this answer
Even with the same name? That's got to get you in some kind of trouble, even if the netbios name is not used as frequent as in NT? – MichelZ Jul 18 '12 at 7:27
you're right - name should be unique. – pQd Jul 18 '12 at 7:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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