Phew!!!
many thanks toall of you that replied. I'll have a closer look when i
get back to work
What I've actually got is one table called IP_subnet that has all my
subnet details, e.g. def gateway, dns servers, subnet mask ip pool
address range, whether to generate dynamic dns entries in my dhcpd
config file etc and another one called ip_client where a subnet column
is a foreign key pointing to the IP_subnet table and another column is
the host component of the address.

The ip_client table holds things such client machine operating system,
use dhcp , generate a dns entry,owning user, registering user, date
created, date modified hostname , a foreign ptr to a table of dhcp
options associated with that host.and a few other things.

I did think of having 1 ip_client record for every ip address and a
boolean that indicated whether it was in use, but we've got a class b
network, and that's a lot of addresses :-))
BTW I'm using db2 V9.1 on a RH advanced server 4

--CELKO-- wrote:
> >> Perhaps you could store all 254 IP addess in the TABLE, and use a second COLUMN to denote if it is taken. <<
>
> Go one step further and have a DATE column that tells you when the IP
> addess was assigned and perhaps a column for the assginee.

alexs wrote:
> Phew!!!
> many thanks toall of you that replied. I'll have a closer look when i
> get back to work
> What I've actually got is one table called IP_subnet that has all my
> subnet details, e.g. def gateway, dns servers, subnet mask ip pool
> address range, whether to generate dynamic dns entries in my dhcpd
> config file etc and another one called ip_client where a subnet column
> is a foreign key pointing to the IP_subnet table and another column is
> the host component of the address.
>
> The ip_client table holds things such client machine operating system,
> use dhcp , generate a dns entry,owning user, registering user, date
> created, date modified hostname , a foreign ptr to a table of dhcp
> options associated with that host.and a few other things.
>
> I did think of having 1 ip_client record for every ip address and a
> boolean that indicated whether it was in use, but we've got a class b
> network, and that's a lot of addresses :-))

Not that much. A class B has 65k records. Truthfully, that's nothing
for a DB. If you had a Class A, then maybe you'd look at performance
issues.

B.