Birmingham mumbai

[
 284 
]
Active and previous DHCP leases are stored in the 
/var/lib/dhcp/dhcpd.leases
 file, 
and a typical lease entry in that file would look similar to the following:
lease 192.168.1.138 { 
  starts 0 2020/10/05 16:37:30; 
  ends 0 2020/10/06 16:42:30; 
  cltt 0 2020/20/06 16:37:30; 
  binding state active; 
  next binding state free; 
  rewind binding state free; 
  hardware ethernet 32:6e:92:01:1f:7f; 
} 
When a new device is added to your network and receives an IP address from your 
new DHCP server, you should see the lease information populate that file. This file 
can be incredibly helpful, because whenever you connect a new device, you won't 
have to interrogate the device itself to find out what its IP address is. You can just 
check the 
/var/lib/dhcp/dhcpd.leases
 file. If the device advertises its hostname, 
you'll see it within its lease entry. A good example of how this can be useful is 
connecting a Raspberry Pi to your network. Once you plug it in and turn it on, you'll 
see its IP address in the 
dhcpcd.leases
 file, and then you can connect to it via SSH 
with the IP without having to plug a monitor into it to find out which IP it was given. 
Similarly, you can view the temporary IP address of a new network appliance that 
you plug in so that you can connect to it and configure it.
If you have any trouble setting up the 
isc-dhcp-server
 daemon, double-check that 
you have set all the correct and matching values within your static IP assignment, 
as well as within your 
/etc/dhcp/dhcpd.conf
 file. For example, your server must be 
within the same network as the IPs you're assigning to clients. As long as everything 
matches, you should be fine and it should start properly.
Next, let's take a look at another important service within a network—DNS.