mirror of
https://gitlab.isc.org/isc-projects/bind9
synced 2025-08-31 14:35:26 +00:00
regen HEAD
This commit is contained in:
@@ -14,7 +14,7 @@
|
||||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch03.html,v 1.82 2011/01/05 01:14:07 tbox Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch03.html,v 1.83 2011/01/21 01:14:13 tbox Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
@@ -282,7 +282,7 @@ zone "eng.example.com" {
|
||||
</p>
|
||||
<p>
|
||||
For more detail on ordering responses, check the
|
||||
<span><strong class="command">rrset-order</strong></span> substatement in the
|
||||
<span><strong class="command">rrset-order</strong></span> sub-statement in the
|
||||
<span><strong class="command">options</strong></span> statement, see
|
||||
<a href="Bv9ARM.ch06.html#rrset_ordering">RRset Ordering</a>.
|
||||
</p>
|
||||
|
@@ -14,7 +14,7 @@
|
||||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch06.html,v 1.273 2011/01/13 05:13:50 tbox Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch06.html,v 1.274 2011/01/21 01:14:13 tbox Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
@@ -2741,7 +2741,7 @@ options {
|
||||
IPv6 addresses will be ignored for the purposes
|
||||
of determining if dns64 is to be applied. Any
|
||||
non matching address will prevent any further
|
||||
DNS64 processing from occuring for this client.
|
||||
DNS64 processing from occurring for this client.
|
||||
</p>
|
||||
<p>
|
||||
A optional <span><strong class="command">suffix</strong></span> can also
|
||||
@@ -5030,7 +5030,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
|
||||
buffer (<span><strong class="command">edns-udp-size</strong></span>).
|
||||
</p>
|
||||
<p>
|
||||
Setting this to a low value will encourge additional
|
||||
Setting this to a low value will encourage additional
|
||||
TCP traffic to the nameserver.
|
||||
</p>
|
||||
</dd>
|
||||
@@ -6011,7 +6011,7 @@ ns.domain.com.rpz-nsdname CNAME .
|
||||
to the master file as soon as possible afterward; in the case
|
||||
of the managed key database, this will usually occur within 30
|
||||
seconds. So, whenever <span><strong class="command">named</strong></span> is using
|
||||
automatic key maintenace, those two files can be expected to
|
||||
automatic key maintenance, those two files can be expected to
|
||||
exist in the working directory. (For this reason among others,
|
||||
the working directory should be always be writable by
|
||||
<span><strong class="command">named</strong></span>.)
|
||||
@@ -7012,7 +7012,7 @@ example.com. NS ns2.example.net.
|
||||
<dd>
|
||||
<p>
|
||||
Zones configured for dynamic DNS may also use this
|
||||
option to allow varying levels of autonatic DNSSEC key
|
||||
option to allow varying levels of automatic DNSSEC key
|
||||
management. There are four possible settings:
|
||||
</p>
|
||||
<p>
|
||||
|
Reference in New Issue
Block a user