[src/netbsd-3]: src/usr.sbin/bind/named Pull up file removal (requested by tr...

[riz <riz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/c78a83081820
branches:  netbsd-3
changeset: 576500:c78a83081820
user:      riz <riz%NetBSD.org@localhost>
date:      Tue Jul 05 22:41:28 2005 +0000

description:
Pull up file removal (requested by tron in ticket #516):
Remove outdated BIND 8 version of named.conf(5). The build now picks up
the correct version from "src/dist/bind/bin/named".

diffstat:

 usr.sbin/bind/named/named.conf.5 |  2300 --------------------------------------
 1 files changed, 0 insertions(+), 2300 deletions(-)

diffs (truncated from 2304 to 300 lines):

diff -r d001726a1a4c -r c78a83081820 usr.sbin/bind/named/named.conf.5
--- a/usr.sbin/bind/named/named.conf.5  Tue Jul 05 22:38:04 2005 +0000
+++ /dev/null   Thu Jan 01 00:00:00 1970 +0000
@@ -1,2300 +0,0 @@
-.\"     $NetBSD: named.conf.5,v 1.5 2004/06/03 15:05:45 heas Exp $
-.\"
-.\" Copyright (c) 1999-2000 by Internet Software Consortium
-.\"
-.\" Permission to use, copy, modify, and distribute this software for any
-.\" purpose with or without fee is hereby granted, provided that the above
-.\" copyright notice and this permission notice appear in all copies.
-.\"
-.\" THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
-.\" ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
-.\" CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
-.\" DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
-.\" PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
-.\" ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
-.\" SOFTWARE.
-.Dd May 21, 2004
-.Dt NAMED.CONF 5
-.Os
-.Sh NAME
-.Nm named.conf
-.Nd configuration file for
-.Xr named 8
-.Sh OVERVIEW
-BIND 9 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.
-.Ss General Syntax
-A BIND 9 configuration consists of two general features, statements
-and comments.
-All statements end with a semicolon.
-Many statements can contain substatements, which are each also
-terminated with a
-semicolon.
-.Pp
-The following statements are supported:
-.Bl -tag -width 0n
-.It Ic logging
-specifies what the server logs, and where the log messages are sent
-.It Ic options
-controls global server configuration options and sets defaults for other
-statements
-.It Ic zone
-defines a zone
-.It Ic acl
-defines a named IP address matching list, for access control and other uses
-.It Ic key
-specifies key information for use in authentication and authorization
-.It Ic trusted-keys
-defines DNSSEC keys that are preconfigured into the server and implicitly
-trusted
-.It Ic server
-sets certain configuration options for individual remote servers
-.It Ic controls
-declares control channels to be used by the
-.Nm rndc
-utility
-.It Ic include
-includes another file
-.El
-.Pp
-The
-.Ic logging
-and
-.Ic options
-statements may only occur once per configuration, while the rest may
-appear numerous times.
-Further detail on each statement is provided
-in individual sections below.
-.Pp
-Comments may 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.
-.Pp
-C-style comments start with the two characters
-.Li /*
-(slash, star) and end with
-.Li */
-(star, slash).
-Because they are completely delimited with these characters,
-they can be used to comment only a portion of a line or to span
-multiple lines.
-.Pp
-C-style comments cannot be nested.
-For example, the following is
-not valid because the entire comment ends with the first
-.Li */ :
-.Bd -literal -offset indent
-/* This is the start of a comment.
-   This is still part of the comment.
-/* This is an incorrect attempt at nesting a comment. */
-   This is no longer in any comment. */
-.Ed
-.Pp
-C++-style comments start with the two characters
-.Li //
-(slash, slash) and continue to the end of the physical line.
-They cannot be continued across multiple physical lines; to have
-one logical comment span multiple lines, each line must use the
-.Li //
-pair.
-For example:
-.Bd -literal -offset indent
-// This is the start of a comment.  The next line
-// is a new comment, even though it is logically
-// part of the previous comment.
-.Ed
-.Pp
-Shell-style (or perl-style, if you prefer) comments start with the
-character
-.Li #
-(hash or pound or number or octothorpe or whatever) and continue to
-the end of the physical line, like C++ comments.
-For example:
-.Bd -literal -offset indent
-# This is the start of a comment.  The next line
-# is a new comment, even though it is logically
-# part of the previous comment.
-.Ed
-.Pp
-.Em WARNING :
-you cannot use the
-.Li ;
-(semicolon) character to start a comment such as you would in a zone
-file.
-The semicolon indicates the end of a configuration statement,
-so whatever follows it will be interpreted as the start of the next
-statement.
-.Sh DOCUMENTATION DEFINITIONS
-Described below are elements used throughout the BIND configuration
-file documentation.
-Elements which are only associated with one
-statement are described only in the section describing that statement.
-.Bl -tag -width 0n
-.It Va acl_name
-The name of an
-.Va address_match_list
-as defined by the
-.Ic acl
-statement.
-.It Va address_match_list
-A list of one or more
-.Va ip_addr ,
-.Va ip_prefix ,
-.Va key_id ,
-or
-.Va acl_name
-elements, as described in the
-.Sx ADDRESS MATCH LISTS
-section.
-.It Va dotted-decimal
-One or more integers valued 0 through 255 separated only by dots
-.Pq Sq \&. ,
-such as
-.Li 123 ,
-.Li 45.67
-or
-.Li 89.123.45.67 .
-.It Va domain_name
-A quoted string which will be used as a DNS name, for example
-.Qq Li my.test.domain .
-.It Va path_name
-A quoted string which will be used as a pathname, such as
-.Qq Li zones/master/my.test.domain .
-.It Va ip_addr
-An IP address with exactly four elements in
-.Va dotted-decimal
-notation.
-.It Va ip_port
-An IP port
-.Va number .
-.Va number is limited to
-.Li 0
-through
-.Li 65535 ,
-with values below 1024 typically restricted to
-root-owned processes.
-In some cases an asterisk
-.Pq Sq *
-character
-can be used as a place holder to select a random high-numbered port.
-.It Va ip_prefix
-An IP network specified in
-.Va dotted-decimal
-form, followed by
-.Sq /
-and then the number of bits in the netmask.
-E.g.,
-.Li 127/8
-is
-the network
-.Li 127.0.0.0
-with netmask
-.Li 255.0.0.0 .
-.Li 1.2.3.0/28
-is network
-.Li 1.2.3.0
-with netmask
-.Li 255.255.255.240.
-.It Va key_name
-A string representing the name of a shared key, to be used for transaction
-security.
-.It Va number
-A non-negative integer with an entire range limited by the range of a
-C language signed integer (2,147,483,647 on a machine with 32 bit
-integers).
-Its acceptable value might further be limited by the
-context in which it is used.
-.It Va size_spec
-A
-.Va number ,
-the word
-.Li unlimited ,
-or the word
-.Li default .
-.Pp
-The maximum value of
-.Va size_spec
-is that of unsigned long integers on the machine.
-.Li unlimited
-requests unlimited use, or the maximum available amount.
-.Li default
-uses the limit that was in force when the server was started.
-.Pp
-A
-.Va number
-can optionally be followed by a scaling factor:
-.Li K
-or
-.Li k
-for kilobytes,
-.Li M
-or
-.Li m
-for megabytes, and
-.Li G
-or
-.Li g
-for gigabytes, which scale by 1024, 1024*1024, and 1024*1024*1024
-respectively.
-.Pp
-Integer storage overflow is currently silently ignored during
-conversion of scaled values, resulting in values less than intended,
-possibly even negative.
-Using
-.Li unlimited
-is the best way to safely set a really large number.
-.It Va yes_or_no
-Either
-.Li yes
-or
-.Li no .
-The words
-.Li true
-and
-.Li false
-are also accepted, as are the numbers
-.Li 1 and
-.Li 0 .
-.El
-.Sh ADDRESS MATCH LISTS
-.Ss Syntax
-.Bd -literal
-\fIaddress_match_list\fR    = 1\&*\fIaddress_match_element\fR
-.Pp
-\fIaddress_match_element\fR = [ \&"!\&" ] ( \fIaddress_match_list\fR /
-                                  \fIip_address\fR / \fIip_prefix\fR /
-                                  \fIacl_name\fR / \&"key \&" \fIkey_id\fR ) \&";\&"
-.Ed
-.Ss Definition and Usage
-Address match lists are primarily used to determine access control for
-various server operations.
-They are also used to define priorities
-for querying other nameservers and to set the addresses on which
-.Nm named
-will listen for queries.
-The elements which constitute an address match list can be any
-of the following:
-.Bl -bullet
-.It
-an
-.Va ip-address
-(in
-.Va dotted-decimal
-notation,
-.It
-an
-.Va ip-prefix
-(in the
-.Sq / No Ns -notation ) ,
-.It