4 replies
by rubyvida1 Accepted solution
by dumphrey Accepted solution
DNS does not need active directory. When you boot up the second server 2003, the server config wizard should pop up, you can use that to set up the server to host DNS.
You do not need to make the server a domain controller, though it should be a member of the domain.
Integrate it with AD.
Now Do you want this to be a primary (read/wrote), redundant dns server or a redundant secondary server (read only)?
See if this helps any:
http://www.windowsnetworking.com/articles_tutorials/Making-DNS-Service-Fault-Tolerant.html
by kjell_andorsen Accepted solution
You certainly don't have to install active directory on the second server as it Server 2003 would allow you to just set it up as a secondary server. However, if you only have one domian controller currently I strongly reccomend you set the second server up as a Domain Controller just for redundancy.
In my opinion having just a single DC is asking for trouble, what happens if that server crashes? Having at least 2 DCs is definitely considered best practice.
If you do decide to promote the second server to a domain controller there's not that much you need to worry about as long as you have a simple AD structure. There are numerous technet articles on how to configure replication of both AD and DNS. If you have problems finding them let me know.
by rubyvida1 Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending