DHCP is widely used in corporate settings, by internet service providers and by proxy servers such as Microsoft's Internet Connection Service.
The major technical hurdle that DHCP must overcome is that lacking an IP address initially, a DHCP client can't use the TCP/IP packet to negotiate an address lease. Instead, it must send a special DHCP Service request that includes the client hardware address. DHCP servers respond to the request. The client then selects a DHCP server and requests an IP address which it uses. The DHCP server can provide additional information at the time it provides the IP addresses including addresses of Domain Name Service servers, WINS servers, etc. DHCP provided addresses are leased. The lease can be terminated by either the server or client and will expire after a time in any case.
Because DHCP provided addresses can and do change, it is difficult or impossible to use DHCP to provide IP addresses to servers that must be reached using the Internet. Conceptually at least, local DHCP assigned addresses can be found using a local Name Server. But potential external clients can't find those addresses using global Domain Name Servers. Lease periods are generally a few days. Renegotiation is undertaken early -- halfway through the lease period. The lease period is a compromise between a desire not to disrupt IP traffic by changing the address and the need to reuse IP addresses fairly promptly when a client shuts down or negotiates a new lease with a different server.
DHCP requests and responses can be propagated through routers and switches provided that the latter are configured to forward the closely related BOOTP protocol. BOOTP is a protocol used to bootstrap an operating system onto a (usually diskless) computer via a network.
Return To Index Copyright 1994-2008 by Donald Kenney.