Your message dated Sat, 21 Nov 2009 10:49:54 -0600
with message-id <[email protected]>
and subject line Re: Bug#132492: bind not compatible with djbdns in
forward-first mode
has caused the Debian Bug report #132492,
regarding bind not compatible with djbdns in forward-first mode
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
132492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=132492
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind
Version: 1:8.3.0-1.1
Severity: critical
Hi.
the attached config works fine with 8.2.5-2. the upgrade to 8.3.0-1.1 leads to
tons of errors in dameon.log:
Feb 5 21:34:37 gateway named[4294]: sysquery: no addrs found for root NS
(K.ROOT-SERVERS.NET)
Feb 5 21:34:37 gateway named[4294]: sysquery: no addrs found for root NS
(L.ROOT-SERVERS.NET)
Feb 5 21:34:37 gateway named[4294]: sysquery: no addrs found for root NS
(M.ROOT-SERVERS.NET)
Feb 5 21:34:37 gateway named[4294]: sysquery: no addrs found for root NS
(I.ROOT-SERVERS.NET)
and it doesn't work, i can't resolve my local doamins, or remote domains. so
the package is broken and breaks every other dns-based service for me.
Cord
-- System Information
Debian Release: 3.0
Kernel Version: Linux gateway 2.4.16-pre1 #1 Sun Dec 2 20:03:09 CET 2001 i486
unknown
Versions of the packages bind depends on:
ii libc6 2.2.4-7 GNU C Library: Shared libraries and Timezone
ii netbase 4.07 Basic TCP/IP networking system
--- Begin /etc/bind/named.conf (modified conffile)
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind/README.Debian for information on the
// structure of BIND configuration files in Debian for BIND versions 8.2.1
// and later, *BEFORE* you customize this configuration file.
//
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below. Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an unprivileged
// port by default.
// query-source address * port 53;
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
forwarders {
193.189.244.197;
193.189.244.205;
193.189.244.213;
};
};
// reduce log verbosity on issues outside our control
logging {
category lame-servers { null; };
category cname { null; };
};
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
// add entries for other zones below here
zone "42.42.10.in-addr.arpa" {
type master;
file "/etc/bind/db.10.42.42";
};
zone "intern.cord.de" {
type master;
file "/etc/bind/db.intern.cord.de";
};
// zone "cord.de" {
// type slave;
// masters { 195.247.160.16; };
// file "db.cord.de";
//};
// zone "abacom.net" {
// type slave;
// masters { 195.247.160.16; };
// file "db.abacom.net";
// };
--- End /etc/bind/named.conf
--- End Message ---
--- Begin Message ---
Version: 1:9.1.0-1
--
This bug does not apply to bind9.
lamont
--- End Message ---
