Unbound is spinning into space with crazy high CPU about once every hour. Kill -9 kills the process and the new process is perfectly happy for a bit until it too spins into space eating a ton of CPU and becoming unresponsive. The release notes don't show changes to Unbound, but this started happening after I updated this AM.
Not sure if it's related, but earlier this morning DNS resolution stopped working. I did not check CPU utilization, but just had to restart unbound multiple times before it started working again. I'll keep an eye on it and report back if it reoccurs.
So you have a lot of host aliases that require resolving?
Cheers,
Franco
I do. I use several aliases wit URL tables with thousands of IPs (ASN lookups). That was never an issue before. The problem with Undboud being unresponsive only happened once after 21.7.6. After forcing a service restart it has been working as expected. In my case it might just have been a one time anomaly. I'll update if it happens again.