0

This question already has an answer here:

I wanted to know the use of having multiple domain controllers for one domain And some more questions related to it are:

If there are multiple domain controllers can computer information in one domain controller visible to others? If there are two computers having a saame domain name shown as xyz in control panel is there a possibility of them to be in a different domain?

PS:I am new to AD and could not find straight forward answer.

marked as duplicate by Chris McKeown, Ward, mdpc, Michael Hampton Aug 24 '13 at 17:04

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

migrated from superuser.com Aug 23 '13 at 19:31

This question came from our site for computer enthusiasts and power users.

5

The primary reason for having multiple domain controllers is for fault tolerance. They will replicate the Active Directory information between them and can provide services if the other is unavailable.

3

Having multiple DC's is a best practice standard. You should always have at least 2 DC's to safe guard against one going down. If all you had was one, and it went down, there'd be nothing for your objects to authenticate to.

It's very common for environments to have more than 2 DC's as well. There are a lot of factors which go into deciding if a new DC is needed. For example, you may have more than one physical location and want to have DC's on each site. When DC's enroll into an existing domain, they're able to find each other and share information.

You can also have multiple forests (groups of domains) linked together. You can do this by attaching them to the same "site" (using a directory manager like IDM) or by establishing trusts between the separately configured domains. However, most needs are satisfied by simply creating a new OU in an existing forest. You'll usually see multiple domains configured together as part of mergers and migrations or because someone had an older Novell IDM infrastructure.

Given the freedom which Virtual Machines offer, I'd highly recommend you get something like virtualbox and download a release preview of Microsoft Server 2012 R2 (currently free) and build your own domain. Feel free to play around and readh through Microsofts online tech databases.

http://technet.microsoft.com/en-us/library/cc786438(v=ws.10).aspx

  • Nitpick: A Forest is not a Domain. A Forest contains Domains (the first one being the Forest Root Domain). You seem to be using the word Forest and Domain interchangeably in your answer. – Chris McKeown Aug 23 '13 at 21:04
  • I was intentionally writing globally. When you provide domain services as a service you start talking of "forests" in the very plural sense. – Colyn1337 Oct 11 '13 at 22:03
  • 1
    Not sure I understand. Domain != Forest, whatever the volume of domains you're talking about. Maybe edit your answer to clarify? – Chris McKeown Oct 11 '13 at 22:13
  • @ChrisMcKeown Perhaps I mistook where you saw the issue... Which part did you think I was using Forest when I should have been using Domain? – Colyn1337 Oct 11 '13 at 22:20
  • 1
    "You can also have multiple forests (domains) linked together" - to me that looks as if you're using the term interchangably. I'm sure that's not what you intended based on your comments, but it may confuse others. – Chris McKeown Oct 11 '13 at 23:00