Currently, we have one site Default-First-Site - Gross default name, I know. We have plans to add a remote site. The the main site is a that is split into dozens of smaller subnets. The remote site is connected to us by a MAN. Essentially, it is a 20Mbps bidirectional link between the main site and the remote site. The remote site is, which is obviously in the range.

I am setting up DFS, a RODC, and a few other things for that remote site and have now set up a site for in in Active Directory so that the clients will connect to the appropriate DFS member and use the RODC that is on-site. We'll call this site Remote-Site for this question. In AD Sites I defined the as belonging to Remote-Site. I have no subnet definition for Default-First-Site.

My question is, do I need to define as the subnet for Default-First-Site, or will anything not in Remote-Site assume it is part of Default-First-Site? Also, if I define as the subnet for Default-First-Site, will that screw up anything in Remote-Site, since is obviously a subnet of


You can have overlapping subnets in AD and they'll behave as you'd expect. A less-specific "catch all" subnet, like, will be selected by clients unless a more specific subnet, like, is defined in the Sites container.

So, define the subnet and associated it with your Default-First-Site-Name site (which you can rename to be less ugly), and then create addt'l sites and subnets for the remote locations with more specific subnets inside specified.

You can read a more in-depth article if you want more details, but based on your question I think you already understand what you're looking for and your expected behavior is the product's designed behavior.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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