mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-30 14:07:59 +00:00
Code Issues Releases Wiki Activity

hint zones do go in views; match_clients -> match-clients

Browse Source
This commit is contained in:
Andreas Gustafsson
2000-07-18 18:16:19 +00:00
parent 209ec709f3
commit 0ade7651fc
2 changed files with 5 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/arm/Bv9ARM.6.html
View File

@@ -16,7 +16,7 @@
- SOFTWARE. - SOFTWARE.
--> -->
<!-- $Id: Bv9ARM.6.html,v 1.8 2000/07/12 17:54:33 gson Exp $ --> <!-- $Id: Bv9ARM.6.html,v 1.9 2000/07/18 18:16:18 gson Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<HTML> <HTML>
@@ -3886,7 +3886,7 @@ view</CODE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=1038409"></A> <PRE CLASS="2Level-fixed"><A NAME="pgfId=1038409"></A>
<KBD CLASS="Literal-user-input"> view </KBD><EM CLASS="variable">view name</EM><KBD CLASS="Literal-user-input"> {</KBD> <KBD CLASS="Literal-user-input"> view </KBD><EM CLASS="variable">view name</EM><KBD CLASS="Literal-user-input"> {</KBD>
<KBD CLASS="Literal-user-input">match_clients {</KBD> <EM CLASS="variable">address_match_list</EM><KBD CLASS="Literal-user-input"> } ; </KBD> <KBD CLASS="Literal-user-input">match-clients {</KBD> <EM CLASS="variable">address_match_list</EM><KBD CLASS="Literal-user-input"> } ; </KBD>
<EM CLASS="Optional-meta-syntax">[</EM><CODE CLASS="grammar_literal">view_option</CODE><KBD CLASS="Literal-user-input">;</KBD><EM CLASS="Optional-meta-syntax"> ...]</EM> <EM CLASS="Optional-meta-syntax">[</EM><CODE CLASS="grammar_literal">view_option</CODE><KBD CLASS="Literal-user-input">;</KBD><EM CLASS="Optional-meta-syntax"> ...]</EM>
<EM CLASS="Optional-meta-syntax">[</EM><CODE CLASS="grammar_literal">zone_statement</CODE><KBD CLASS="Literal-user-input">;</KBD><EM CLASS="Optional-meta-syntax"> ...]]</EM> <EM CLASS="Optional-meta-syntax">[</EM><CODE CLASS="grammar_literal">zone_statement</CODE><KBD CLASS="Literal-user-input">;</KBD><EM CLASS="Optional-meta-syntax"> ...]]</EM>
<KBD CLASS="Literal-user-input">};</KBD> <KBD CLASS="Literal-user-input">};</KBD>
@@ -3964,18 +3964,7 @@ zone</CODE>
statements must occur inside <CODE CLASS="Program-Process"> statements must occur inside <CODE CLASS="Program-Process">
view</CODE> view</CODE>
statements.</P> statements.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1107611">
</A>
A <CODE CLASS="Program-Process">
zone</CODE>
statement of type <EM CLASS="variable">
hint</EM>
for the root zone (`<EM CLASS="grammar_literal">
.</EM>
') does not strictly define a zone. Therefore, it should not be included in a <CODE CLASS="Program-Process">
view</CODE>
statement.</P>
<P CLASS="3LevelContinued"> <P CLASS="3LevelContinued">
<A NAME="pgfId=1038608"> <A NAME="pgfId=1038608">
</A> </A>

9
doc/arm/Bv9ARM.txt
View File

@@ -734,9 +734,7 @@ The key{} statement has two clauses: algorithm and secret. While the
configuration parser will accept any string as the argument to algorithm, configuration parser will accept any string as the argument to algorithm,
currently only the string "hmac-md5" has any meaning. The secret is a currently only the string "hmac-md5" has any meaning. The secret is a
base-64 encoded string, typically generated with either dnssec-keygen or base-64 encoded string, typically generated with either dnssec-keygen or
mmencode. The parser will happily accept an invalid base-64 string, but it mmencode.
will never work with the server because the server validates the
base-64 of the secret for itself when loading its own configuration file.
The server{} statement uses the key clause to associate a key{}-defined key The server{} statement uses the key clause to associate a key{}-defined key
with a server. The argument to the server{} statement is a host name or with a server. The argument to the server{} statement is a host name or
@@ -2920,7 +2918,7 @@ representation of the key data.
6.2.17 view Statement Grammar 6.2.17 view Statement Grammar
view view name { view view name {
match_clients { address_match_list } ; match-clients { address_match_list } ;
[view_option; ...] [view_option; ...]
[zone_statement; ...]] [zone_statement; ...]]
}; };
@@ -2958,9 +2956,6 @@ statements specified on the top level of the configuration file are
considered to be part of this default view. If any explicit view statements considered to be part of this default view. If any explicit view statements
are present, all zone statements must occur inside view statements. are present, all zone statements must occur inside view statements.
A zone statement of type hint for the root zone ('.') does not strictly
define a zone. Therefore, it should not be included in a view statement.
Here is an example of a typical split DNS setup implemented using view Here is an example of a typical split DNS setup implemented using view
statements. statements.