Software·43,854 discussions

DNS/DHCP Implementation

Locked

Hello:

In a 10-server environment that is running Windows 2000 server with 2 NT servers, in what order should DNS and DHCP services be implemented? Should all services be implemented on one server or different servers? Can more than one DNS Server be configured when the Active Directory is set up, and can DHCP be configured to automatically update DNS records?

I know that this is a bit involved, but we are having this debate at work and I would welcome the input from the Techrepublic community

Thanks,

Topic

DNS/DHCP Implementation

In reply to DNS/DHCP Implementation

Answers to your questions really depends upon the design topolopy, # of clients, # of segments, security design and so forth. A 10 server environment is a rather “large” environment. I’ll assume that you have decided to segregate workstations into groups and connect each group on the LAN via a router. Then a breakdown would be something along the lines of , : a PDC with AD and a BDC. A seperate Web server, with a backup and 6 groupings of 35 to 50 computers each [each group connected to the LANvia a router. You’ve decided to use DHCP cuz a static routing for 150 or so workstations is a pain in the butt to do. Therefore DHCP servers will be required on each routed segment. That would take care of the 10 servers. Still kinda overkill on the# of servers.

Finally Automatic update of DNS records can be configured if required.

DNS/DHCP Implementation

In reply to DNS/DHCP Implementation

Poster rated this answer

DNS/DHCP Implementation

In reply to DNS/DHCP Implementation

Whether you implement DNS and DHCP on one server depends on how the workload is spread across your servers. Normally a Domain Controller will be your Primary DNS server as it will contain the master record of the Active Directory. You can setup SEcondary and Caching DNS servers, if you have a very large network requiring lots of regular DNS queries.(even in and AD environment).
Yes DHCP can be configured to automatically update DNS.

You do not say how many Workstations you have running in your environment, but if you have less that 100 then you should be okay with having DNS and DHCP on one server (as long as it is not a database server or an exchange server, or something that is very heavy on the server)

DNS/DHCP Implementation

In reply to DNS/DHCP Implementation

Poster rated this answer

DNS/DHCP Implementation

In reply to DNS/DHCP Implementation

I am assuming you are still NT4 DC’s are going to migrate, but you don’t indicate number of clients. I run 26 servers and 120 w/s, plus 6 other sites with varying w/s and 4-8 servers at each. We started with NT4 domain + BDC, and DNS on member server. Upgraded DNS to 2000 to give Microsoft recomended DNS server (dynamic updates, AD integration). If your PDC runs DNS, then it’ll update automatically of course. Then upgraded our PDC to 2000. Upgraded DHCP server to 2000 and authorised (need AD/DNS to do that). Then created new server and promoted to DC with AD integrated DNS. After settling period, we now run two DC’s at each major site, and each DC runs AD integrated DNS . DHCP is on a server with Print Services and WINS. We don’t have a “heavy” DNS requirement and all seems to behave. I don’t run any other services on the DC’s as they are too important to the WAN. I pretty much think we have it about right, but it depends on what other loads are on your servers. You can, of course also run two DHCP servers by splitting the scope if you want redundancy. Some one already answered your other question.

DNS/DHCP Implementation

In reply to DNS/DHCP Implementation

Poster rated this answer

DNS/DHCP Implementation

In reply to DNS/DHCP Implementation

This question was closed by the author

[Author]

Replies