asked on

Adding new 2008 server to network, want it to be AD and DNS controller

Hello all,

I currently have a 2003 network, with two AD servers (A & B). I in the process of retiring A, and have a new 2008 R2 server to go in its place. Server A is also currently a DNS server (and it was the first one implemented).

I have done the ADPrep work to make the forest/domain ready for the new 2008 server. I want this server to do two things on my network:

1) An AD controller
2) the main DNS server on the network.

I want to confirm the best way to install these roles on the new 2008 machine. Should I install DNS first, and then install AD? What about DNS-Aware AD? Does that fit in here anywhere? Anything else?

Thanks,

Tony

ASKER CERTIFIED SOLUTION

Mike Kline

membership

This solution is only available to members.

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

Start Free Trial

Brian Pierce

If you have AD integrated DNS - which is the default, then its best to run DCPROMO first, then simply add DNS later - it will populate automatically when AD replicates.

As for being the 'main' DNS server, I'm not sure what you are getting at, the AD Integrated DNS, then all DNS servers are equal, all can answer DNS queries, and unlike traditional DNS all are update-able 'primary' DNS servers.

Sajid Shaik M

join this new domain to existing frest as additional dmain controller ..... after complete process.... now either u can seize or u can transfer fsmo roles....

see the following links...

http://www.petri.co.il/transferring_fsmo_roles.htm

htp://www.petri.co.il/seizing_fsmo_roles.htm

or u can do safe side..... after joining additional domain to existing forest remove this server and seize the FSMO and make this server as DNS sever ... thats it.. check and let me know ps

all the best