Discussion Locked

Location of AD, DNS, DHCP

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
Is it recommended to have Active Directory, DNS and DHCP installed on the same server? Can I put AD on one server and DNS/DHCP on another server. Would this affect performance? I have about 150 users that will be logging on to the domain.

Thanks,
Chris

2 replies

by Member 32001153

Your main AD server should have DNS on it. DHCP is not a requirement, AFAIK.

AD and DNS work closely together and having DNS no a different server adds additional chances for failure.

Performance would be minimized by having them together. DHCP, on the other hand, is not a big issue, depending on how long you set your leases.

Querying for a DHCP server obtaining an address is not a big deal compared to naming an authentication.

Let's also be clear on something else. An AD server with DNS/DHCP, etc. should not a file server. The Microsoft domain models for client/server networking do not lend themselves to the all eggs in one basket approach.

by chris..

Well you should have at least two DC's to begin with. Also note that AD is not a service like DDNS and DHCP ... honestly there is nothing that should prohibit you from having all of that on the DC.

Default configuration for 2K DHCP leases is 8 days with a 4 day half-life check on the lease. DNS... such a light traffic load that it won't matter.

Depending on available resources though, it is best practice to place all three of those services on seperate servers, considering the user load your network has, I wouldn't worry about it if your short on servers. Then again a simple desktop class system can be dedicated to runnng DNS and DHCP and still remain just a member server.

This discussion is closed to new replies.