Tracking historical lease information

Glenn Satchell glenn.satchell at
Thu Jan 20 11:13:39 UTC 2011

It's trivial to use syslog to log dhcp entries, then you can keep the 
syslog files for as long as you like. A script to scan those shouldn't 
be too difficult to find or write. You could also take entries from 
syslog and put them into a database if that was more useful.

Jan 17 13:55:13 drill dhcpd: [ID 702911] BOOTREQUEST from 
00:1b:11:18:b9:d2 via hme0
Jan 17 13:55:13 drill dhcpd: [ID 702911] BOOTREPLY for to shredder (00:1b:11:18:b9:d2) via hme0
Jan 17 13:55:13 drill dhcpd: [ID 702911] DHCPREQUEST for from 00:1b:11:18:b9:d2 via hme0
Jan 17 13:55:13 drill dhcpd: [ID 702911] DHCPACK on to 00:1b:11:18:b9:d2 via hme0


On 01/20/11 10:32, Chris Buxton wrote:
> Most commercial DDI solutions offer this. For example, on a BlueCat Adonis, there's a software component that watches the dhcpd.leases file and reports all new leases back to the BlueCat Proteus that controls it. All leases are stored in a database for easy retrieval, and you can look at the history of a given IP address to see who leased it and when.
> However, it sounds like you don't have the ability to migrate to a new DHCP platform. In which case, perhaps you can use a similar technique when you roll your own, or perhaps you can find a DDI solution that doesn't require replacing the box (nor your existing DHCP installation on the box); I know there's at least one such out there.
> Chris Buxton
> BlueCat Networks
> On Jan 19, 2011, at 3:05 PM, David Carlin wrote:
>> I'm looking for a way to track historical lease information.  For
>> example, I want to be able to query a specific IP and time stamp and
>> be returned the MAC address which has a lease for that IP at that
>> point in time.
>> I've come across the following logging/tracking solutions searching
>> the list archives:
>> Gluff -
>> FindHosts -
>> DHCPStatus -
>> -
>> LanLord -
>> DHCPStatus, and Lanlord seem to be geared toward
>> reporting on the status of current leases.  Only FindHosts and Gluff
>> appear to have facilities to support historical use.  Gluff seems the
>> most promising, but I'm not in control of the DHCP servers to upgrade
>> them to 4.1.0+.
>> Anyone else have any other recommendations before I go the roll your own route?
>> David

More information about the dhcp-users mailing list