Problems with 100% CPU load of unbound

Unbound
1

Hello,
we use unbound in a loadbalancer configuration. We noticed that
sometimes the unbound process uses 100% of CPU even when it does not
receive any DNS requests. It uses this 100% cpu load till we restart the
process. After restarting all is ok again.

We don't know why this happens. We used unbound from debian-testing and
a self compiled version, too. The issue happened in both installations.

Does anybody have any information about this issue?

Currently used versions:

unbound:

2

Hi Sebastian,

In 1.4.5 a bug was fixed where a long loop could be entered, now cycle
detection has a loop-counter and maximum search amount.

An upgrade to 1.4.5 (or 1.4.6rc1) may solve the issue. If not please
let me know.

Best regards,
   Wouter