DNS and DHCP can make a system administrator's life simpler and easier. Fortunately, the protocols are so flexible that they can be implemented either together or separately depending on the size and configuration of your enterprise network. So whether you have 5 or 5000 computers in your network this would be justifiable action because of the following reasons:
Looking up IP addresses can be a nightmare if you have more than a couple to remember If you have network-enabled printers, unless you lock the address, it will change every time you disconnect the printer from the network. This can be extremely frustrating for the users. If you have more than a small number of machines, then you should be looking at implementing DNS in addition to DCHP.
There are a number of ways to implement DNS in-house depending on the specifics of the company computer systems architecture. The choice depends on the available skills in your shop and the network configuration. One nice thing about implementing DNS is that once it is set up, it pretty much runs without much need for human intervention. That means that if you hire a consultant to do the initial configuration, you only need to maintain the service with a minimum of skills and resources. I found two choices for configuring the service using Microsoft Active Directory or (the newest possibility) purchasing a DNS/DHCP service appliance. Whatever implementation you choose, once it is configured, the best DNS/DHCP server reliably blinks and serves IP addresses and host names on your network at minimal cost and productivity.