To use this protocol, the network administrator needs to set up a DHCP server and configure BOOTP relay agents on links that do not have a DHCP server. Advance planning can reduce DHCP load on the network.
For example, one server can be configured to handle all your clients, but all packets must be passed through it. If you have a single router between two large networks, it is wiser to place two servers in your network, one on each link.
Another aspect to consider is that DHCP implies a pattern of traffic. For example, if you set your default lease time to fewer than two days and your machines are powered off for the weekend, Monday morning becomes a period of high DHCP traffic. Although DHCP traffic does not cause huge overhead for the network, it needs to be considered when deciding where to place DHCP servers on a network and how many to use.
After enabling DHCP to get the client on the network, a client has
no requirement to enter anything. The DHCP client,
reads the dhcpcd.ini file, which contains information
on logging and other parameters needed to start running. After installation,
decide which method to use for TCP/IP configuration: minimum configuration
or DHCP. If DHCP is selected, choose an interface and specify
some optional parameters. To choose the interface, select the keyword any,
dhcpcd to find the first interface that works
and use it. This method minimizes the amount of input on the client side.