6.7. Dynamic Host Configuration Protocol (DHCP)

In the beginning of TCP/IP-based networks, managers characterized every node's location in a content record or dialog box. From that point on, the location was altered unless somebody transformed it. The issue was that executives every so often would erroneously put clashing locations into different nodes on the network, creating a network's form of disorder. To determine this issue and to make it simpler to allocate TCP/IP addresses, an administration called Dynamic Host Configuration Protocol (DHCP) was developed.

DHCP services keep running on a DHCP server, where they control a scope of IP locations called a scope. At the point when nodes associate with the network, they contact the DHCP server to get a relegated address that they can utilize. Addresses given by a DHCP server are said to be leased to the client who utilize them, which means they stay assigned to a specific node for a set timeframe before they terminate and get to be accessible for another node to utilize. Frequently, lease periods are for only a couple of days, however network administrators can set whenever period they need.

You ought not to utilize DHCP for nodes that give network services, especially for servers that give services over the Internet. This is on the grounds that changing a TCP/IP location would make dependably interfacing with those PCs outlandish. Rather, utilize DHCP to bolster client workstations that don't have to host services for different nodes.

You may think a host is a server, and in some networking contexts, you would be correct. In any case, in the language of Internet names and addresses, each PC that has an IP location is known as a host, therefore the name, Dynamic Host Configuration Protocol. Recollecting that each PC is known as a host is especially imperative in the UNIX and Linux universes, where the term is a great deal more normal than in the Windows or Macintosh universes.