Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bind9 (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Also affects: bind9 (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1085593
Title:
bind 9.8.1-P1 crashes with an
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Reproduced on 1:9.8.1.dfsg.P1-4ubuntu0.4 (Precise).
On Raring, it doesn't crash, but I do get significant (90%) constant
CPU use with the following:
Dec 3 08:39:11 raring1 named[2561]: dns_dnssec_findzonekeys2:
(Raring CPU hog on 1:9.8.4.dfsg-1ubuntu1)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1085593
Title:
bind 9.8.1-P1 crashes with an assertion failure
To manage notifications about
I first experienced with bug with a normal (correct) zone file. Just
the zone contained users information which I'm not willing to publish,
thus I deleted most of the zone file and edited the rest and now it
contains RRSIG records with wrong hashes, I don't this malforming
affects anything - I
Thanks.
If this happens with valid zone files, it sounds like an important issue
to me for a stable release. I can imagine scenarios where server serving
a large number of zones could crash due to a single customer, or
something like that. bind should not crash. So I'm marking this as
Importance:
My conversation with upstream:
*My bug report sent to ISC:*
Attached is a named.conf and the zone file which result in assertion failure
with bind 9.8.1 (actually BIND 9.8.1-P1 on ubuntu 12.04.01).
Bug does NOT appears in 9.8.4 nor in 9.9.2 so I guess it's fixed, though I
can't find anything
As for the exact commit - I myself can't find anything related in the
changes history.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1085593
Title:
bind 9.8.1-P1 crashes with an
We move them on to the latest maintenance checkout point/release on the
branch they are using *when* they encounter a bug.
Emphasis mine. Although I'm not saying that this is necessarily a
problem for Ubuntu to have a micro release exception here, it is
interesting that ISC advise their customers