|
@@ -52,7 +52,8 @@
|
|
|
<note>
|
|
|
<para>
|
|
|
BIND 10 provides a EDNS0- and DNSSEC-capable
|
|
|
- authoritative DNS server and a forwarding DNS server.
|
|
|
+ authoritative DNS server and a caching recursive name server
|
|
|
+ which also provides forwarding.
|
|
|
</para>
|
|
|
</note>
|
|
|
|
|
@@ -1308,12 +1309,6 @@ what is XfroutClient xfr_client??
|
|
|
-->
|
|
|
</para>
|
|
|
|
|
|
- <note><simpara>
|
|
|
- The current version only provides a forwarding DNS server.
|
|
|
- It does not cache and does not iterate to find answers.
|
|
|
- It simply forwards the query on to another full resolver.
|
|
|
- </simpara></note>
|
|
|
-
|
|
|
<para>
|
|
|
The main <command>bind10</command> process can be configured
|
|
|
to select to run either the authoritative or resolver.
|
|
@@ -1330,15 +1325,26 @@ what is XfroutClient xfr_client??
|
|
|
|
|
|
</para>
|
|
|
|
|
|
-<!-- TODO: -->
|
|
|
- <note><simpara>
|
|
|
- In the current version, the master <command>bind10</command>
|
|
|
- process must be stopped and restarted to start up the resolver.
|
|
|
- </simpara></note>
|
|
|
+ <para>
|
|
|
+ The master <command>bind10</command> will stop and start
|
|
|
+ the desired services.
|
|
|
+ </para>
|
|
|
|
|
|
<para>
|
|
|
- Then the upstream address and port must be configured to
|
|
|
- forward queries to, such as:
|
|
|
+ The resolver also needs to be configured to listen on an address
|
|
|
+ and port:
|
|
|
+
|
|
|
+ <screen>
|
|
|
+> <userinput>config set Resolver/listen_on [{ "address": "127.0.0.1", "port": 53 }]</userinput>
|
|
|
+> <userinput>config commit</userinput>
|
|
|
+</screen>
|
|
|
+ </para>
|
|
|
+
|
|
|
+<!-- 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:
|
|
|
|
|
|
<screen>
|
|
|
> <userinput>config set Resolver/forward_addresses [{ "address": "<replaceable>192.168.1.1</replaceable>", "port": 53 }]</userinput>
|
|
@@ -1350,17 +1356,15 @@ what is XfroutClient xfr_client??
|
|
|
</para>
|
|
|
|
|
|
<para>
|
|
|
- The resolver also needs to be configured to listen on an address
|
|
|
- and port:
|
|
|
+ Normal iterative name service can be re-enabled by clearing the
|
|
|
+ forwarding address(es); for example:
|
|
|
|
|
|
<screen>
|
|
|
-> <userinput>config set Resolver/listen_on [{ "address": "127.0.0.1", "port": 53 }]</userinput>
|
|
|
+> <userinput>config set Resolver/forward_addresses []</userinput>
|
|
|
> <userinput>config commit</userinput>
|
|
|
</screen>
|
|
|
</para>
|
|
|
|
|
|
-<!-- TODO: later the above will have some defaults -->
|
|
|
-
|
|
|
<!-- TODO: later try this
|
|
|
|
|
|
> config set Resolver/forward_addresses[0]/address "192.168.8.8"
|