Bind9 DHCP3 ddns static lease question: Post successful setup
[stable]
I have a successful setup of internal ddns.
It works like a champ for 99% of what I need.
The problem is assigning static leases through dhcpd.
To be complete, here is some information that may com in useful:
Client:
uncommented line in /etc/dhclient.conf to
send host-name "3800-dc";
This worked wonderfully in my complete dhcp pool.
If I take a look at tail /var/log/syslog on the dhcp server, I have
some lines like the following:
May 16 07:02:16 localhost dhcpd: DHCPDISCOVER from00:13:d3:XX:YY:ZZ via eth1
May 16 07:02:17 localhost dhcpd: DHCPOFFER on 199.30.30.89 to
00:13:d3:XX:YY:ZZ (3800-dc) via eth1
May 16 07:02:17 localhost named[3636]: client 127.0.0.1#34817:
updating zone 'test.domain/IN': adding an RR
May 16 07:02:17 localhost named[3636]: client 127.0.0.1#34817:
updating zone 'test.domain/IN': adding an RR
May 16 07:02:17 localhost dhcpd: Added new forward map from
3800-dc.test.domain. to 199.30.30.89
However, whenver I add the following to my dhcpd.conf
host 3800-dc {
hardware ethernet 00:13:d3:XX:YY:ZZ;
fixed-address 199.30.30.89;
}
I get lines like the following in the syslog:
May 16 20:18:05 localhost dhcpd: DHCPRELEASE of 199.30.30.89 from
00:13:d3:XX:YY:ZZ via eth1 (not found)
May 16 20:18:07 localhost dhcpd: DHCPDISCOVER from 00:13:d3:XX:YY:ZZ via eth1
May 16 20:18:07 localhost dhcpd: DHCPOFFER on 199.30.30.89 to
00:13:d3:XX:YY:ZZ via eth1
May 16 20:18:07 localhost dhcpd: DHCPREQUEST for 199.30.30.89
(199.30.30.2) from 00:13:d3:XX:YY:ZZ via eth1
May 16 20:18:07 localhost dhcpd: DHCPACK on 199.30.30.89 to
00:13:d3:XX:YY:ZZ via eth1
I have found a work around to this problem. I can stop the DNS server,
delete the .jrnl files associated with my network, and add the entries
into the DNS files. Both the revers and forward looking zone files.
This is a working solution for just the few IPs I need static now, but
will become a pain in the rear in the near future.
I want to have static leases for all of my PCs connected to the LAN
(about 30) and use a truly dynamic pool for traveling laptops, new
loads, etc...
This is not just a debian specific problem. Once the static leases are
defined, in either Debian or WinXP (not my choice), the problem is
created.
As usual, any help is greatly appreciated.
Reply to: