2 Domain Controllers on the Same Network - Microsoft Q&A (2024)

FAQs

Can you have 2 domain controllers on the same network? ›

As long as all the addressing is static so the members will use the correct domain controller / DNS it should work.

Each domain in Active Directory is identified by a (DNS) Domain Name System domain name and requires one or more domain controllers. If your network requires more than one domain, you can easily create multiple domains.

Even more important, having at least two DCs in each domain provides redundancy: If one DC fails, the other one can step in, ensuring that there is no interruption in core Active Directory services like autenthication and authorization.

Having two domains pointing to the same website is definitely feasible and can greatly benefit your business. Of course, there are alternative options, like using subdomains or subfolders. However, if you believe having separate domains point to your website is the right move for you, then go for it!

If you want to host multiple websites on one server, it is possible, as the server's IP is dedicated to it. This means that you can configure the server to serve different domains or subdomains with different content, a practice known as virtual hosting.

One laptop can only have one domain, when you join CompanyA, you must exit CompanyB. Simple and best way is to partition the hard drive and install the OS on each partition. Then set each OS to connect to a single domain. When Booting up, select the OS relavent to the domain you want to connect to.

Typically you would want two domain controllers, one acts as a back up and should be physically separate from the other, i.e. Don't have both in the same VM Host. If you can get remote offices to authenticate on a centrally located DC, then all the better because you will be using less hardware and minimize management.

You should have at least two per AD site. There extensive amount of MS documentation on planning and placement, the official recommendation is probably buried somewhere there. In case one DC fails, you'll have something to provide services from, at least up to the point you can recover back to a stable state.

Domain services, such as those that domain controllers provide, are just one part of Microsoft Active Directory. A domain controller can operate as a single system, but they are usually implemented in clusters for improved reliability and availability.

Also Below are the commonly required ports to communicate with DCs. UDP Port 88 for Kerberos authentication UDP and TCP Port 135 for domain controllers-to-domain controller and client to domain controller operations. TCP Port 139 and UDP 138 for File Replication Service between domain controllers.

Is it enough to have one domain controller? ›

Decide how many virtualized domain controllers you need

If the answer to this question is one domain, then your environment might only require only one or two domain controllers (see below for redundancy). If you need multiple domains, then you will need at least one domain controller per domain.

Non-availability of resources for any of the DSfW services might lead to domain malfunction and slowness at the client workstation. For an enterprise with user base up to 2000 users per domain and associated resources such as user workstations and shares, you must have at least two domain controllers.