Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ISC Open Source Projects
BIND
Commits
33682c92
Commit
33682c92
authored
Aug 09, 2001
by
Andreas Gustafsson
Browse files
regenerated docs
parent
f4909f01
Changes
10
Hide whitespace changes
Inline
Side-by-side
bin/rndc/rndc.8
View file @
33682c92
...
...
@@ -19,7 +19,7 @@
rndc \- name server control utility
.SH SYNOPSIS
.sp
\fBrndc\fR [ \fB-c \fIconfig-file\fB\fR ] [ \fB-s \fIserver\fB\fR ] [ \fB-p \fIport\fB\fR ] [ \fB-V\fR ] [ \fB-y \fIkey_id\fB\fR ] \fBcommand\fR
\fBrndc\fR [ \fB-c \fIconfig-file\fB\fR ] [
\fB-k \fIkey-file\fB\fR ] [
\fB-s \fIserver\fB\fR ] [ \fB-p \fIport\fB\fR ] [ \fB-V\fR ] [ \fB-y \fIkey_id\fB\fR ] \fBcommand\fR
.SH "DESCRIPTION"
.PP
\fBrndc\fR controls the operation of a name
...
...
@@ -51,6 +51,14 @@ Use \fIconfig-file\fR
as the configuration file instead of the default,
\fI/etc/rndc.conf\fR.
.TP
\fB-k \fIkey-file\fB\fR
Use \fIkey-file\fR
as the key file instead of the default,
\fI/etc/rndc.key\fR. The key in
\fI/etc/rndc.key\fR will be used to authenticate
commands sent to the server if the \fIconfig-file\fR
does not exist.
.TP
\fB-s \fIserver\fB\fR
\fIserver\fR is
the name or address of the server which matches a
...
...
bin/rndc/rndc.html
View file @
33682c92
...
...
@@ -69,6 +69,14 @@ CLASS="REPLACEABLE"
></TT
>
] [
<TT
CLASS=
"OPTION"
>
-k
<TT
CLASS=
"REPLACEABLE"
><I
>
key-file
</I
></TT
></TT
>
] [
<TT
CLASS=
"OPTION"
>
-s
<TT
CLASS=
"REPLACEABLE"
><I
...
...
@@ -99,7 +107,7 @@ CLASS="REPLACEABLE"
><DIV
CLASS=
"REFSECT1"
><A
NAME=
"AEN3
1
"
NAME=
"AEN3
4
"
></A
><H2
>
DESCRIPTION
</H2
...
...
@@ -154,7 +162,7 @@ CLASS="COMMAND"
><DIV
CLASS=
"REFSECT1"
><A
NAME=
"AEN4
3
"
NAME=
"AEN4
6
"
></A
><H2
>
OPTIONS
</H2
...
...
@@ -186,6 +194,39 @@ CLASS="FILENAME"
</P
></DD
><DT
>
-k
<TT
CLASS=
"REPLACEABLE"
><I
>
key-file
</I
></TT
></DT
><DD
><P
>
Use
<TT
CLASS=
"REPLACEABLE"
><I
>
key-file
</I
></TT
>
as the key file instead of the default,
<TT
CLASS=
"FILENAME"
>
/etc/rndc.key
</TT
>
. The key in
<TT
CLASS=
"FILENAME"
>
/etc/rndc.key
</TT
>
will be used to authenticate
commands sent to the server if the
<TT
CLASS=
"REPLACEABLE"
><I
>
config-file
</I
></TT
>
does not exist.
</P
></DD
><DT
>
-s
<TT
CLASS=
"REPLACEABLE"
><I
...
...
@@ -297,7 +338,7 @@ CLASS="COMMAND"
><DIV
CLASS=
"REFSECT1"
><A
NAME=
"AEN
82
"
NAME=
"AEN
94
"
></A
><H2
>
LIMITATIONS
</H2
...
...
@@ -325,7 +366,7 @@ CLASS="OPTION"
><DIV
CLASS=
"REFSECT1"
><A
NAME=
"AEN
90
"
NAME=
"AEN
102
"
></A
><H2
>
SEE ALSO
</H2
...
...
@@ -367,7 +408,7 @@ CLASS="CITETITLE"
><DIV
CLASS=
"REFSECT1"
><A
NAME=
"AEN1
06
"
NAME=
"AEN1
18
"
></A
><H2
>
AUTHOR
</H2
...
...
doc/arm/Bv9ARM.ch03.html
View file @
33682c92
...
...
@@ -1133,11 +1133,11 @@ CLASS="command"
>
will also look in
<TT
CLASS=
"filename"
>
/
var/run/named
.key
</TT
>
(or wh
er
ever
>
/
etc/rndc
.key
</TT
>
(or wh
at
ever
<TT
CLASS=
"varname"
>
localstate
dir
</TT
>
sysconf
dir
</TT
>
was defined when
the
<SPAN
CLASS=
"acronym"
...
...
@@ -1145,11 +1145,11 @@ CLASS="acronym"
>
build was configured).
The
<TT
CLASS=
"filename"
>
named
.key
</TT
>
rndc
.key
</TT
>
file is generated by
<B
running
<B
CLASS=
"command"
>
named
</B
>
rndc-confgen -a
</B
>
as described in
<A
HREF=
"Bv9ARM.ch06.html#controls_statement_definition_and_usage"
...
...
@@ -1329,7 +1329,7 @@ following controls statements:</P
><PRE
CLASS=
"programlisting"
>
controls {
inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
};
</PRE
><P
...
...
@@ -1338,6 +1338,37 @@ CLASS="programlisting"
CLASS=
"literal"
>
rndc_key
</TT
>
.
</P
><P
>
Running the
<B
CLASS=
"command"
>
rndc-confgen
</B
>
program will
conveniently create a
<TT
CLASS=
"filename"
>
rndc.conf
</TT
>
file for you, and also display the
corresponding
<B
CLASS=
"command"
>
controls
</B
>
statement that you need to
add to
<TT
CLASS=
"filename"
>
named.conf
</TT
>
. Alternatively,
you can run
<B
CLASS=
"command"
>
rndc-confgen -a
</B
>
to set up
a
<TT
CLASS=
"filename"
>
rndc.key
</TT
>
file and not modify
<TT
CLASS=
"filename"
>
named.conf
</TT
>
at all.
</P
></DD
></DL
></DIV
...
...
@@ -1348,7 +1379,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN65
0
"
NAME=
"AEN65
8
"
>
3.4.2. Signals
</A
></H2
><P
...
...
@@ -1361,7 +1392,7 @@ CLASS="command"
><DIV
CLASS=
"informaltable"
><A
NAME=
"AEN6
54
"
NAME=
"AEN6
62
"
></A
><P
></P
...
...
doc/arm/Bv9ARM.ch04.html
View file @
33682c92
...
...
@@ -88,7 +88,7 @@ HREF="Bv9ARM.ch04.html#incremental_zone_transfers"
></DT
><DT
>
4.3.
<A
HREF=
"Bv9ARM.ch04.html#AEN7
14
"
HREF=
"Bv9ARM.ch04.html#AEN7
22
"
>
Split DNS
</A
></DT
><DT
...
...
@@ -98,12 +98,12 @@ HREF="Bv9ARM.ch04.html#tsig"
></DT
><DT
>
4.5.
<A
HREF=
"Bv9ARM.ch04.html#AEN8
74
"
HREF=
"Bv9ARM.ch04.html#AEN8
82
"
>
TKEY
</A
></DT
><DT
>
4.6.
<A
HREF=
"Bv9ARM.ch04.html#AEN8
8
9"
HREF=
"Bv9ARM.ch04.html#AEN89
7
"
>
SIG(0)
</A
></DT
><DT
...
...
@@ -113,7 +113,7 @@ HREF="Bv9ARM.ch04.html#DNSSEC"
></DT
><DT
>
4.8.
<A
HREF=
"Bv9ARM.ch04.html#AEN9
74
"
HREF=
"Bv9ARM.ch04.html#AEN9
82
"
>
IPv6 Support in
<SPAN
CLASS=
"acronym"
>
BIND
</SPAN
...
...
@@ -274,7 +274,7 @@ CLASS="sect1"
><H1
CLASS=
"sect1"
><A
NAME=
"AEN7
14
"
NAME=
"AEN7
22
"
>
4.3. Split DNS
</A
></H1
><P
...
...
@@ -672,7 +672,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN8
05
"
NAME=
"AEN8
13
"
>
4.4.1. Generate Shared Keys for Each Pair of Hosts
</A
></H2
><P
...
...
@@ -690,7 +690,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN81
0
"
NAME=
"AEN81
8
"
>
4.4.1.1. Automatic Generation
</A
></H3
><P
...
...
@@ -732,7 +732,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN82
1
"
NAME=
"AEN82
9
"
>
4.4.1.2. Manual Generation
</A
></H3
><P
...
...
@@ -753,7 +753,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN8
26
"
NAME=
"AEN8
34
"
>
4.4.2. Copying the Shared Secret to Both Machines
</A
></H2
><P
...
...
@@ -765,7 +765,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN8
29
"
NAME=
"AEN8
37
"
>
4.4.3. Informing the Servers of the Key's Existence
</A
></H2
><P
...
...
@@ -813,7 +813,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN84
1
"
NAME=
"AEN84
9
"
>
4.4.4. Instructing the Server to Use the Key
</A
></H2
><P
...
...
@@ -873,7 +873,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN85
7
"
NAME=
"AEN8
6
5"
>
4.4.5. TSIG Key Based Access Control
</A
></H2
><P
...
...
@@ -919,7 +919,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN87
0
"
NAME=
"AEN87
8
"
>
4.4.6. Errors
</A
></H2
><P
...
...
@@ -948,7 +948,7 @@ CLASS="sect1"
><H1
CLASS=
"sect1"
><A
NAME=
"AEN8
74
"
NAME=
"AEN8
82
"
>
4.5. TKEY
</A
></H1
><P
...
...
@@ -1014,7 +1014,7 @@ CLASS="sect1"
><H1
CLASS=
"sect1"
><A
NAME=
"AEN8
8
9"
NAME=
"AEN89
7
"
>
4.6. SIG(0)
</A
></H1
><P
...
...
@@ -1086,7 +1086,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN9
06
"
NAME=
"AEN9
14
"
>
4.7.1. Generating Keys
</A
></H2
><P
...
...
@@ -1165,7 +1165,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN9
26
"
NAME=
"AEN9
34
"
>
4.7.2. Creating a Keyset
</A
></H2
><P
...
...
@@ -1218,7 +1218,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN9
38
"
NAME=
"AEN9
46
"
>
4.7.3. Signing the Child's Keyset
</A
></H2
><P
...
...
@@ -1268,7 +1268,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN95
1
"
NAME=
"AEN95
9
"
>
4.7.4. Signing the Zone
</A
></H2
><P
...
...
@@ -1330,7 +1330,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN9
6
7"
NAME=
"AEN97
5
"
>
4.7.5. Configuring Servers
</A
></H2
><P
...
...
@@ -1358,7 +1358,7 @@ CLASS="sect1"
><H1
CLASS=
"sect1"
><A
NAME=
"AEN9
74
"
NAME=
"AEN9
82
"
>
4.8. IPv6 Support in
<SPAN
CLASS=
"acronym"
>
BIND
</SPAN
...
...
@@ -1418,7 +1418,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN99
0
"
NAME=
"AEN99
8
"
>
4.8.1. Address Lookups Using AAAA Records
</A
></H2
><P
...
...
@@ -1440,7 +1440,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN
995
"
NAME=
"AEN
1003
"
>
4.8.2. Address Lookups Using A6 Records
</A
></H2
><P
...
...
@@ -1460,7 +1460,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN
999
"
NAME=
"AEN
1007
"
>
4.8.2.1. A6 Chains
</A
></H3
><P
...
...
@@ -1506,7 +1506,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN101
0
"
NAME=
"AEN101
8
"
>
4.8.2.2. A6 Records for DNS Servers
</A
></H3
><P
...
...
@@ -1536,7 +1536,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN10
16
"
NAME=
"AEN10
24
"
>
4.8.3. Address to Name Lookups Using Nibble Format
</A
></H2
><P
...
...
@@ -1567,7 +1567,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN10
2
3"
NAME=
"AEN103
1
"
>
4.8.4. Address to Name Lookups Using Bitstring Format
</A
></H2
><P
...
...
@@ -1594,7 +1594,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN103
0
"
NAME=
"AEN103
8
"
>
4.8.5. Using DNAME for Delegation of IPv6 Reverse Addresses
</A
></H2
><P
...
...
doc/arm/Bv9ARM.ch05.html
View file @
33682c92
...
...
@@ -81,7 +81,7 @@ CLASS="TOC"
></DT
><DT
>
5.1.
<A
HREF=
"Bv9ARM.ch05.html#AEN105
0
"
HREF=
"Bv9ARM.ch05.html#AEN105
8
"
>
The Lightweight Resolver Library
</A
></DT
><DT
...
...
@@ -96,7 +96,7 @@ CLASS="sect1"
><H1
CLASS=
"sect1"
><A
NAME=
"AEN105
0
"
NAME=
"AEN105
8
"
>
5.1. The Lightweight Resolver Library
</A
></H1
><P
...
...
doc/arm/Bv9ARM.ch06.html
View file @
33682c92
...
...
@@ -91,7 +91,7 @@ HREF="Bv9ARM.ch06.html#Configuration_File_Grammar"
></DT
><DT
>
6.3.
<A
HREF=
"Bv9ARM.ch06.html#AEN349
0
"
HREF=
"Bv9ARM.ch06.html#AEN349
9
"
>
Zone File
</A
></DT
></DL
...
...
@@ -145,7 +145,7 @@ file documentation:</P
><DIV
CLASS=
"informaltable"
><A
NAME=
"AEN1
092
"
NAME=
"AEN1
100
"
></A
><P
></P
...
...
@@ -740,7 +740,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN12
55
"
NAME=
"AEN12
63
"
>
6.1.1.1. Syntax
</A
></H3
><PRE
...
...
@@ -771,7 +771,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN12
63
"
NAME=
"AEN12
71
"
>
6.1.1.2. Definition and Usage
</A
></H3
><P
...
...
@@ -882,7 +882,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN1
292
"
NAME=
"AEN1
300
"
>
6.1.2. Comment Syntax
</A
></H2
><P
...
...
@@ -901,7 +901,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN1
297
"
NAME=
"AEN1
305
"
>
6.1.2.1. Syntax
</A
></H3
><P
...
...
@@ -933,7 +933,7 @@ CLASS="sect3"
><H3
CLASS=
"sect3"
><A
NAME=
"AEN13
06
"
NAME=
"AEN13
14
"
>
6.1.2.2. Definition and Usage
</A
></H3
><P
...
...
@@ -1043,7 +1043,7 @@ CLASS="acronym"
><DIV
CLASS=
"informaltable"
><A
NAME=
"AEN133
0
"
NAME=
"AEN133
8
"
></A
><P
></P
...
...
@@ -1271,7 +1271,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN1
399
"
NAME=
"AEN1
407
"
>
6.2.1.
<B
CLASS=
"command"
>
acl
</B
...
...
@@ -1318,7 +1318,7 @@ CLASS="command"
><DIV
CLASS=
"informaltable"
><A
NAME=
"AEN14
1
2"
NAME=
"AEN142
0
"
></A
><P
></P
...
...
@@ -1416,7 +1416,7 @@ CLASS="sect2"
><H2
CLASS=
"sect2"
><A
NAME=
"AEN144
1
"
NAME=
"AEN144
9
"
>
6.2.3.
<B
CLASS=
"command"
>
controls
</B
...
...
@@ -1539,76 +1539,59 @@ HREF="Bv9ARM.ch03.html#admin_tools"
must be signed by one of its specified keys to
be honored.
</P
><P
>
The
<B
>
If no
<B
CLASS=
"command"
>
controls
</B
>
statement is present,
<B
CLASS=
"command"
>
named
</B
>
will set up a default
control channel listening on the loopback address 127.0.0.1
and its IPv6 counterpart ::1.
In this case, and also when the
<B
CLASS=
"command"
>
controls
</B
>
statement
is present but does not have a
<B
CLASS=
"command"
>
keys
</B
>
clause is not strictly required.
If it is not present, then a random key will be generated automatically
and placed in a file named
<TT
>
clause,
<B
CLASS=
"command"
>
named
</B
>
will attempt to load the command channel key
from the file
<TT
CLASS=
"filename"
>
named
.key
</TT
>
, which is
usually in
<TT
>
rndc
.key
</TT
>
in
<TT
CLASS=
"filename"
>
/var/run
</TT
>
but will be wherever
<TT
>
/etc
</TT
>
(or whatever
<TT
CLASS=
"varname"
>
localstate
dir
</TT
>
was specified as when
<SPAN
>
sysconf
dir
</TT
>
was specified as when
<SPAN
CLASS=
"acronym"
>
BIND
</SPAN
>
was built.
<TT
CLASS=
"filename"
>
named.key
</TT
>
contains a complete
<TT
CLASS=
"filename"
>
rndc.conf
</TT
>
-compatible
configuration and is used by
<B
CLASS=
"command"
>
rndc
</B
>
when it
cannot find its primary configuration file.
</P
><P
>
Similarly,
<TT
CLASS=
"filename"
>
named.key
</TT
>
is generated when
no
<B
CLASS=
"command"
>
controls
</B
>
statement is present at all. In
that situation it will configure a control channel to run on
127.0.0.1.
</P
><P
>
There are two ways to disable the creation of
<TT
>
was built).
To create a
<TT
CLASS=
"filename"
>
named.key
</TT
>
. One is to ensure that all of your
<B
CLASS=
"command"
>
inet
</B
>
control channels have a
<B
CLASS=
"command"
>
keys
</B
>
clause. The other is to have a
<B
CLASS=
"command"
>
controls
</B
>
statement