DHCP 4.2.0 DDNS and OMAPI Bugs (RHEL5.5 x86_64)
jwest at brandeis.edu
Wed Sep 1 13:37:01 UTC 2010
Has anybody else run into this issue?
Anybody running 4.2.0 on RHEL5 with no problems?
On 08/30/10 17:02, Joshua West wrote:
> Hey folks,
> I just tried updating our systems from 4.1.1-P1 to 4.2.0 and had to
> revert back. I've encountered a couple issues with 4.2.0.
> This is all on RHEL 5.5 64-bit.
> The first issue is DDNS updates no longer work. The error I receive
> in /var/log/messages is :
> dhcpd: Unable to add forward map from myhost.mydomain.com to 18.104.22.168:
> not found
> With the hostname and IP addresses obviously changed for this email...
> Perhaps this has something to do with the BIND libraries compiled in
> for async DDNS updates starting in 4.2.0? I cannot build DHCP 4.2.0
> with the RHEL 5.5 supplied bind-libbind-devel / bind-devel packages
> (aka --with-libbind=/usr) as they are for an older version of BIND
> than 9.7.x.
> Packet captures on the dhcp servers and on the destination DNS server
> show that no packets were sent/received regarding the ddns update.
> The second and third bugs have to do with OMAPI. When I try to
> connect to the omapi port (900 on my system), I receive an error from
> dhcpctl_connect: operation in progress
> In addition, dhcpd then spikes to 100% CPU usage.
> Has anybody else run into these issues?
Senior Systems Engineer
More information about the dhcp-users