mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-09-03 07:25:18 +00:00
Code Issues Releases Wiki Activity

[jreed-docs] miscellaneous docs

Browse Source
This commit is contained in:
Jeremy C. Reed
2011-03-02 11:48:45 -06:00
parent e241028cc0
commit f664bc1482
1 changed files with 38 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
doc/guide/bind10-guide.xml
View File

@@ -1212,10 +1212,9 @@ TODO
<title>Incoming Zone Transfers</title> <title>Incoming Zone Transfers</title>
<para> <para>
The <command>b10-xfrin</command> process is started by Incoming zones are transferred using the <command>b10-xfrin</command>
<command>bind10</command>. process which is started by <command>bind10</command>.
It can be manually triggered to request an AXFR zone When received, the zone is stored in the BIND 10
transfer. When received, it is stored in the BIND 10
data store, and its records can be served by data store, and its records can be served by
<command>b10-auth</command>. <command>b10-auth</command>.
In combination with <command>b10-zonemgr</command> (for In combination with <command>b10-zonemgr</command> (for
@@ -1226,8 +1225,22 @@ TODO
<note><simpara> <note><simpara>
The current development release of BIND 10 only supports The current development release of BIND 10 only supports
AXFR. (IXFR is not supported.) AXFR. (IXFR is not supported.)
<!-- TODO: sqlite3 data source only? -->
</simpara></note> </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> <para>
To manually trigger a zone transfer to retrieve a remote zone, To manually trigger a zone transfer to retrieve a remote zone,
you may use the <command>bindctl</command> utility. you may use the <command>bindctl</command> utility.
@@ -1236,6 +1249,9 @@ TODO
<screen>&gt; <userinput>Xfrin retransfer zone_name="<option>foo.example.org</option>" master=<option>192.0.2.99</option></userinput></screen> <screen>&gt; <userinput>Xfrin retransfer zone_name="<option>foo.example.org</option>" master=<option>192.0.2.99</option></userinput></screen>
</para> </para>
<!-- TODO: can that retransfer be used to identify a new zone? -->
<!-- TODO: what if doesn't exits at that master IP? -->
</chapter> </chapter>
<chapter id="xfrout"> <chapter id="xfrout">
@@ -1342,28 +1358,34 @@ what is XfroutClient xfr_client??
<!-- TODO: later the above will have some defaults --> <!-- TODO: later the above will have some defaults -->
<para> <section>
To enable forwarding, the upstream address and port must be <title>Forwarding</title>
configured to forward queries to, such as:
<screen> <para>
To enable forwarding, the upstream address and port must be
configured to forward queries to, such as:
<screen>
&gt; <userinput>config set Resolver/forward_addresses [{ "address": "<replaceable>192.168.1.1</replaceable>", "port": 53 }]</userinput> &gt; <userinput>config set Resolver/forward_addresses [{ "address": "<replaceable>192.168.1.1</replaceable>", "port": 53 }]</userinput>
&gt; <userinput>config commit</userinput> &gt; <userinput>config commit</userinput>
</screen> </screen>
(Replace <replaceable>192.168.1.1</replaceable> to point to your (Replace <replaceable>192.168.1.1</replaceable> to point to your
full resolver.) full resolver.)
</para> </para>
<para> <para>
Normal iterative name service can be re-enabled by clearing the Normal iterative name service can be re-enabled by clearing the
forwarding address(es); for example: forwarding address(es); for example:
<screen> <screen>
&gt; <userinput>config set Resolver/forward_addresses []</userinput> &gt; <userinput>config set Resolver/forward_addresses []</userinput>
&gt; <userinput>config commit</userinput> &gt; <userinput>config commit</userinput>
</screen> </screen>
</para> </para>
</section>
<!-- TODO: later try this <!-- TODO: later try this