diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html index 0223911996..315a8e710c 100644 --- a/doc/arm/Bv9ARM.ch06.html +++ b/doc/arm/Bv9ARM.ch06.html @@ -91,7 +91,7 @@ HREF="Bv9ARM.ch06.html#Configuration_File_Grammar" >
The identity field specifies a name or a wildcard name. The -nametype field has 4 values: The identity field specifies a name or a wildcard name. Normally, this +is the name of the TSIG or SIG(0) key used to sign the update request. When a +TKEY exchange has been used to create a shared secret, the identity of the +shared secret is the same as the identity of the key used to authenticate the +TKEY exchange. When the identity field specifies a +wildcard name, it is subject to DNS wildcard expansion, so the rule will apply +to multiple identities. The identity field must +contain a fully qualified domain name.
The nametype field has 4 values: +name, subdomain, , +wildcard, -and , and self +>.
Matches when the updated name is the -same as the name in the name field.
Exact-match semantics. This rule matches when the +name being updated is identical to the contents of the +name field.Matches when the updated name is a subdomain -of the name in the name field (which includes the name itself).
This rule matches when the name being updated +is a subdomain of, or identical to, the contents of the +name field.Matches when the updated name is a valid -expansion of the wildcard name in the name field.
The name field is +subject to DNS wildcard expansion, and this rule matches when the name +being updated name is a valid expansion of the wildcard.Matches when the updated name is the -same as the message signer. The name field is ignored.
This rule matches when the name being updated +matches the contents of the identity field. +The name field is ignored, but should be +the same as the identity field. The +self nametype is most useful when allowing using +one key per name to update, where the key has the same name as the name +to be updated. The identity would be +specified as * in this case.If no types are specified, the rule matches all types except +>In all cases, the name field must +specify a fully qualified domain name.
If no types are explicitly specified, this rule matches all types except SIG, NS, SOA, and NXT. Types may be specified by name, including "ANY" (ANY matches all types except NXT, which can never be updated). +Note that when an attempt is made to delete all records associated with a +name, the rules are checked for each existing record type.
[RFC974] [RFC1034] [RFC1035] [RFC2181] [RFC2308] [RFC1995] [RFC1996] [RFC2136] [RFC2845] [RFC1886] [RFC2065] [RFC2137] [RFC1535] [RFC1536] [RFC1982] [RFC1183] [RFC1706] [RFC2168] [RFC1876] [RFC2052] [RFC2163] [RFC2230] [RFC1101] [RFC1123] [RFC1591] [RFC2317] [RFC1537] [RFC1912] [RFC1912] [RFC2010] [RFC2219] [RFC1464] [RFC1713] [RFC1794] [RFC2240] [RFC2345] [RFC2352] [RFC1712] Proposed Standards Still Under Development
Other Important RFCs About DNS
Resource Record Types
DNS
DNS
Other DNS
Obsolete and Unimplemented Experimental RRs
A.3.3. Other Documents About BIND
Bibliography