asked on

Setting up a geographically distant domain controller and DNS using Microsoft server technologies

I wish to set up a domain controller and DFS on a system that is located 1000 miles south of my primary server installation.

I am wondering a few things:
1) What the prerequisites are in terms of the DNS "zone" the server will fit into? Does it need to be a "public" zone or set up in a particular way?

2) Does DFS replication demand that the replicate-ee be a DC?

3) Are there any common connectivity failures I should watch out for to make this work?

Thanks!

Brian Pierce

The fact that the machines are geographically seperate makes little difference, assuming you have physical connectivity between the sites. There is no need to create a new domain and DNS is no different, you can use AD Integated DNS (the default) by simply insalling DNS once you have promoted the the new DC, DNS will then replcate with Active Directory.

What you do need to do is use a different subnet for each location, define the subnets in AD Sites and Services and create a new site for tthe new romote location, and then assocuate each site with its subnets(s).

You sould also make the new DC a global catalog server, once ith new DC is placed in the remote site all the clients in the site should be configured to use this as their preferred DNS server, they will then authenticate with this DC.

kennethfine

ASKER

Thanks, KCTS.

If the DC at site A is behind a firewall, how will it communicate properly with the DC at site B? Is this a simple q of port forwarding being set up on the firewall, or does the communcation happen by some other means?

ASKER CERTIFIED SOLUTION

Brian Pierce

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kennethfine

ASKER

Ah, great. Thanks for the help, this is exactly waht I was looking for, KCTS.

kennethfine

ASKER

many thanks KCTS!