AD DC setup in perimeter network

Home Forums Microsoft Networking and Management Services Active Directory AD DC setup in perimeter network

This topic contains 3 replies, has 3 voices, and was last updated by  Techie 10 years, 12 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts

  • Techie
    Member
    #128277

    I’m trying to determine the best method to setup two Active directory domain controllers in our production environment. Our main concerns is having redundancy and scalability.

    We have the standard perimeter network setup, a DMZ with web servers and a private network with database servers. Each network uses a different subnets separated by a Ciscio firewall.

    We have a server connecting to a SAN in the DMZ which we need to cluster to provide redundancy. We also eventually want to cluster our Database servers. This requires that both networks to have access to the DC. In order to provide redundancy we want to install two DC.

    Option 1:
    Our original intent was to put both DC’s on the private side and have the DMZ servers connect through the firewall, similar to how web servers connect to the database servers.

    Option 2:
    I recently read that Microsoft recommends putting a DC in both networks and build a trust over the firewall to reduce cross network AD traffic.

    Which options would be best or is there a better option I’m missing? Option 1 requires more AD traffic to go through the firewall and I’m not sure if there a DNS issues as both subnets use diferent IP ranges. However to keep redundancy in Option 2 wouldn’t this require two dC in each network requiring four DC in total? Also wouldn’t this present security issues?

    Any insight into this setup wold be appreciated. Thanks.


    James Haynes
    Member
    #251601

    Re: AD DC setup in perimeter network

    DC setup in perimeter network < —:shock:

    i would advise against that… but thats your call.

    i would think that you could utilize two network cards,…

    or just set up the NATs and policies correctly.

    i dont have a quick answer, i just dont htink its a great idea to pout your DCs in a DMZ.


    Techie
    Member
    #308936

    Re: AD DC setup in perimeter network

    Thanks for your response; we have decided not to put the AD server into the DMZ. We’re trying to find the right NAT and policy settings, so far no luck.

    I assume by utilize two network cards you’re referring to connecting AD server directly with the cluster server. Doesn’t this present a security issue as the DMZ server would have complete access to the AD server?


    guyt
    Member
    #193619

    Re: AD DC setup in perimeter network

    Just wondering whether you can get away without authenticating directly against AD, but using some sort of proxy mechanism similar to a one described here: http://forums.petri.com/showthread.php?t=10879

    As of DMZ-ed DCs, those can not be behind DNAT (SNAT is ok) and have to be fully routable from the internal network point of view.
    For port requirements see:
    http://support.microsoft.com/kb/832017
    http://support.microsoft.com/kb/224196

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.