Hi, my unbound (same version) just went to 100% cpu on one core as well, but for no reason that I've detected yet. However, trying out the suggested command, I see a different problem exposed:
$ dig +short rs.dns-oarc.net txt rst.x3827.rs.dns-oarc.net. rst.x3837.x3827.rs.dns-oarc.net. rst.x3843.x3837.x3827.rs.dns-oarc.net. "79.228.190.64 DNS reply size limit is at least 3843" "79.228.190.64 sent EDNS buffer size 4096" "Tested at 2010-06-26 18:18:24 UTC" This indicates that unbound will be unable to handle some real-world DNSSEC data, according to the web page mentioned. The standard log level of '1' does not log queries, nor answers. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
