head 1.2;
access;
symbols
RELENG_5_5_0_RELEASE:1.1.1.3.8.1
RELENG_5_5:1.1.1.3.8.1.0.6
RELENG_5_5_BP:1.1.1.3.8.1
RELENG_5_4_0_RELEASE:1.1.1.3.8.1
RELENG_5_4:1.1.1.3.8.1.0.4
RELENG_5_4_BP:1.1.1.3.8.1
RELENG_4_11_0_RELEASE:1.1.1.2.2.1
RELENG_4_11:1.1.1.2.2.1.0.18
RELENG_4_11_BP:1.1.1.2.2.1
RELENG_5_3_0_RELEASE:1.1.1.3.8.1
RELENG_5_3:1.1.1.3.8.1.0.2
RELENG_5_3_BP:1.1.1.3.8.1
RELENG_5:1.1.1.3.0.8
RELENG_5_BP:1.1.1.3
RELENG_4_10_0_RELEASE:1.1.1.2.2.1
RELENG_4_10:1.1.1.2.2.1.0.16
RELENG_4_10_BP:1.1.1.2.2.1
RELENG_5_2_1_RELEASE:1.1.1.3
RELENG_5_2_0_RELEASE:1.1.1.3
RELENG_5_2:1.1.1.3.0.6
RELENG_5_2_BP:1.1.1.3
v8_3_7:1.1.1.3
RELENG_4_9_0_RELEASE:1.1.1.2.2.1
RELENG_4_9:1.1.1.2.2.1.0.14
RELENG_4_9_BP:1.1.1.2.2.1
v8_3_6:1.1.1.3
RELENG_5_1_0_RELEASE:1.1.1.3
RELENG_5_1:1.1.1.3.0.4
RELENG_5_1_BP:1.1.1.3
RELENG_4_8_0_RELEASE:1.1.1.2.2.1
RELENG_4_8:1.1.1.2.2.1.0.12
RELENG_4_8_BP:1.1.1.2.2.1
v8_3_4:1.1.1.3
RELENG_5_0_0_RELEASE:1.1.1.3
RELENG_5_0:1.1.1.3.0.2
RELENG_5_0_BP:1.1.1.3
RELENG_4_7_0_RELEASE:1.1.1.2.2.1
RELENG_4_7:1.1.1.2.2.1.0.10
RELENG_4_7_BP:1.1.1.2.2.1
RELENG_4_6_2_RELEASE:1.1.1.2.2.1
RELENG_4_6_1_RELEASE:1.1.1.2.2.1
v8_3_3:1.1.1.3
RELENG_4_6_0_RELEASE:1.1.1.2.2.1
RELENG_4_6:1.1.1.2.2.1.0.8
RELENG_4_6_BP:1.1.1.2.2.1
v8_3_2_t1b:1.1.1.3
RELENG_4_5_0_RELEASE:1.1.1.2.2.1
RELENG_4_5:1.1.1.2.2.1.0.6
RELENG_4_5_BP:1.1.1.2.2.1
RELENG_4_4_0_RELEASE:1.1.1.2.2.1
RELENG_4_4:1.1.1.2.2.1.0.4
RELENG_4_4_BP:1.1.1.2.2.1
v8_2_4:1.1.1.3
RELENG_4_3_0_RELEASE:1.1.1.2.2.1
RELENG_4_3:1.1.1.2.2.1.0.2
RELENG_4_3_BP:1.1.1.2.2.1
v8_2_3:1.1.1.3
RELENG_4_2_0_RELEASE:1.1.1.2
v8_2_3_t6b:1.1.1.2
RELENG_4_1_1_RELEASE:1.1.1.2
PRE_SMPNG:1.1.1.2
RELENG_4_1_0_RELEASE:1.1.1.2
RELENG_3_5_0_RELEASE:1.1.1.1.2.1
RELENG_4_0_0_RELEASE:1.1.1.2
RELENG_4:1.1.1.2.0.2
RELENG_4_BP:1.1.1.2
RELENG_3_4_0_RELEASE:1.1.1.1.2.1
v8_2_2_p5:1.1.1.2
RELENG_3_3_0_RELEASE:1.1.1.1
RELENG_3_2_PAO:1.1.1.1.0.4
RELENG_3_2_PAO_BP:1.1.1.1
RELENG_3_2_0_RELEASE:1.1.1.1
RELENG_3_1_0_RELEASE:1.1.1.1
RELENG_3:1.1.1.1.0.2
RELENG_3_BP:1.1.1.1
RELENG_3_0_0_RELEASE:1.1.1.1
v8_1_2:1.1.1.1
bind_8_1_2_t3b:1.1.1.1
ISC:1.1.1;
locks; strict;
comment @# @;
1.2
date 2004.09.24.19.48.40; author des; state dead;
branches;
next 1.1;
1.1
date 98.05.03.04.11.30; author peter; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 98.05.03.04.11.30; author peter; state Exp;
branches
1.1.1.1.2.1;
next 1.1.1.2;
1.1.1.2
date 99.11.30.02.41.46; author peter; state Exp;
branches
1.1.1.2.2.1;
next 1.1.1.3;
1.1.1.3
date 2001.02.17.15.48.22; author asmodai; state Exp;
branches
1.1.1.3.8.1;
next ;
1.1.1.3.8.1
date 2004.09.26.03.09.22; author des; state dead;
branches;
next ;
1.1.1.2.2.1
date 2001.02.27.09.42.16; author asmodai; state Exp;
branches;
next ;
1.1.1.1.2.1
date 99.12.13.15.05.35; author peter; state Exp;
branches;
next 1.1.1.1.2.2;
1.1.1.1.2.2
date 2001.02.27.10.01.29; author asmodai; state Exp;
branches;
next ;
desc
@@
1.2
log
@Retire the BIND 8 sources.
@
text
@
BIND Configuration File Guide
BIND Configuration File Guide
Overview
BIND 8 is much more configurable than previous release of BIND.
There are entirely new areas of configuration, such as access control lists
and categorized logging. Many options that previously applied to all zones
can now be used selectively. These features, plus a consideration of future
configuration needs led to the creation of a new configuration file format.
The Configuration File
Statements
A BIND 8 configuration consists of statements and comments.
Statements end with a semicolon. Many statements contain a block of
substatements, which are also terminated with a semicolon.
The following statements are supported:
acl
-
defines a named IP address matching list, for access control and other uses
include
-
includes a file
key
-
specifies key information for use in authentication and authorization
logging
-
specifies what the server logs, and where the log messages are sent
options
-
controls global server configuation options and sets defaults for other
statements
server
-
sets certain configuration options on a per-server basis
zone
-
defines a zone
The logging and options statements may only
occur once per configuration.
Converting from BIND 4.9.x
BIND 4.9.x configuration files can be converted to the new format
by using src/bin/named/named-bootconf.pl, a perl script that
is part of the BIND 8.1 source kit.
[ BIND Home
| ISC ]
Last Updated: $Id: config.html,v 1.4 1998/03/21 01:03:11 halley Exp $
@
1.1
log
@Initial revision
@
text
@@
1.1.1.1
log
@Import (trimmed) ISC bind-8.1.2-t3b. This will be updated to 8.1.2 on
final release.
Obtained from: ftp.isc.org
@
text
@@
1.1.1.1.2.1
log
@MFC: bind 8.2.2.p5
Urged by: imp, alfred, and a whole bunch of other folks.
Approved by: jkh (a few days ago)
@
text
@d50 1
a50 1
controls global server configuration options and sets defaults for other
a52 4
controls
declares control channels to be used by the ndc utility
a56 5
trusted-keys
defines DNSSEC keys that are preconfigured into the server and implicitly
trusted
d65 1
a65 6
Comments
The BIND 8 comment syntax allows for
comments to appear anywhere that whitespace may appear in a BIND
configuration file. To appeal to programmers of all kinds, they can
be written in C, C++, or shell/perl constructs.
d69 3
a71 3
BIND 4.9.x configuration files can be converted to the new format by
using src/bin/named/named-bootconf, a shell script that is part of
the BIND 8.2.x source kits.
d75 2
a76 2
[ BIND Home
| ISC ]
d80 1
a80 1
Last Updated: $Id: config.html,v 1.10 1999/09/15 20:28:01 cyarnell Exp $
@
1.1.1.1.2.2
log
@MFC: BIND 8.2.3-REL documentation.
@
text
@d14 1
a14 1
BIND 8 is much more configurable than previous releases of BIND.
d94 1
a94 1
Last Updated: $Id: config.html,v 1.11 2000/11/28 20:03:48 cyarnell Exp $
@
1.1.1.2
log
@Import bind v8.2.2.p5, minus the crypto for the time being. The bind
package does have BXA export approval, but the licensing strings on the
dnssafe code are a bit unpleasant. The crypto is easy to restore and bind
will run without it - just without full dnssec support.
Obtained from: The Internet Software Consortium (www.isc.org)
@
text
@d50 1
a50 1
controls global server configuration options and sets defaults for other
a52 4
controls
declares control channels to be used by the ndc utility
a56 5
trusted-keys
defines DNSSEC keys that are preconfigured into the server and implicitly
trusted
d65 1
a65 6
Comments
The BIND 8 comment syntax allows for
comments to appear anywhere that whitespace may appear in a BIND
configuration file. To appeal to programmers of all kinds, they can
be written in C, C++, or shell/perl constructs.
d69 3
a71 3
BIND 4.9.x configuration files can be converted to the new format by
using src/bin/named/named-bootconf, a shell script that is part of
the BIND 8.2.x source kits.
d75 2
a76 2
[ BIND Home
| ISC ]
d80 1
a80 1
Last Updated: $Id: config.html,v 1.10 1999/09/15 20:28:01 cyarnell Exp $
@
1.1.1.2.2.1
log
@MFC: Update BIND documentation to 8.2.3-REL.
@
text
@d14 1
a14 1
BIND 8 is much more configurable than previous releases of BIND.
d94 1
a94 1
Last Updated: $Id: config.html,v 1.11 2000/11/28 20:03:48 cyarnell Exp $
@
1.1.1.3
log
@Virgin import of ISC BIND v8.2.3-REL docs
@
text
@d14 1
a14 1
BIND 8 is much more configurable than previous releases of BIND.
d94 1
a94 1
Last Updated: $Id: config.html,v 1.11 2000/11/28 20:03:48 cyarnell Exp $
@
1.1.1.3.8.1
log
@MFC: BIND 9 and related bits.
Approved by: re
@
text
@@