mirror of
https://gitlab.isc.org/isc-projects/kea
synced 2025-08-29 21:18:02 +00:00
Merge branch 'jreed-docs'
This commit is contained in:
commit
729bbdeb81
@ -1199,10 +1199,9 @@ TODO
|
||||
<title>Incoming Zone Transfers</title>
|
||||
|
||||
<para>
|
||||
The <command>b10-xfrin</command> process is started by
|
||||
<command>bind10</command>.
|
||||
It can be manually triggered to request an AXFR zone
|
||||
transfer. When received, it is stored in the BIND 10
|
||||
Incoming zones are transferred using the <command>b10-xfrin</command>
|
||||
process which is started by <command>bind10</command>.
|
||||
When received, the zone is stored in the BIND 10
|
||||
data store, and its records can be served by
|
||||
<command>b10-auth</command>.
|
||||
In combination with <command>b10-zonemgr</command> (for
|
||||
@ -1213,8 +1212,22 @@ TODO
|
||||
<note><simpara>
|
||||
The current development release of BIND 10 only supports
|
||||
AXFR. (IXFR is not supported.)
|
||||
|
||||
<!-- TODO: sqlite3 data source only? -->
|
||||
|
||||
</simpara></note>
|
||||
|
||||
<!-- TODO:
|
||||
|
||||
how to tell bind10 you are a secondary?
|
||||
|
||||
when will it first attempt to check for new zone? (using REFRESH?)
|
||||
what if zonemgr is not running?
|
||||
|
||||
what if a NOTIFY is sent?
|
||||
|
||||
-->
|
||||
|
||||
<para>
|
||||
To manually trigger a zone transfer to retrieve a remote zone,
|
||||
you may use the <command>bindctl</command> utility.
|
||||
@ -1223,6 +1236,9 @@ TODO
|
||||
<screen>> <userinput>Xfrin retransfer zone_name="<option>foo.example.org</option>" master=<option>192.0.2.99</option></userinput></screen>
|
||||
</para>
|
||||
|
||||
<!-- TODO: can that retransfer be used to identify a new zone? -->
|
||||
<!-- TODO: what if doesn't exist at that master IP? -->
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="xfrout">
|
||||
@ -1329,28 +1345,34 @@ what is XfroutClient xfr_client??
|
||||
|
||||
<!-- TODO: later the above will have some defaults -->
|
||||
|
||||
<para>
|
||||
To enable forwarding, the upstream address and port must be
|
||||
configured to forward queries to, such as:
|
||||
<section>
|
||||
<title>Forwarding</title>
|
||||
|
||||
<screen>
|
||||
<para>
|
||||
|
||||
To enable forwarding, the upstream address and port must be
|
||||
configured to forward queries to, such as:
|
||||
|
||||
<screen>
|
||||
> <userinput>config set Resolver/forward_addresses [{ "address": "<replaceable>192.168.1.1</replaceable>", "port": 53 }]</userinput>
|
||||
> <userinput>config commit</userinput>
|
||||
</screen>
|
||||
|
||||
(Replace <replaceable>192.168.1.1</replaceable> to point to your
|
||||
full resolver.)
|
||||
</para>
|
||||
(Replace <replaceable>192.168.1.1</replaceable> to point to your
|
||||
full resolver.)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Normal iterative name service can be re-enabled by clearing the
|
||||
forwarding address(es); for example:
|
||||
<para>
|
||||
Normal iterative name service can be re-enabled by clearing the
|
||||
forwarding address(es); for example:
|
||||
|
||||
<screen>
|
||||
<screen>
|
||||
> <userinput>config set Resolver/forward_addresses []</userinput>
|
||||
> <userinput>config commit</userinput>
|
||||
</screen>
|
||||
</para>
|
||||
</para>
|
||||
|
||||
</section>
|
||||
|
||||
<!-- TODO: later try this
|
||||
|
||||
|
@ -144,6 +144,9 @@ The default is the basename of ARG 0.
|
||||
</variablelist>
|
||||
</refsect1>
|
||||
|
||||
<!--
|
||||
TODO: configuration section
|
||||
-->
|
||||
<!--
|
||||
<refsect1>
|
||||
<title>FILES</title>
|
||||
|
@ -22,7 +22,7 @@
|
||||
bindctl \- control and configure BIND 10
|
||||
.SH "SYNOPSIS"
|
||||
.HP \w'\fBbindctl\fR\ 'u
|
||||
\fBbindctl\fR [\fB\-a\ \fR\fB\fIaddress\fR\fR] [\fB\-h\fR] [\fB\-c\ \fR\fB\fIfile\fR\fR] [\fB\-p\ \fR\fB\fInumber\fR\fR] [\fB\-\-address\ \fR\fB\fIaddress\fR\fR] [\fB\-\-help\fR] [\fB\-\-certificate\-chain\ \fR\fB\fIfile\fR\fR] [\fB\-\-port\ \fR\fB\fInumber\fR\fR] [\fB\-\-version\fR]
|
||||
\fBbindctl\fR [\fB\-a\ \fR\fB\fIaddress\fR\fR] [\fB\-h\fR] [\fB\-c\ \fR\fB\fIfile\fR\fR] [\fB\-p\ \fR\fB\fInumber\fR\fR] [\fB\-\-address\ \fR\fB\fIaddress\fR\fR] [\fB\-\-help\fR] [\fB\-\-certificate\-chain\ \fR\fB\fIfile\fR\fR] [\fB\-\-csv\-file\-dir\fR\fB\fIfile\fR\fR] [\fB\-\-port\ \fR\fB\fInumber\fR\fR] [\fB\-\-version\fR]
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
The
|
||||
@ -52,6 +52,11 @@ daemon\&. The default is 127\&.0\&.0\&.1\&.
|
||||
The PEM formatted server certificate validation chain file\&.
|
||||
.RE
|
||||
.PP
|
||||
\fB\-\-csv\-file\-dir\fR\fIfile\fR
|
||||
.RS 4
|
||||
The directory name in which the user/password CSV file is stored (see AUTHENTICATION)\&. By default this option doesn\'t have any value, in which case the "\&.bind10" directory under the user\'s home directory will be used\&.
|
||||
.RE
|
||||
.PP
|
||||
\fB\-h\fR, \fB\-\-help\fR
|
||||
.RS 4
|
||||
Display command usage\&.
|
||||
@ -85,10 +90,10 @@ Display the version number and exit\&.
|
||||
.RE
|
||||
.SH "AUTHENTICATION"
|
||||
.PP
|
||||
The tool will authenticate using a username and password\&. On the first successful login, it will save the details to
|
||||
~/\&.bind10/default_user\&.csv
|
||||
which will be used for later uses of
|
||||
\fBbindctl\fR\&.
|
||||
The tool will authenticate using a username and password\&. On the first successful login, it will save the details to a comma\-separated\-value (CSV) file which will be used for later uses of
|
||||
\fBbindctl\fR\&. The file name is
|
||||
default_user\&.csv
|
||||
located under the directory specified by the \-\-csv\-file\-dir option\&.
|
||||
.SH "USAGE"
|
||||
.PP
|
||||
The
|
||||
|
Loading…
x
Reference in New Issue
Block a user