[19098] in bugtraq
Re: Bug in Bind 9.1.0?
daemon@ATHENA.MIT.EDU (Maarten de Vries)
Fri Feb 9 11:52:18 2001
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <1092155960.20010209140422@netraam.com>
Date: Fri, 9 Feb 2001 14:04:22 +0100
Reply-To: Maarten de Vries <maarten@netraam.com>
From: Maarten de Vries <Maarten.de.Vries@NETRAAM.COM>
To: BUGTRAQ@SECURITYFOCUS.COM
On Wednesday, February 07, 2001, 11:15:48 PM, I wrote:
> I believe ISC is still investigating this. Haven't heard from the
> FreeBSD people yet, altough they were the first I reported this to...
In the meantime, I was informed by Doug Barton (who maintains the Bind
port in FreeBSD) that "the FreeBSD team is currently investigating
solutions to the problems brought to light by version 9.1.0 of BIND.
Meanwhile, our port of BIND 9 has been updated to use BIND version
9.1.1rc1 which, in addition to significant bug fixes contains code that
turns those failure modes into logged warnings".
Those warnings look like this:
Feb 9 13:56:04 tel named[88689]: socket.c:1673: unexpected error:
Feb 9 13:56:04 tel named[88689]: socket.c:1673: unexpected error:
Feb 9 13:56:04 tel named[88689]: internal_accept(): accept() returned peer address family 0 (expected 2)
Feb 9 13:56:04 tel named[88689]: internal_accept(): accept() returned peer address family 0 (expected 2)
It doesn't indeed crash anymore.
Upgrading time, then :-)
--
Maarten
