From a0e2e604a3c1e4e6971bdfbf60e943a2dad76df3 Mon Sep 17 00:00:00 2001 From: Mark Andrews Date: Mon, 10 Jan 2005 05:59:18 +0000 Subject: [PATCH] regen --- bin/check/named-checkzone.8 | 11 ++- bin/check/named-checkzone.html | 38 ++++++++-- doc/arm/Bv9ARM.ch06.html | 127 ++++++++++++++++++++++----------- doc/arm/Bv9ARM.ch07.html | 8 +-- doc/arm/Bv9ARM.ch08.html | 14 ++-- doc/arm/Bv9ARM.ch09.html | 108 ++++++++++++++-------------- doc/arm/Bv9ARM.html | 38 +++++----- 7 files changed, 212 insertions(+), 132 deletions(-) diff --git a/bin/check/named-checkzone.8 b/bin/check/named-checkzone.8 index 6d939b3842..17d4a29c2f 100644 --- a/bin/check/named-checkzone.8 +++ b/bin/check/named-checkzone.8 @@ -13,14 +13,14 @@ .\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR .\" PERFORMANCE OF THIS SOFTWARE. .\" -.\" $Id: named-checkzone.8,v 1.18.18.3 2004/06/03 04:17:52 marka Exp $ +.\" $Id: named-checkzone.8,v 1.18.18.4 2005/01/10 05:59:15 marka Exp $ .\" .TH "NAMED-CHECKZONE" "8" "June 13, 2000" "BIND9" "" .SH NAME named-checkzone \- zone file validity checking tool .SH SYNOPSIS .sp -\fBnamed-checkzone\fR [ \fB-d\fR ] [ \fB-j\fR ] [ \fB-q\fR ] [ \fB-v\fR ] [ \fB-c \fIclass\fB\fR ] [ \fB-k \fImode\fB\fR ] [ \fB-n \fImode\fB\fR ] [ \fB-o \fIfilename\fB\fR ] [ \fB-t \fIdirectory\fB\fR ] [ \fB-w \fIdirectory\fB\fR ] [ \fB-D\fR ] \fBzonename\fR \fBfilename\fR +\fBnamed-checkzone\fR [ \fB-d\fR ] [ \fB-j\fR ] [ \fB-q\fR ] [ \fB-v\fR ] [ \fB-c \fIclass\fB\fR ] [ \fB-k \fImode\fB\fR ] [ \fB-n \fImode\fB\fR ] [ \fB-o \fIfilename\fB\fR ] [ \fB-t \fIdirectory\fB\fR ] [ \fB-w \fIdirectory\fB\fR ] [ \fB-D\fR ] [ \fB-W \fImode\fB\fR ] \fBzonename\fR \fBfilename\fR .SH "DESCRIPTION" .PP \fBnamed-checkzone\fR checks the syntax and integrity of @@ -75,6 +75,13 @@ is similar to the directory clause in \fB-D\fR Dump zone file in canonical format. .TP +\fB-W \fImode\fB\fR +Specify whether to check for non-terminal wildcards. +Non-terminal wildcards are almost always the result of a +failure to understand the wildcard matching algorithm (RFC 1034). +Possible modes are \fB"warn"\fR (default) and +\fB"ignore"\fR. +.TP \fBzonename\fR The domain name of the zone being checked. .TP diff --git a/bin/check/named-checkzone.html b/bin/check/named-checkzone.html index 1813a7576e..2e8bdcb9ba 100644 --- a/bin/check/named-checkzone.html +++ b/bin/check/named-checkzone.html @@ -15,7 +15,7 @@ - PERFORMANCE OF THIS SOFTWARE. --> - + ] [-D] [-W mode] {zonename} {filename}

DESCRIPTION

OPTIONS

-W mode

Specify whether to check for non-terminal wildcards. + Non-terminal wildcards are almost always the result of a + failure to understand the wildcard matching algorithm (RFC 1034). + Possible modes are "warn" (default) and + "ignore". +

zonename

RETURN VALUES

SEE ALSO

AUTHOR

6.3. Zone File
] [ check-wildcard yes_or_no; ] + [ allow-notify { address_match_list

check-wildcard

This option is used to check for non-terminal wildcards. +The use of non-terminal wildcards is almost always as a result of a failure +to understand the wildcard matching algorithm (RFC 1034). This option +affects master zones. The default (yes) is to check +for non-terminal wildcards and issue a warning. +

6.2.16.2. Forwarding

6.2.16.3. Dual-stack Servers

6.2.16.5. Interfaces

6.2.16.6. Query Address

6.2.16.8. Bad UDP Port Lists

6.2.16.9. Operating System Resource Limits

6.2.16.10. Server Resource Limits

6.2.16.11. Periodic Task Intervals

6.2.19. trusted-keys

6.2.20. trusted-keys

6.2.22. view] [ check-wildcard yes_or_no; ] + [ dialup dialup_option

6.2.24. zone

6.2.24.1. Zone Types

6.2.24.2. Class

6.2.24.3. Zone Options

check-wildcard

See the description of +check-wildcard in Section 6.2.16.1.

database

6.3. Zone File

6.3.1.1. Resource Records

6.3.1.2. Textual expression of RRs

6.3.2. Discussion of MX Records

6.3.4. Inverse Mapping in IPv4

6.3.5. Other Zone File Directives

6.3.5.1. The $ORIGIN

6.3.5.2. The $INCLUDE

6.3.5.3. The $TTL

6.3.6. BIND

7.2. chroot

7.2. chroot

7.2.1. The chroot

7.2.2. Using the setuid

8.1. Common Problems
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?

8.1. Common Problems

8.1.1. It's not working; how can I figure out what's wrong?

8.2. Incrementing and Changing the Serial Number

8.3. Where Can I Get Help?

A.1. Acknowledgments

A.1. Acknowledgments

A.1.1. A Brief History of the DNS

Bibliography

Standards

[RFC974] 

[RFC1034] 

[RFC1035] 

[RFC2181] 

[RFC2308] 

[RFC1995] 

[RFC1996] 

[RFC2136] 

[RFC2845] 

Proposed Standards Still Under Development

[RFC1886] 

[RFC2065] 

[RFC2137] 

Other Important RFCs About DNS

[RFC1535] 

[RFC1536] 

[RFC1982] 

Resource Record Types

[RFC1183] 

[RFC1706] 

[RFC2168] 

[RFC1876] 

[RFC2052] 

[RFC2163] 

[RFC2230] 

DNS

[RFC1101] 

[RFC1123] 

[RFC1591] 

[RFC2317] 

DNS

[RFC1537] 

[RFC1912] 

[RFC2010] 

[RFC2219] 

Other DNS

[RFC1464] 

[RFC1713] 

[RFC1794] 

[RFC2240] 

[RFC2345] 

[RFC2352] 

Obsolete and Unimplemented Experimental RRs

[RFC1712] 

A.3.3. Other Documents About BIND

Bibliography

6.2.19. trusted-keys
6.2.20. trusted-keys
6.2.22. view
6.2.24. zone
6.3. Zone File
6.3.2. Discussion of MX Records
6.3.4. Inverse Mapping in IPv4
6.3.5. Other Zone File Directives
6.3.6. BIND
7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuid
8.1. Common Problems
8.1.1. It's not working; how can I figure out what's wrong?
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
A.1. Acknowledgments
A.1.1. A Brief History of the DNS
A.3.3. Other Documents About BIND