|
I am setting up a new forest and I want to use a separate DNS server. I have setup tons of AD servers but never used a separate DNS server (I always had AD set it up on the AD server). I am wondering, should I setup the AD servers first then the DNS server, or setup the DNS first then the AD servers?
Thanks |
|
Install the AD roles and it should install and provide a basic DNS configuration for you. AD REQUIRES a DNS server with the ability to use and update Service records - if you don't have one in place, AD installs it when AD itself is installed.
If you aren't familiar with the process, I would STRONGLY recommend you LEARN it first - setup a test domain or two before implementing the actual production one. Better still, if you want to ensure you get it right, consider hiring someone professional to get it done right the first time. I have several consultants who hire me to migrate their domains to to new versions of AD while they cover the everyday support needs. |
|
Sorry, maybe I wasn't clear. I am very familiar with setting up AD and I know that it will setup DNS for you. I don't want it to. I want to setup DNS on a separate box and have AD use it for DNS.
|
|
The system will have a lot of users and I want to take some of the load off of the AD servers by having DNS and DHCP on a separate box.
|
|
How many thousands?
DNS is really a lightweight service as is AD for most environments. Have you looked at the processor utilization and network utilization on your existing server(s)? Honestly, I used to run an AD for about 1000 users and we had 3 DCs that were BARELY used because the functionality has minimal resource requirements and if you're installing new multi-core servers, it really should be a non-issue. Going forward with this plan will more likely create more problems than it solves. |
|
OK, I will take your advise and set them up as usual.
Thanks |
