While this question is better answered on an AD list, or even WinNT-L, I'll bite.
It depends on the size of your network. It's generally recommended, on large networks, to separate DNS/DHCP from AD servers, because of logons. Let's say your company of 10000 all log on at 8am EST. We'll, during logon their querying AD for authentication and GP settings (among other things), their querying DHCP to ensure their IP is still okay, and their registering their IP with DNS. All of these things happening at once on the same server is "a bad thing". Now, I have an environment of 250 PCs, all of which log on at different times of the day because of our roaming student population. I have AD, DNS, and DHCP all on the same machine with no worries. Steven --- Steven Dickenson <[EMAIL PROTECTED]> Network Administrator The Key School, Annapolis Maryland -----Original Message----- From: Bridges, Samantha [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 8:59 AM To: Exchange Discussions Subject: DNS & DHCP Question Is it not recommended to run DHCP and DNS services on the Root server in a Windows AD setup? I will be upgrading our domain to AD next week and wonder if I should setup another server or two for the DCHP services and DNS services. What should the root server be capable of handling? Should it be just a root server and that's it? What are your thoughts on where to "put" these services. Thanks forum! Samantha _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
