Hi There, In discussion with the Debian package maintainer for dhcpd, it's been recommended I submit a bug report upstream to ISC about dhcpd 3.1.1.
There is a detailed description of the problem available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537557, however the crux of it is that dhcpd fails to work properly when DNS names are used in the 'address' and 'peer address' options within the 'failover peer' stanza. This is despite the fact that the dhcpd.conf(5) man page says in several references that using both IP addresses and DNS names are accepted. When I use IP addresses within 'failover peer', failover works and IP address assignment works. However when I use DNS names, failover does not work and both the failover peers believe they are the one true (authoritative) DHCP server. They individually DHCPOFFER different IP addresses to a DHCP client on the LAN segment. In addition to this, IP address assignment from both servers only partially works. In the case of Debian's dhcp3-server 3.1.1-lenny2 (which is built from ISC dhcpd 3.1.1 source tree), IP addresses are assigned out, but dhcpd does not provide the DHCP client with 'option domain-name-servers' information. In the case of Debian's dhcp3-server-ldap 3.1.1-lenny2 (which I'm told is built from ISC dhcpd 3.1.1 + a 3rd party patch), IP address assignment stops altogether. The fact that it doesn't properly work in either instance, may or may not indicate that the 3rd party patch for LDAP is not the source of the problem. Would you be so kind as to review the bug report history at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537557 and let me know what ISC's assessment of this bug is? If there is any further information I that you require, please do not hesitate to contact me. Kind Regards, Stewart _________________________________________________________________ What goes online, stays online Check the daily blob for the latest on what's happening around the web http://windowslive.ninemsn.com.au/blog.aspx
