diff --git a/bin/check/named-checkconf.8 b/bin/check/named-checkconf.8 index e1ddf63938..f579750bb1 100644 --- a/bin/check/named-checkconf.8 +++ b/bin/check/named-checkconf.8 @@ -13,7 +13,7 @@ .\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR .\" PERFORMANCE OF THIS SOFTWARE. .\" -.\" $Id: named-checkconf.8,v 1.28 2007/05/09 03:33:50 marka Exp $ +.\" $Id: named-checkconf.8,v 1.29 2007/05/21 04:09:03 marka Exp $ .\" .hy 0 .ad l @@ -33,13 +33,18 @@ named\-checkconf \- named configuration file syntax checking tool .SH "SYNOPSIS" .HP 16 -\fBnamed\-checkconf\fR [\fB\-v\fR] [\fB\-j\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] {filename} [\fB\-z\fR] +\fBnamed\-checkconf\fR [\fB\-h\fR] [\fB\-v\fR] [\fB\-j\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] {filename} [\fB\-z\fR] .SH "DESCRIPTION" .PP \fBnamed\-checkconf\fR checks the syntax, but not the semantics, of a named configuration file. .SH "OPTIONS" .PP +\-h +.RS 4 +Print the usage summary and exit. +.RE +.PP \-t \fIdirectory\fR .RS 4 Chroot to diff --git a/bin/check/named-checkconf.html b/bin/check/named-checkconf.html index 88de098019..2b1cc349c1 100644 --- a/bin/check/named-checkconf.html +++ b/bin/check/named-checkconf.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -29,18 +29,22 @@named-checkconf
[-v
] [-j
] [-t
] {filename} [directory
-z
]
named-checkconf
[-h
] [-v
] [-j
] [-t
] {filename} [directory
-z
]
named-checkconf checks the syntax, but not the semantics, of a named configuration file.
+ Print the usage summary and exit. +
directory
Chroot to directory
so that
@@ -70,20 +74,20 @@
named-checkconf returns an exit status of 1 if errors were detected and 0 otherwise.
named-checkzone
[-d
] [-j
] [-q
] [-v
] [-c
] [class
-f
] [format
-F
] [format
-i
] [mode
-k
] [mode
-m
] [mode
-M
] [mode
-n
] [mode
-o
] [filename
-s
] [style
-S
] [mode
-t
] [directory
-w
] [directory
-D
] [-W
] {zonename} {filename}mode
named-checkzone
[-d
] [-h
] [-j
] [-q
] [-v
] [-c
] [class
-f
] [format
-F
] [format
-i
] [mode
-k
] [mode
-m
] [mode
-M
] [mode
-n
] [mode
-o
] [filename
-s
] [style
-S
] [mode
-t
] [directory
-w
] [directory
-D
] [-W
] {zonename} {filename}mode
named-compilezone
[-d
] [-j
] [-q
] [-v
] [-c
] [class
-C
] [mode
-f
] [format
-F
] [format
-i
] [mode
-k
] [mode
-m
] [mode
-n
] [mode
-o
] [filename
-s
] [style
-t
] [directory
-w
] [directory
-D
] [-W
] {zonename} {filename}mode
named-checkzone checks the syntax and integrity of a zone file. It performs the same checks as named does when loading a @@ -53,12 +53,16 @@
Enable debugging.
+ Print the usage summary and exit. +
Quiet mode - exit code only. @@ -169,6 +173,8 @@
filename
Write zone output to filename
.
+ If filename
is -
then
+ write to standard out.
This is mandatory for named-compilezone.
style
named-checkzone returns an exit status of 1 if errors were detected and 0 otherwise.
edns-disabled
++ Log queries that have been forced to use plain + DNS due to timeouts. This is often due to + the remote servers not being RFC 1034 compliant + (not always returning FORMERR or similar to + EDNS queries and other extension to the DNS + when they are not understood). i.e. this is + targeted at servers that fail to respond to + DNS queries that they don't understand. +
++ Note: the log message can be also due to + packet loss. Before reporting servers for + non RFC 1034 compliance they should be re-tested + to determine the nature of of the non-compliance. + This testing should prevent / reduce the + number of false positive reports. +
++ Note: eventually named will have to stop + treating such timeouts as due to RFC 1034 non + compliance and start treating it as plain + packet loss as falsely classifying packet + loss as due to RFC 1034 non compliance impacts + on DNSSEC validation. +
+
This is the grammar of the lwres
statement in the named.conf
file:
@@ -1655,7 +1688,7 @@ category notify { null; };
The lwres statement configures the name @@ -1706,14 +1739,14 @@ category notify { null; };
mastersname
[portip_port
] { (masters_list
|ip_addr
[portip_port
] [keykey
] ) ; [...] };
masters lists allow for a common set of masters to be easily used by @@ -1722,7 +1755,7 @@ category notify { null; };
This is the grammar of the options
statement in the named.conf
file:
@@ -2809,7 +2842,7 @@ options {
The forwarding facility can be used to create a large site-wide cache on a few servers, reducing traffic over links to external @@ -2853,7 +2886,7 @@ options {
Dual-stack servers are used as servers of last resort to work around @@ -3056,7 +3089,7 @@ options {
The interfaces and ports that the server will answer queries from may be specified using the listen-on option. listen-on takes @@ -3440,7 +3473,7 @@ query-source-v6 address * port *;
avoid-v4-udp-ports and avoid-v6-udp-ports specify a list of IPv4 and IPv6 UDP ports that will not be used as system @@ -3454,7 +3487,7 @@ query-source-v6 address * port *;
The server's usage of many system resources can be limited. Scaled values are allowed when specifying resource limits. For @@ -3513,7 +3546,7 @@ query-source-v6 address * port *;
The following options set limits on the server's resource consumption that are enforced internally by the @@ -3591,7 +3624,7 @@ query-source-v6 address * port *;
@@ -4648,7 +4681,7 @@ query-source-v6 address * port *;
trusted-keys {string
number
number
number
string
; [string
number
number
number
string
; [...]] @@ -4657,7 +4690,7 @@ query-source-v6 address * port *;The trusted-keys statement defines @@ -4700,7 +4733,7 @@ query-source-v6 address * port *;
The view statement is a powerful feature @@ -4956,10 +4989,10 @@ zone
zone_name
[