Subject: bin/11341: named SIGSEGV w/ previously working named.conf
To: None <gnats-bugs@gnats.netbsd.org>
From: Ingolf Steinbach <ingolf@jellonet.de>
List: netbsd-bugs
Date: 10/30/2000 08:47:13
>Number: 11341
>Category: bin
>Synopsis: named crashes (SIGSEGV) with previously working named.conf
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Oct 30 08:47:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: Ingolf Steinbach
>Release: 1.5_BETA as of 2000-10-23
>Organization:
>Environment:
System: NetBSD maus 1.5_BETA NetBSD 1.5_BETA (MAUS) #0: Sun Oct 29 00:59:25 MEST 2000 ingolf@maus:/usr/obj/sys/arch/amiga/compile/MAUS amiga
>Description:
named emits a syntax error and crashes due to a SIGSEGV
with the named.conf below. This file worked before (when running
1.5_ALPHA). The daemon syslogs the following messages before crashing:
Oct 30 17:24:55 maus named[620]: /etc/namedb/named.conf:10: syntax error near '195.27.27.18'
Oct 30 17:24:55 maus named[620]: /etc/namedb/named.conf:12: syntax error near '}'
>How-To-Repeat:
Use the following /etc/namedb/named.conf and start named:
# $NetBSD: named.conf,v 1.3 1999/01/22 01:41:19 mycroft Exp $
# boot file for secondary name server
# Note that there should be one primary entry for each SOA record.
options {
directory "/etc/namedb";
forward only;
forwarders {
195.27.27.18;
};
};
# primary server config:
#
zone "localhost" {
type master;
file "localhost";
};
zone "127.IN-ADDR.ARPA" {
type master;
file "127";
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.int" {
type master;
file "loopback.v6";
};
zone "local.net" {
type master;
file "local.net";
};
zone "2.168.192.IN-ADDR.ARPA" {
type master;
file "192.168.2";
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.c.e.f.ip6.int" {
type master;
file "fec0:0000:0000:0000";
};
# the very rest:
#
zone "." {
type hint;
file "/etc/namedb/root.cache";
};
>Fix:
don't know
>Release-Note:
>Audit-Trail:
>Unformatted: