Comment 0 for bug 6944

Package: bind9
Version: 1:9.2.3+9.2.4-rc5-1
Severity: critical
Justification: breaks the whole system

Hi Bind9 Maintainer

Something must have changed since the last 'sarge' bind9 update.

I'm runing a IPv6 enabled system and had no troubles util 2-3 days ago when bind9 suddenly started to behave strangely.

Everything starts OK.
I can do dig AXFR @localhost zone.dom that works fine.

nmap shows that bind9 is listening to UDP on port 53...

But:

magma:~# host -a woody.ch localhost
Trying "woody.ch"
;; connection timed out; no servers could be reached

The only error I could figure out is shortly after starting bind9:

Jul 4 11:54:31 magma named[5415]: client.c:1317: unexpected error:
Jul 4 11:54:31 magma named[5415]: failed to get request's destination: failure

Other hostmasters also notifyed me, that their secondary zone on my ns don't work anymore.

Any idea of where the problem lies?

-Benoit-

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=C

Versions of packages bind9 depends on:
ii adduser 3.57 Add and remove users and groups
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libdns11 1:9.2.3+9.2.4-rc5-1 DNS Shared Library used by BIND
ii libisc7 1:9.2.3+9.2.4-rc5-1 ISC Shared Library used by BIND
ii libisccc0 1:9.2.3+9.2.4-rc5-1 Command Channel Library used by BI
ii libisccfg0 1:9.2.3+9.2.4-rc5-1 Config File Handling Library used
ii liblwres1 1:9.2.3+9.2.4-rc5-1 Lightweight Resolver Library used
ii libssl0.9.7 0.9.7d-3 SSL shared libraries
ii netbase 4.17 Basic TCP/IP networking system

-- no debconf information