The exchange with a DHCP server (that is down at the very moment) is nothing extraordinary: - Request - Discover - Discover .... - Discover
(133 seconds passed) and stop. Of course the client starts using formerly assigned IP address of 10.1.1.92 .
When the date changes at midnight so the 4th of February starts, the client starts sending DHCP Discovers again. First couple questions are: Is this expected behaviour? If not so, why it stopped sending Discovers ?
I was curious and manually modified the lease to expire not the next day but in 30 minutes:
Interestingly the client did not start with DHCP Request as if the lease would already have expired. I thought it might have been the time-zone setting playing role but this was not the case checked the system UTC time and the lease should still be valid. The client has kept sending Discovers perpetually and accordingly to the configured protocol timings (as one would expect) of course not getting any offer (server still down).
Would the afore described behaviour be an indication of an undocumented feature (bug) ? I read in the documentation that client stopping sending discovers after a timeout would be anticipated in the case of a valid static lease, which is not the case here.
I would hugely appreciate any insight in the described behaviour.
With my best wishes
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.