browsers.
- The statistics channel can now provide data in JSON
format as well as XML.
- - New stats counters track TCP and UDP queries recieved
+ - New stats counters track TCP and UDP queries received
per zone, and EDNS options received in total.
- The internal and export versions of the BIND libraries
(libisc, libdns, etc) have been unified so that external
<para>
Set the DSCP code point to be used when sending the
query. Valid DSCP code points are in the range
- [0..63]. By default no code point is explictly set.
+ [0..63]. By default no code point is explicitly set.
</para>
</listitem>
</varlistentry>
<term><option>+[no]subnet=addr/prefix</option></term>
<listitem>
<para>
- Send an EDNS Client Subnet option with the speciifed
+ Send an EDNS Client Subnet option with the specified
IP address or network prefix.
</para>
</listitem>
<para>
This option is mandatory unless the <option>-f</option> has
been used to specify a zone file. (If <option>-f</option> has
- been specified, this option may still be used; it will overrde
+ been specified, this option may still be used; it will override
the value found in the file.)
</para>
</listitem>
been used to specify a zone file, or a default key TTL was
set with the <option>-L</option> to
<command>dnssec-keygen</command>. (If either of those is true,
- this option may still be used; it will overrde the value found
+ this option may still be used; it will override the value found
in the zone or key file.)
</para>
</listitem>
The data data files in this directory are sample GeoIP databases,
generated from the corresponding CSV files. Thanks to MaxMind, Inc.
-for assitance with producing these files.
+for assistance with producing these files.
Unless otherwise noted, the databases only support IPv4:
GeoIPASNum.dat: AS Number
GeoIPNetSpeed.dat: Net Speed
-GeoIP.dat can also be egenerated using the open source 'geoip-csv-to-dat'
+GeoIP.dat can also be generated using the open source 'geoip-csv-to-dat'
utility:
$ geoip-csv-to-dat -i "BIND9 geoip test data v1" -o GeoIP.dat << EOF
In most cases, setting a value to 0 does not
literally mean zero; it means "undefined" or
"as big as possible", depending on the context.
- See the expalantions of particular parameters
+ See the explanations of particular parameters
that use <varname>size_spec</varname>
for details on how they interpret its use.
</para>
restarted (NTA's do not persist across restarts).
</para>
<para>
- For convienience, TTL-style time unit suffixes can be
+ For convenience, TTL-style time unit suffixes can be
used to specify the NTA lifetime in seconds, minutes
or hours. <option>nta-lifetime</option> defaults to
one hour. It cannot exceed one day.
the negative trust anchor is allowed to expire early.
</para>
<para>
- Validity checks can be disabled for an indivdiual
+ Validity checks can be disabled for an individual
NTA by using <command>rndc nta -f</command>, or
for all NTA's by setting <option>nta-recheck</option>
to zero.
</para>
<para>
- For convienience, TTL-style time unit suffixes can be
+ For convenience, TTL-style time unit suffixes can be
used to specify the NTA recheck interval in seconds,
minutes or hours. The default is five minutes.
</para>
than matching the case of the records entered in
the zone file. This allows responses to exactly
match the query, which is required by some clients
- due to incorrect use of case-sensitive comparisions.
+ due to incorrect use of case-sensitive comparisons.
</para>
<para>
Case-insensitive compression is <emphasis>always</emphasis>
the client matches this ACL.
</para>
<para>
- There are circusmstances in which <command>named</command>
+ There are circumstances in which <command>named</command>
will not preserve the case of owner names of records:
if a zone file defines records of different types with
the same name, but the capitalization of the name is
different (e.g., "www.example.com/A" and
- "WWW.EXAMPLE.COM/AAAA"), then all resposnes for that
+ "WWW.EXAMPLE.COM/AAAA"), then all responses for that
name will use the <emphasis>first</emphasis> version
of the name that was used in the zone file. This
limitation may be addressed in a future release. However,
is over 1000 <emphasis>and</emphasis> the ratio is over 10),
the one that appears last in the configuration file is the
one chosen. To eliminate any ambiguity, it is recommended
- that under normal circumstnaces, rate limiting bands should
+ that under normal circumstances, rate limiting bands should
be configured using either <command>size</command> or
<command>ratio</command> parameters, but not both.
</para>
<para>
Each RR can have a TTL as the second
field in the RR, which will control how long other
- servers can cache
- the it.
+ servers can cache it.
</para>
</entry>
</row>
<sect1 id="dlz-info">
<title>DLZ (Dynamically Loadable Zones)</title>
<para>
- DLZ (Dynamically Loadable Zones) is an extention to BIND 9 that allows
+ DLZ (Dynamically Loadable Zones) is an extension to BIND 9 that allows
zone data to be retrieved directly from an external database. There is
no required format or schema. DLZ drivers exist for several different
database backends including PostgreSQL, MySQL, and LDAP and can be
consists of a single domain name. Example:
<literallayout>
www.example.com
- mx.examle.net
+ mx.example.net
ns.xxx.example
</literallayout>
</listitem>
</itemizedlist>
<para>
The modified OpenSSL code is included in the BIND 9 release,
- in the form of a context diff against the latest verions of
+ in the form of a context diff against the latest versions of
OpenSSL. OpenSSL 0.9.8, 1.0.0, and 1.0.1 are supported; there are
separate diffs for each version. In the examples to follow,
we use OpenSSL 0.9.8, but the same methods work with OpenSSL
and address-to-hostname lookup services to applications by
transmitting lookup requests to a resolver daemon
<command>lwresd</command>
- running on the local host. The resover daemon performs the
+ running on the local host. The resolver daemon performs the
lookup using the DNS or possibly other name service protocols,
and returns the results to the application through the library.
The library and resolver daemon communicate using a simple
There are four main functions for the getaddrbyname opcode.
One render function converts a getaddrbyname request structure —
<type>lwres_gabnrequest_t</type> —
- to the lighweight resolver's canonical format.
+ to the lightweight resolver's canonical format.
It is complemented by a parse function that converts a packet in this
canonical format to a getaddrbyname request structure.
Another render function converts the getaddrbyname response structure
There are four main functions for the no-op opcode.
One render function converts a no-op request structure —
<type>lwres_nooprequest_t</type> —
- to the lighweight resolver's canonical format.
+ to the lightweight resolver's canonical format.
It is complemented by a parse function that converts a packet in this
canonical format to a no-op request structure.
Another render function converts the no-op response structure —
<para>
The lightweight resolver uses
<function>lwres_getaddrsbyname()</function> to perform
- foward lookups.
+ forward lookups.
Hostname <parameter>name</parameter> is looked up using the
resolver
context <parameter>ctx</parameter> for memory allocation.
projects / thirdparty / bind9.git / commitdiff
