From owner-freebsd-bugs  Mon Jul 14 04:00:04 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA13899
          for bugs-outgoing; Mon, 14 Jul 1997 04:00:04 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA13873;
          Mon, 14 Jul 1997 04:00:02 -0700 (PDT)
Resent-Date: Mon, 14 Jul 1997 04:00:02 -0700 (PDT)
Resent-Message-Id: <199707141100.EAA13873@hub.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, beckmann@nacamar.net
Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA13515
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 14 Jul 1997 03:52:59 -0700 (PDT)
Received: (from root@localhost)
	by mail.nacamar.de (8.8.6/8.8.5) id MAA06738;
	Mon, 14 Jul 1997 12:52:55 +0200 (CEST)
Message-Id: <199707141052.MAA06738@mail.nacamar.de>
Date: Mon, 14 Jul 1997 12:52:55 +0200 (CEST)
From: beckmann@nacamar.net
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/4087: nameservice terminates after ndc restart
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         4087
>Category:       bin
>Synopsis:       nameservice terminates after ndc restart
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul 14 04:00:01 PDT 1997
>Last-Modified:
>Originator:     Michael Beckmann
>Organization:
Nacamar Data Communications
>Release:        FreeBSD 2.2-970703-RELENG i386
>Environment:

BIND 4.9.6
FreeBSD 2.2-RELENG with stock BIND 4.9.6 from FreeBSD distribution
FreeBSD 2.2.1-RELEASE with updated libs and BIND 4.9.6 from BIND distribution

Problem does not exist in FreeBSD 2.2.2-RELEASE which has BIND 4.9.4P1

>Description:

The ndc program is used as a frontend for BIND. Executing

ndc restart

will terminate named, but not restart it. This used to work in previous
releases.

cron jobs that restart named on a regular basis via ndc will terminate
nameservice.

>How-To-Repeat:

1. launch named -b /etc/namedb/named.boot
2. execute ndc reload

>Fix:

>From the ndc(8) manpage:

>Audit-Trail:
>Unformatted:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
BUGS
       Arguments to named are not preserved by restart, or  known
       by  start.   Some mechanism for controlling the parameters
       and environment should exist.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<

The default location for the named.boot file in BIND is /etc/named.boot .
FreeBSD keeps that file in /etc/namedb/named.boot and starts named with
the argument -b /etc/namedb/named.boot . So the solution might be to
either change the default location of the file in BIND or in FreeBSD.
Or fix ndc. Or make a symbolic link. Or... Or....

I don't know why this problem hasn't been there in previous
releases. The ndc bug seems to be a long standing one. I can do an
ndc restart just fine on a FreeBSD 2.2.2-RELEASE system, although
named was started with -b /etc/namedb/named.boot .