Since we do not pre-create /etc/namedb/s, add additional documentation

to the comments in named.conf to describe to the user how to create it.
    (named.conf does not use /etc/namedb/s by default anyway so us not
    pre-created it in the mtree does not hurt us terribly).
This commit is contained in:
dillon 1998-12-02 19:59:24 +00:00
parent a9a95cffaf
commit 56a5135adc

View File

@ -1,4 +1,4 @@
// $Id: named.conf,v 1.2 1998/05/11 11:26:28 peter Exp $
// $Id: named.conf,v 1.3 1998/12/01 21:36:33 dillon Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy
@ -80,7 +80,11 @@ zone "0.0.127.IN-ADDR.ARPA" {
//
// NOTE!!! FreeBSD runs bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind.
// to bind. The following sequence is suggested:
//
// mkdir /etc/namedb/s
// chown bind.bind /etc/namedb/s
// chmod 750 /etc/namedb/s
/*
zone "domain.com" {