Firstly, a DHCP server is needed which distributes the IP addresses. This machine will serve as a base for all DHCP requests and must also have a fixed IP address. Therefore, on a network there can only be one machine with a fixed IP address, the DHCP server.
The basic communication system is BOOTP (with UDP frame). When a machine is turned on, it has no information on its network configuration, and there is nothing special that the user needs to do to find an IP address. In order to do this, the technique used is the broadcast: to find and talk with a DHCP server, the machine will simply send a special broadcast packet (broadcast on 255.255.255.255 with other information such as the type of request, the connection ports, etc.) over the local network. When the DHCP receives the broadcast packet, it will send back another broadcast packet (do not forget that the client does not obviously have the IP address and that therefore cannot be connected to directly) containing all the information required for the client.
It could be believed that one single packet is enough for the protocol to work. In fact, there are several types of DHCP packets likely to be issued either by the client for the server(s), or by the servers to a client:
DHCPDISCOVER (to locate available DHCP servers)
DHCPOFFER (server response to a DHCPDISCOVER packet, which contains the initial parameters)
DHCPREQUEST (varied request from the client for example to extend its lease)
DHCPACK (server response which contains the parameters and IP address of the client)
DHCPNAK (server response to indicate to the client that its lease has expired or if the client announces a bad network configuration)
DHCPDECLINE (the client announces to the server that the address is already in use)
DHCPRELEASE (the client releases its IP address)
DHCPINFORM (the client requests local parameters, it already has its IP address)
The first packet issued by the client is a DHCPDISCOVER type packet. The server responds with a DHCPOFFER packet, particularly in order to submit an IP address to the client. The client establishes its configuration and then makes a DHCPREQUEST to validate its IP address (a broadcast request since DHCPOFFER does not contain the IP address). The server simply responds with a DHCPACK with the IP address for confirmation of the allocation. Normally, this is enough for the client to obtain an effective network configuration, but it can be longer or shorter according to whether the client accepts the IP address or not.
A DHCP client will receive an Automatic Private IP Addressing (APIPA) address when it fails to obtain an IP address from a DHCP server after several attempts. This typically happens when there is no DHCP server available on the network or if the server is unreachable. APIPA assigns an IP address in the 169.254.0.1 to 169.254.255.254 range, allowing for local communication on the same subnet.
The client IP address, the clients host name, the port address to use during communication
The broadcast message is forwarded using an IP helper address, The client broadcasts to find the server
Inverse domain is used to map an address to a name. For instance, if a server receives a request from a client and this server has only the ip addresses of the clients in its list then the server needs to find out if this client is on its authorized client list. In order to determine if the client is on the authorized client list,server asks its resolver to query to the DNS server to map an address to name. And this type of querys are called inverse query(pointer query -PTR).
Inverse domain is used to map an address to a name. For instance, if a server receives a request from a client and this server has only the ip addresses of the clients in its list then the server needs to find out if this client is on its authorized client list. In order to determine if the client is on the authorized client list,server asks its resolver to query to the DNS server to map an address to name. And this type of querys are called inverse query(pointer query -PTR).
A DHCP server will privide a client with a valid IP address for the network for which the DHCP server is providing a service.Where there is no DHCP server the IP address for a client must be set manually. When doing this care must be taken to ensure that two IP addresses are not set the same on the network.
show mac address table
When a client specifies a domain name to contact a server, the first step is a DNS (Domain Name System) lookup to resolve the domain name into an IP address. Next, the client establishes a connection to the server using the resolved IP address, typically through the Transmission Control Protocol (TCP) for reliable communication. Once connected, the client sends an HTTP request to the server, which then processes the request and responds accordingly. Finally, the client receives the server's response, completing the interaction.
DHCP Accept is not a standard term in networking, but it may refer to the process where a DHCP client accepts an IP address and configuration parameters assigned by a DHCP server. During DHCP communication, after the server offers an IP address, the client sends a DHCP Request to accept that offer, and the server responds with a DHCP Ack to confirm the lease. This process enables devices to automatically obtain network settings without manual configuration.
In a LAN (Local Area Network), the two terms that describe the data requester and data provider are: Client → the device/user that requests data or services. Server → the device/system that provides or shares the requested data. Together, this is called the Client–Server model.
When you enter a URL into your browser you are directing your computer to connect to a server that is listening at the corresponding ip address, which will then send you the HTML that makes up that web page. Your computer is a client connecting to a server.
The client sends a DNS query, typically a recursive query, to the DNS server when it seeks to resolve a domain name into an IP address. In this query, the client requests that the DNS server either provide the requested address or continue querying other DNS servers on its behalf until the information is found. The client can also send iterative queries, where it asks for information and expects the server to provide the best answer it has, potentially directing the client to other DNS servers for further information.