>1. Does aix 4.1.4 come with a DHCP server like NT?
>2. If it doesn't how much does it cost?
>3. Will the dhcp server allow you to integrate it with you DNS server to support dynamic
>updates and if it will integrate thin how do you configure it to work.
>Problem:
>I am currently running a RS/6000 and AIX 4.1.4 as a nameserver. I am running DHCP on a NT 3.51
>machine and have some perl programs that automatically ftp down a report several times a day from
>the NT to the RS/6000. I parse these reports out and restart the named. This gives forward and
>reverse lookup of win95 clients without using the Microsoft centric WINS server that does not yet
>support reverse arpa lookup.
>What I really want?
>I want to run the DHCP server and DNS server on the RS/6000. I want to have dynamic updates when
>people get a new lease from the DHCP server. Is this possible without buying someones integrated
>database package for dns and dhcp. What modifications must be done to the dhcp server portion of
>the RS/6000 to let it make dynamic updates to the named.
Yes. 4.1.4 includes a DHCP server. It even includes a hook to
recompile the named forward and reverse lookup tables. We personally
use the DHCP server in a static mode (ie, we assign IP's based on a
specific MAC address) so we do not need feature. The DHCP server
also includes support of BOOTP clients (in our case HP JetDirect
Printers).
The only real problem I encountered with the AIX DHCP server is
that when a specific client entry is changed to reflect a new MAC
address (ie a machine replacement or upgrade to a new NIC) the DHCP
server did not pickup the change when the you refreshed the server.
My only recourse was to stop the DHCP server (stopsrc -s dhcpsd) and
delete the client reservation database files (dhcpsd.ar and
dhcpsd.cr). Then I would restart the server. This caused the
obvious problem of clients having their IP reservation expire early.
This bug was supposed to be fixed with the latest patch level. I
haven't had tiime to verifiy.
Another problem that affected me was the while you can define
default IP settings for specific subnets. For example for subnet
aa.bb.cc.dd I can supposedly setup the DNS server, Subnet Mask, etc.
for all nodes in the subnet. The problem is that I doesn't work.
It merrily ignores the IP settings for the subnet (possibly because we
are using DHCP more as a BOOTP static IP assignment service). We
found that the IP settings worked for global assignments and client
specific assignments.