• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1536
  • Last Modified:

Domain Controller - DR design best practices

Hello there;

OK So we are setting up a new environment for a Client and we want to make the best design plan possible.

Site 1 (left):  Production environment   (2 DC )

AD1: DHCP, DNS, CG & Holds all 5 FSMO Roles


Site 2 (right): DR Site (1 DC)



Best design plan for DHCP,DNS,CG,FSMO, domain design "i.e child domain"

After hours of reading I reached a conclusion that we don't really need to make any changes to  FSMO Roles & we don't need to have a child domain on the DR site.

- Both sites "Production and DR" can be on the same domain in one single forest.
- First domain controller will be hosting all Five FSMO roles and there is no need to transfer or  or seize it.

If AD one goes offline and no hope of getting it back online:

-  seize FSMO roles to AD2

If the hole production site goes offline and there is no hope of getting it back online:

-  seize FSMO roles to DR AD

- Split the DHCP pool between 3 servers

- Make DNS available on 1st DC and DR DC

My question is: what do you think about this setup ?

  • 3
  • 2
  • 2
  • +1
3 Solutions
i would say GOOD design .. let us have the different Active directory sites for both physical sites
configure replication interval as less as 15 minutes

and have then different subnets and configure DHCP servers for 80-20 rule

atigrisAuthor Commented:
OK very good, How about DNS ? what is your though on that ? Thanks
I use the same setup betwen our core prod site and our remote DR site.
I'm assuming you have two different subnets with associated AD sites.
Tested successfully including Exchange failover using Doubletake.
Straight forward and simple to support.
AD replication is pretty good for what it does.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Child domains just add extra complexity. If you need different domain password policies, or you want completely separate administrators to be delegated control of a child company, then that might be of value, but otherwise it is complexity that doesn't buy any value.

I think your design looks good - KISS.
atigrisAuthor Commented:
- I could create 2 sites this way the  replication dose not have to be over the hole domain.
- each site on it's own subnet.
- NO need to use child domains.
- DHCP use 80-20 rule & use SuperScope to simplify DHCP administration.
- Primary and Secondary DNS server on the production site and one DNS on the DR site.
- NO need to change  FSMO roles - all roles can be on first created machine.
- All machines can be Global Catalog server.

atigrisAuthor Commented:
no complete answer was provided.
about dns
you already have inclused a that in the ADC on the DR site
You only need superscopes if you have a multi-net.

Otherwise your plan looks good to me.


Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now