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

add new domain controller on remote side

i Need to install a new Domain Controller on a remote side, connected via site 2 site VPN.
here is the plan (A is the existing network, B the remote network)
- install new Server on B, use DC from A as ist Primary DNS Server
- join Server on B to existing Domain
- create new AD site and subnet in active Directory
- promote Server on B
- Change Primary DNS on Server B to itself and secondary to Server on A
- add Server on B as secondary DNS in A

is there anything else that Needs to be done to make this working properly (e.g. reverse DNS zones, Delegation, ...)

Thanks for any advise
0
mwiesauer
Asked:
mwiesauer
  • 3
  • 2
1 Solution
 
Will SzymkowskiSenior Solution ArchitectCommented:
It is pretty basic procedure. All above looks correct. Just make sure that you have DHCP at your remote site as well. Configuring this role on the DC in the remote site is also fine.

Will.
0
 
mwiesauerAuthor Commented:
thanks, so no DNS Delegation or reverse zones needed!
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
DNS delegation happens automatically when you are using AD-integrated zones, after promoting a domain controller. If you have any Zones that are not AD-integrated then you will need to add delegation manually.

Reverse Zones should also be created if they are not already. If they are delegation will also be automatic if it is an AD-integrated zone.

Will.
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
RizzleCommented:
Chaps

Quick question here, cant you only have one DNS server as your primary in a domain?

In terms of DHCP. wouldn't have the primary DHCP at site A then configuring the DHCP at site B in like a Hot Standby/load sharing be ideal?
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
From my experience it is not recommended to do DHCP broadcast over a WAN circuit. It is possible but i would not do this because now you have WAN as a dependance for DHCP.

cant you only have one DNS server as your primary in a domain?
This is configured on the client. You have Primary DNS and Secondary DNS servers that the client will use. If the primary is not reachable it will use the secondary (after a timeout period happens).

It is recommended to have the housing site be the primary DNS pointer for the DHCP clients and have the DNS IP for the secondary DNS entry for the remote site.

Do not get confused with Remote Site.

E.g...
Site A
DC/DNS IP = 192.168.0.1
Clients Site A DNS = Primary 192.168.0.1 Secondary 192.168.1.1

Site B
DC/DNS IP = 192.168.1.1
Clients Site A DNS = Primary 192.168.1.1 Secondary 192.168.0.1

This way if the DC/DNS is not responsive for whatever reason it will query over the WAN circuit to get DNS.

Will.
0
 
mwiesauerAuthor Commented:
makes sense to me! DHCP is not an issue..
Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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