+4237. [doc] Upgraded documentation toolchain to use DocBook 5
+ and dblatex. [RT #40766]
+
4236. [func] On machines with 2 or more processors (CPU), the
default value for the number of UDP listeners
has been changed to the number of detected
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" []>
<!--
- Copyright (C) 2004-2010, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<!-- $Id: FAQ.xml,v 1.54 2010/01/19 23:48:55 tbox Exp $ -->
-
-<article class="faq">
- <title>Frequently Asked Questions about BIND 9</title>
- <articleinfo>
+<!-- Converted by db4-upgrade version 1.0 -->
+<article xmlns="http://docbook.org/ns/docbook" version="5.0" class="faq">
+
+ <info>
<copyright>
<year>2004</year>
<year>2005</year>
<year>2003</year>
<holder>Internet Software Consortium.</holder>
</copyright>
- </articleinfo>
- <qandaset defaultlabel='qanda'>
+ </info>
+ <qandaset defaultlabel="qanda">
- <qandadiv><title>Compilation and Installation Questions</title>
+ <qandadiv>
<qandaentry>
<question>
</qandadiv> <!-- Compilation and Installation Questions -->
- <qandadiv><title>Configuration and Setup Questions</title>
+ <qandadiv>
<qandaentry>
<!-- configuration, log -->
You are running chrooted (-t) and have not supplied local timezone
information in the chroot area.
</para>
- <simplelist>
+ <simplelist type="vert">
<member>FreeBSD: /etc/localtime</member>
<member>Solaris: /etc/TIMEZONE and /usr/share/lib/zoneinfo</member>
<member>OSF: /etc/zoneinfo/localtime</member>
</qandadiv> <!-- Configuration and Setup Questions -->
- <qandadiv><title>Operations Questions</title>
+ <qandadiv>
<qandaentry>
<question>
</qandadiv> <!-- Operations Questions -->
- <qandadiv><title>General Questions</title>
+ <qandadiv>
<qandaentry>
<question>
of sending dynamic update requests to DNS servers without
being specifically configured to do so. If the update
requests are coming from a Windows 2000 machine, see
- <ulink
- url="http://support.microsoft.com/support/kb/articles/q246/8/04.asp">
- <http://support.microsoft.com/support/kb/articles/q246/8/04.asp></ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://support.microsoft.com/support/kb/articles/q246/8/04.asp">
+ <http://support.microsoft.com/support/kb/articles/q246/8/04.asp></link>
for information about how to turn them off.
</para>
</answer>
usage rules and are leaking queries to the Internet. You
should establish your own zones for these addresses to prevent
you querying the Internet's name servers for these addresses.
- Please see <ulink url="http://as112.net/"><http://as112.net/></ulink>
+ Please see <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://as112.net/"><http://as112.net/></link>
for details of the problems you are causing and the counter
measures that have had to be deployed.
</para>
</qandadiv> <!-- General Questions -->
- <qandadiv><title>Operating-System Specific Questions</title>
+ <qandadiv>
- <qandadiv><title>HPUX</title>
+ <qandadiv>
<qandaentry>
<question>
</qandadiv> <!-- HPUX -->
- <qandadiv><title>Linux</title>
+ <qandadiv>
<qandaentry>
<question>
</para>
<para>
See:
- <ulink url="http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=2"><http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=2></ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=2"><http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=2></link>
</para>
</answer>
</qandaentry>
non-blocking is ignored. It is reported that setting
xfrm_larval_drop to 1 helps but this may have negative side effects.
See:
-<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=427629"><https://bugzilla.redhat.com/show_bug.cgi?id=427629></ulink>
+<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://bugzilla.redhat.com/show_bug.cgi?id=427629"><https://bugzilla.redhat.com/show_bug.cgi?id=427629></link>
and
-<ulink url="http://lkml.org/lkml/2007/12/4/260"><http://lkml.org/lkml/2007/12/4/260></ulink>.
+<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://lkml.org/lkml/2007/12/4/260"><http://lkml.org/lkml/2007/12/4/260></link>.
</para>
<para>
xfrm_larval_drop can be set to 1 by the following procedure:
<para>
Red Hat have adopted the National Security Agency's
- SELinux security policy (see <ulink
- url="http://www.nsa.gov/selinux"><http://www.nsa.gov/selinux></ulink>)
+ SELinux security policy (see <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.nsa.gov/selinux"><http://www.nsa.gov/selinux></link>)
and recommendations for BIND security , which are more
secure than running named in a chroot and make use of
the bind-chroot environment unnecessary .
</question>
<answer>
<para>
- Ubuntu uses AppArmor <ulink url="http://en.wikipedia.org/wiki/AppArmor">
- <http://en.wikipedia.org/wiki/AppArmor></ulink> in
+ Ubuntu uses AppArmor <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://en.wikipedia.org/wiki/AppArmor">
+ <http://en.wikipedia.org/wiki/AppArmor></link> in
addition to normal file system permissions to protect the system.
</para>
<para>
</qandadiv> <!-- Linux -->
- <qandadiv><title>Windows</title>
+ <qandadiv>
<qandaentry>
<question>
</qandadiv> <!-- Windows -->
- <qandadiv><title>FreeBSD</title>
+ <qandadiv>
<qandaentry>
<question>
</informalexample>
<para>
See also
- <ulink url="http://people.freebsd.org/~dougb/randomness.html">
- <http://people.freebsd.org/~dougb/randomness.html></ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://people.freebsd.org/~dougb/randomness.html">
+ <http://people.freebsd.org/~dougb/randomness.html></link>.
</para>
</answer>
</qandaentry>
</qandadiv> <!-- FreeBSD -->
- <qandadiv><title>Solaris</title>
+ <qandadiv>
<qandaentry>
<question>
Sun has a blog entry describing how to do this.
</para>
<para>
- <ulink
- url="http://blogs.sun.com/roller/page/anay/Weblog?catname=%2FSolaris">
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://blogs.sun.com/roller/page/anay/Weblog?catname=%2FSolaris">
<http://blogs.sun.com/roller/page/anay/Weblog?catname=%2FSolaris>
- </ulink>
+ </link>
</para>
</answer>
</qandaentry>
</qandadiv>
- <qandadiv><title>Apple Mac OS X</title>
+ <qandadiv>
<qandaentry>
<question>
</para>
<informalexample>
<programlisting>
-% sudo rndc-confgen > /etc/rndc.conf</programlisting>
+% sudo rndc-confgen > /etc/rndc.conf</programlisting>
</informalexample>
<para>
Copy the key statement from /etc/rndc.conf into /etc/rndc.key, e.g.:
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2009, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2002 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.named-checkconf">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.named-checkconf">
+ <info>
+ <date>2014-01-10</date>
+ </info>
<refentryinfo>
- <date>January 10, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</refnamediv>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>named-checkconf</command>
- <arg><option>-h</option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-j</option></arg>
- <arg><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
- <arg choice="req">filename</arg>
- <arg><option>-p</option></arg>
- <arg><option>-x</option></arg>
- <arg><option>-z</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-j</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">filename</arg>
+ <arg choice="opt" rep="norepeat"><option>-p</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-x</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-z</option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>named-checkconf</command>
checks the syntax, but not the semantics, of a
<command>named</command> configuration file. The file is parsed
successful. <command>named-checkconf</command> can be run
on these files explicitly, however.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para><command>named-checkconf</command>
returns an exit status of 1 if
errors were detected and 0 otherwise.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
-
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2007, 2009-2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2002 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.named-checkzone">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.named-checkzone">
+ <info>
+ <date>2014-02-19</date>
+ </info>
<refentryinfo>
- <date>February 19, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</refnamediv>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>named-checkzone</command>
- <arg><option>-d</option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-j</option></arg>
- <arg><option>-q</option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">format</replaceable></option></arg>
- <arg><option>-F <replaceable class="parameter">format</replaceable></option></arg>
- <arg><option>-J <replaceable class="parameter">filename</replaceable></option></arg>
- <arg><option>-i <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-k <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-m <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-M <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-n <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-l <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
- <arg><option>-o <replaceable class="parameter">filename</replaceable></option></arg>
- <arg><option>-r <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-s <replaceable class="parameter">style</replaceable></option></arg>
- <arg><option>-S <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-T <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-w <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-D</option></arg>
- <arg><option>-W <replaceable class="parameter">mode</replaceable></option></arg>
- <arg choice="req">zonename</arg>
- <arg choice="req">filename</arg>
+ <arg choice="opt" rep="norepeat"><option>-d</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-j</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-F <replaceable class="parameter">format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-J <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-M <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-o <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">style</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-S <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-T <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-w <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-W <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">zonename</arg>
+ <arg choice="req" rep="norepeat">filename</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>named-compilezone</command>
- <arg><option>-d</option></arg>
- <arg><option>-j</option></arg>
- <arg><option>-q</option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-C <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">format</replaceable></option></arg>
- <arg><option>-F <replaceable class="parameter">format</replaceable></option></arg>
- <arg><option>-J <replaceable class="parameter">filename</replaceable></option></arg>
- <arg><option>-i <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-k <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-m <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-n <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-l <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
- <arg><option>-r <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-s <replaceable class="parameter">style</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-T <replaceable class="parameter">mode</replaceable></option></arg>
- <arg><option>-w <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-D</option></arg>
- <arg><option>-W <replaceable class="parameter">mode</replaceable></option></arg>
- <arg choice="req"><option>-o <replaceable class="parameter">filename</replaceable></option></arg>
- <arg choice="req">zonename</arg>
- <arg choice="req">filename</arg>
+ <arg choice="opt" rep="norepeat"><option>-d</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-j</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-C <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-F <replaceable class="parameter">format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-J <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">style</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-T <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-w <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-W <replaceable class="parameter">mode</replaceable></option></arg>
+ <arg choice="req" rep="norepeat"><option>-o <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">zonename</arg>
+ <arg choice="req" rep="norepeat">filename</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>named-checkzone</command>
checks the syntax and integrity of a zone file. It performs the
same checks as <command>named</command> does when loading a
least be as strict as those specified in the
<command>named</command> configuration file.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para><command>named-checkzone</command>
returns an exit status of 1 if
errors were detected and 0 otherwise.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>RFC 1035</citetitle>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.ddns-confgen">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.ddns-confgen">
+ <info>
+ <date>2014-03-06</date>
+ </info>
<refentryinfo>
- <date>March 6, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>tsig-keygen</command>
- <arg><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-r <replaceable class="parameter">randomfile</replaceable></option></arg>
- <arg choice="opt">name</arg>
+ <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">randomfile</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat">name</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>ddns-confgen</command>
- <arg><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-k <replaceable class="parameter">keyname</replaceable></option></arg>
- <arg><option>-q</option></arg>
- <arg><option>-r <replaceable class="parameter">randomfile</replaceable></option></arg>
- <group>
- <arg choice="plain">-s <replaceable class="parameter">name</replaceable></arg>
- <arg choice="plain">-z <replaceable class="parameter">zone</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">keyname</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">randomfile</replaceable></option></arg>
+ <group choice="opt" rep="norepeat">
+ <arg choice="plain" rep="norepeat">-s <replaceable class="parameter">name</replaceable></arg>
+ <arg choice="plain" rep="norepeat">-z <replaceable class="parameter">zone</replaceable></arg>
</group>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>tsig-keygen</command> and <command>ddns-confgen</command>
are invocation methods for a utility that generates keys for use
if <command>nsupdate</command> is to be used from a remote
system.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>nsupdate</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2009, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2001, 2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.rndc-confgen">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.rndc-confgen">
+ <info>
+ <date>2013-03-14</date>
+ </info>
<refentryinfo>
- <date>March 14, 2013</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>rndc-confgen</command>
- <arg><option>-a</option></arg>
- <arg><option>-A <replaceable class="parameter">algorithm</replaceable></option></arg>
- <arg><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
- <arg><option>-c <replaceable class="parameter">keyfile</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-k <replaceable class="parameter">keyname</replaceable></option></arg>
- <arg><option>-p <replaceable class="parameter">port</replaceable></option></arg>
- <arg><option>-r <replaceable class="parameter">randomfile</replaceable></option></arg>
- <arg><option>-s <replaceable class="parameter">address</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">chrootdir</replaceable></option></arg>
- <arg><option>-u <replaceable class="parameter">user</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-a</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-A <replaceable class="parameter">algorithm</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">keyfile</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">keyname</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">port</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">randomfile</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">address</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">chrootdir</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-u <replaceable class="parameter">user</replaceable></option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>rndc-confgen</command>
generates configuration files
for <command>rndc</command>. It can be used as a
and a <command>controls</command> statement altogether.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>EXAMPLES</title>
+ <refsection><info><title>EXAMPLES</title></info>
+
<para>
To allow <command>rndc</command> to be used with
no manual configuration, run
</para>
<para><userinput>rndc-confgen</userinput>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>rndc</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.delv">
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.delv">
+ <info>
+ <date>2014-04-23</date>
+ </info>
<refentryinfo>
- <date>April 23, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>delv</command>
- <arg choice="opt">@server</arg>
- <arg><option>-4</option></arg>
- <arg><option>-6</option></arg>
- <arg><option>-a <replaceable class="parameter">anchor-file</replaceable></option></arg>
- <arg><option>-b <replaceable class="parameter">address</replaceable></option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-d <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-i</option></arg>
- <arg><option>-m</option></arg>
- <arg><option>-p <replaceable class="parameter">port#</replaceable></option></arg>
- <arg><option>-q <replaceable class="parameter">name</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">type</replaceable></option></arg>
- <arg><option>-x <replaceable class="parameter">addr</replaceable></option></arg>
- <arg choice="opt">name</arg>
- <arg choice="opt">type</arg>
- <arg choice="opt">class</arg>
+ <arg choice="opt" rep="norepeat">@server</arg>
+ <arg choice="opt" rep="norepeat"><option>-4</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-6</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">anchor-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">address</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">port#</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q <replaceable class="parameter">name</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">type</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-x <replaceable class="parameter">addr</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat">name</arg>
+ <arg choice="opt" rep="norepeat">type</arg>
+ <arg choice="opt" rep="norepeat">class</arg>
<arg choice="opt" rep="repeat">queryopt</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>delv</command>
- <arg><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>delv</command>
- <arg><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>delv</command>
<arg choice="opt" rep="repeat">queryopt</arg>
<arg choice="opt" rep="repeat">query</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>delv</command>
(Domain Entity Lookup & Validation) is a tool for sending
DNS queries and validating the results, using the same internal
<command>delv</command> will perform an NS query for "."
(the root zone).
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SIMPLE USAGE</title>
+ <refsection><info><title>SIMPLE USAGE</title></info>
+
<para>
A typical invocation of <command>delv</command> looks like:
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>QUERY OPTIONS</title>
+ <refsection><info><title>QUERY OPTIONS</title></info>
+
<para><command>delv</command>
provides a number of query options which affect the way results are
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<para><filename>/etc/bind.keys</filename></para>
<para><filename>/etc/resolv.conf</filename></para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dig</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,
<citetitle>RFC5074</citetitle>,
<citetitle>RFC5155</citetitle>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2011, 2013-2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dig">
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dig">
+ <info>
+ <date>2014-02-19</date>
+ </info>
<refentryinfo>
- <date>February 19, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dig</command>
- <arg choice="opt">@server</arg>
- <arg><option>-b <replaceable class="parameter">address</replaceable></option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">filename</replaceable></option></arg>
- <arg><option>-k <replaceable class="parameter">filename</replaceable></option></arg>
- <arg><option>-m</option></arg>
- <arg><option>-p <replaceable class="parameter">port#</replaceable></option></arg>
- <arg><option>-q <replaceable class="parameter">name</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">type</replaceable></option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-x <replaceable class="parameter">addr</replaceable></option></arg>
- <arg><option>-y <replaceable class="parameter"><optional>hmac:</optional>name:key</replaceable></option></arg>
- <arg><option>-4</option></arg>
- <arg><option>-6</option></arg>
- <arg choice="opt">name</arg>
- <arg choice="opt">type</arg>
- <arg choice="opt">class</arg>
+ <arg choice="opt" rep="norepeat">@server</arg>
+ <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">address</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">port#</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q <replaceable class="parameter">name</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">type</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-x <replaceable class="parameter">addr</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-y <replaceable class="parameter"><optional>hmac:</optional>name:key</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-4</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-6</option></arg>
+ <arg choice="opt" rep="norepeat">name</arg>
+ <arg choice="opt" rep="norepeat">type</arg>
+ <arg choice="opt" rep="norepeat">class</arg>
<arg choice="opt" rep="repeat">queryopt</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dig</command>
- <arg><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dig</command>
<arg choice="opt" rep="repeat">global-queryopt</arg>
<arg choice="opt" rep="repeat">query</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dig</command>
(domain information groper) is a flexible tool
for interrogating DNS name servers. It performs DNS lookups and
use "IN." and "CH." when looking up these top level domains.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SIMPLE USAGE</title>
+ <refsection><info><title>SIMPLE USAGE</title></info>
+
<para>
A typical invocation of <command>dig</command> looks like:
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>QUERY OPTIONS</title>
+ <refsection><info><title>QUERY OPTIONS</title></info>
+
<para><command>dig</command>
provides a number of query options which affect
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>MULTIPLE QUERIES</title>
+ <refsection><info><title>MULTIPLE QUERIES</title></info>
+
<para>
The BIND 9 implementation of <command>dig </command>
<literal>isc.org</literal>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>IDN SUPPORT</title>
+ <refsection><info><title>IDN SUPPORT</title></info>
+
<para>
If <command>dig</command> has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
The IDN support is disabled if the variable is set when
<command>dig</command> runs.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<para><filename>/etc/resolv.conf</filename>
</para>
<para><filename>${HOME}/.digrc</filename>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>host</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,
</citerefentry>,
<citetitle>RFC1035</citetitle>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>BUGS</title>
+ <refsection><info><title>BUGS</title></info>
+
<para>
There are probably too many query options.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007-2009, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2002 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.host">
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.host">
+ <info>
+ <date>2009-01-20</date>
+ </info>
<refentryinfo>
- <date>January 20, 2009</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>host</command>
- <arg><option>-aCdlnrsTwv</option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-N <replaceable class="parameter">ndots</replaceable></option></arg>
- <arg><option>-R <replaceable class="parameter">number</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">type</replaceable></option></arg>
- <arg><option>-W <replaceable class="parameter">wait</replaceable></option></arg>
- <arg><option>-m <replaceable class="parameter">flag</replaceable></option></arg>
- <arg><option>-4</option></arg>
- <arg><option>-6</option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-V</option></arg>
- <arg choice="req">name</arg>
- <arg choice="opt">server</arg>
+ <arg choice="opt" rep="norepeat"><option>-aCdlnrsTwv</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-N <replaceable class="parameter">ndots</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-R <replaceable class="parameter">number</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">type</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-W <replaceable class="parameter">wait</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">flag</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-4</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-6</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="req" rep="norepeat">name</arg>
+ <arg choice="opt" rep="norepeat">server</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>host</command>
is a simple utility for performing DNS lookups.
The <option>-V</option> option causes <command>host</command>
to print the version number and exit.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>IDN SUPPORT</title>
+ <refsection><info><title>IDN SUPPORT</title></info>
+
<para>
If <command>host</command> has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
The IDN support is disabled if the variable is set when
<command>host</command> runs.
</para>
- </refsect1>
+ </refsection>
+
+ <refsection><info><title>FILES</title></info>
- <refsect1>
- <title>FILES</title>
<para><filename>/etc/resolv.conf</filename>
</para>
- </refsect1>
+ </refsection>
+
+ <refsection><info><title>SEE ALSO</title></info>
- <refsect1>
- <title>SEE ALSO</title>
<para><citerefentry>
<refentrytitle>dig</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>.
</para>
+ </refsection>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2007, 2010, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGE.
-->
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2014-01-24</date>
+ </info>
<refentryinfo>
- <date>January 24, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>nslookup</command>
- <arg><option>-option</option></arg>
- <arg choice="opt">name | -</arg>
- <arg choice="opt">server</arg>
+ <arg choice="opt" rep="norepeat"><option>-option</option></arg>
+ <arg choice="opt" rep="norepeat">name | -</arg>
+ <arg choice="opt" rep="norepeat">server</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>Nslookup</command>
is a program to query Internet domain name servers. <command>Nslookup</command>
has two modes: interactive and non-interactive. Interactive mode allows
used to print just the name and requested information for a host or
domain.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ARGUMENTS</title>
+ <refsection><info><title>ARGUMENTS</title></info>
+
<para>
Interactive mode is entered in the following cases:
- <orderedlist numeration="loweralpha">
+ <orderedlist numeration="loweralpha" inheritnum="ignore" continuation="restarts">
<listitem>
<para>
when no arguments are given (the default name server will be used)
number and immediately exits.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>INTERACTIVE COMMANDS</title>
+ <refsection><info><title>INTERACTIVE COMMANDS</title></info>
+
<variablelist>
<varlistentry>
<term><constant>host</constant> <optional>server</optional></term>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<para><filename>/etc/resolv.conf</filename>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dig</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>.
</para>
- </refsect1>
-
- <refsect1>
- <title>Author</title>
- <para>
- Andrew Cherenson
- </para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2008-2012, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-dsfromkey">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-dsfromkey">
+ <info>
+ <date>2012-05-02</date>
+ </info>
<refentryinfo>
- <date>May 02, 2012</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-dsfromkey</command>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-1</option></arg>
- <arg><option>-2</option></arg>
- <arg><option>-a <replaceable class="parameter">alg</replaceable></option></arg>
- <arg><option>-C</option></arg>
- <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
- <arg><option>-T <replaceable class="parameter">TTL</replaceable></option></arg>
- <arg choice="req">keyfile</arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-1</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-2</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">alg</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-C</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-T <replaceable class="parameter">TTL</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">keyfile</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-dsfromkey</command>
- <arg choice="req">-s</arg>
- <arg><option>-1</option></arg>
- <arg><option>-2</option></arg>
- <arg><option>-a <replaceable class="parameter">alg</replaceable></option></arg>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
- <arg><option>-s</option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-T <replaceable class="parameter">TTL</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">file</replaceable></option></arg>
- <arg><option>-A</option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg choice="req">dnsname</arg>
+ <arg choice="req" rep="norepeat">-s</arg>
+ <arg choice="opt" rep="norepeat"><option>-1</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-2</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">alg</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-T <replaceable class="parameter">TTL</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-A</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">dnsname</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-dsfromkey</command>
- <arg><option>-h</option></arg>
- <arg><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-dsfromkey</command>
outputs the Delegation Signer (DS) resource record (RR), as defined in
RFC 3658 and RFC 4509, for the given key(s).
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>EXAMPLE</title>
+ <refsection><info><title>EXAMPLE</title></info>
+
<para>
To build the SHA-256 DS RR from the
<userinput>Kexample.com.+003+26160</userinput>
</para>
<para><userinput>example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94</userinput>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<para>
The keyfile can be designed by the key identification
<filename>Knnnn.+aaa+iiiii</filename> or the full file name
the string <filename>keyset-</filename> and the
<option>dnsname</option>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>CAVEAT</title>
+ <refsection><info><title>CAVEAT</title></info>
+
<para>
A keyfile error can give a "file not found" even if the file exists.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>RFC 4431</citetitle>.
<citetitle>RFC 4509</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-importkey">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-importkey">
+ <info>
+ <date>2014-02-20</date>
+ </info>
<refentryinfo>
- <date>February 20, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-importkey</command>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-V</option></arg>
- <arg choice="req"><option>keyfile</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="req" rep="norepeat"><option>keyfile</option></arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-importkey</command>
- <arg choice="req"><option>-f <replaceable class="parameter">filename</replaceable></option></arg>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-V</option></arg>
- <arg><option>dnsname</option></arg>
+ <arg choice="req" rep="norepeat"><option>-f <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>dnsname</option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-importkey</command>
reads a public DNSKEY record and generates a pair of
.key/.private files. The DNSKEY record may be read from an
public key can be added to and removed from the DNSKEY RRset
on schedule even if the true private key is stored offline.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>TIMING OPTIONS</title>
+ <refsection><info><title>TIMING OPTIONS</title></info>
+
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<para>
A keyfile can be designed by the key identification
<filename>Knnnn.+aaa+iiiii</filename> or the full file name
<filename>Knnnn.+aaa+iiiii.key</filename> as generated by
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 5011</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2008-2012, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-keyfromlabel">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-keyfromlabel">
+ <info>
+ <date>2014-02-27</date>
+ </info>
<refentryinfo>
- <date>February 27, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-keyfromlabel</command>
- <arg choice="req">-l <replaceable class="parameter">label</replaceable></arg>
- <arg><option>-3</option></arg>
- <arg><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
- <arg><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">flag</replaceable></option></arg>
- <arg><option>-G</option></arg>
- <arg><option>-I <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
- <arg><option>-k</option></arg>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-n <replaceable class="parameter">nametype</replaceable></option></arg>
- <arg><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-p <replaceable class="parameter">protocol</replaceable></option></arg>
- <arg><option>-R <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-S <replaceable class="parameter">key</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">type</replaceable></option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-y</option></arg>
- <arg choice="req">name</arg>
+ <arg choice="req" rep="norepeat">-l <replaceable class="parameter">label</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><option>-3</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">flag</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-G</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-I <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">nametype</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">protocol</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-R <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-S <replaceable class="parameter">key</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">type</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-y</option></arg>
+ <arg choice="req" rep="norepeat">name</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-keyfromlabel</command>
generates a key pair of files that referencing a key object stored
in a cryptographic hardware service module (HSM). The private key
line. This must match the name of the zone for which the key is
being generated.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>TIMING OPTIONS</title>
+ <refsection><info><title>TIMING OPTIONS</title></info>
+
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>GENERATED KEY FILES</title>
+ <refsection><info><title>GENERATED KEY FILES</title></info>
+
<para>
When <command>dnssec-keyfromlabel</command> completes
successfully,
fields. For obvious security reasons, this file does not have
general read permission.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>RFC 4034</citetitle>,
<citetitle>The PKCS#11 URI Scheme (draft-pechanec-pkcs11uri-13)</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007-2012, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-keygen">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-keygen">
+ <info>
+ <date>2014-02-06</date>
+ </info>
<refentryinfo>
- <date>February 06, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-keygen</command>
- <arg><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
- <arg ><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
- <arg><option>-n <replaceable class="parameter">nametype</replaceable></option></arg>
- <arg><option>-3</option></arg>
- <arg><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-C</option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">flag</replaceable></option></arg>
- <arg><option>-G</option></arg>
- <arg><option>-g <replaceable class="parameter">generator</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-I <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-k</option></arg>
- <arg><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-p <replaceable class="parameter">protocol</replaceable></option></arg>
- <arg><option>-q</option></arg>
- <arg><option>-R <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
- <arg><option>-S <replaceable class="parameter">key</replaceable></option></arg>
- <arg><option>-s <replaceable class="parameter">strength</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">type</replaceable></option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-z</option></arg>
- <arg choice="req">name</arg>
+ <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">nametype</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-3</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-C</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">flag</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-G</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-g <replaceable class="parameter">generator</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-I <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">protocol</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-R <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-S <replaceable class="parameter">key</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">strength</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">type</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-z</option></arg>
+ <arg choice="req" rep="norepeat">name</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-keygen</command>
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
and RFC 4034. It can also generate keys for use with
line. For DNSSEC keys, this must match the name of the zone for
which the key is being generated.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>TIMING OPTIONS</title>
+ <refsection><info><title>TIMING OPTIONS</title></info>
+
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>GENERATED KEYS</title>
+ <refsection><info><title>GENERATED KEYS</title></info>
+
<para>
When <command>dnssec-keygen</command> completes
successfully,
files are generated for symmetric encryption algorithms such as
HMAC-MD5, even though the public and private key are equivalent.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>EXAMPLE</title>
+ <refsection><info><title>EXAMPLE</title></info>
+
<para>
To generate a 768-bit DSA key for the domain
<userinput>example.com</userinput>, the following command would be
and
<filename>Kexample.com.+003+26160.private</filename>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>RFC 2845</citetitle>,
<citetitle>RFC 4034</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2011, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-revoke">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-revoke">
+ <info>
+ <date>2014-01-15</date>
+ </info>
<refentryinfo>
- <date>January 15, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-revoke</command>
- <arg><option>-hr</option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
- <arg><option>-f</option></arg>
- <arg><option>-R</option></arg>
- <arg choice="req">keyfile</arg>
+ <arg choice="opt" rep="norepeat"><option>-hr</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-R</option></arg>
+ <arg choice="req" rep="norepeat">keyfile</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-revoke</command>
reads a DNSSEC key file, sets the REVOKED bit on the key as defined
in RFC 5011, and creates a new pair of key files containing the
now-revoked key.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 5011</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009-2011, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-settime">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-settime">
+ <info>
+ <date>2014-02-06</date>
+ </info>
<refentryinfo>
- <date>February 06, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-settime</command>
- <arg><option>-f</option></arg>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-R <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-I <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
- <arg choice="req">keyfile</arg>
+ <arg choice="opt" rep="norepeat"><option>-f</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-R <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-I <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">keyfile</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-settime</command>
reads a DNSSEC private key file and sets the key timing metadata
as specified by the <option>-P</option>, <option>-A</option>,
file. The private file's permissions are always set to be
inaccessible to anyone other than the owner (mode 0600).
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>TIMING OPTIONS</title>
+ <refsection><info><title>TIMING OPTIONS</title></info>
+
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>PRINTING OPTIONS</title>
+ <refsection><info><title>PRINTING OPTIONS</title></info>
+
<para>
<command>dnssec-settime</command> can also be used to print the
timing metadata associated with a key.
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 5011</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2009, 2011-2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-signzone">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-signzone">
+ <info>
+ <date>2014-02-18</date>
+ </info>
<refentryinfo>
- <date>February 18, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-signzone</command>
- <arg><option>-a</option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-d <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-D</option></arg>
- <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
- <arg><option>-e <replaceable class="parameter">end-time</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">output-file</replaceable></option></arg>
- <arg><option>-g</option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-k <replaceable class="parameter">key</replaceable></option></arg>
- <arg><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
- <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
- <arg><option>-M <replaceable class="parameter">domain</replaceable></option></arg>
- <arg><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
- <arg><option>-I <replaceable class="parameter">input-format</replaceable></option></arg>
- <arg><option>-j <replaceable class="parameter">jitter</replaceable></option></arg>
- <arg><option>-N <replaceable class="parameter">soa-serial-format</replaceable></option></arg>
- <arg><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
- <arg><option>-O <replaceable class="parameter">output-format</replaceable></option></arg>
- <arg><option>-P</option></arg>
- <arg><option>-p</option></arg>
- <arg><option>-Q</option></arg>
- <arg><option>-R</option></arg>
- <arg><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
- <arg><option>-S</option></arg>
- <arg><option>-s <replaceable class="parameter">start-time</replaceable></option></arg>
- <arg><option>-T <replaceable class="parameter">ttl</replaceable></option></arg>
- <arg><option>-t</option></arg>
- <arg><option>-u</option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-X <replaceable class="parameter">extended end-time</replaceable></option></arg>
- <arg><option>-x</option></arg>
- <arg><option>-z</option></arg>
- <arg><option>-3 <replaceable class="parameter">salt</replaceable></option></arg>
- <arg><option>-H <replaceable class="parameter">iterations</replaceable></option></arg>
- <arg><option>-A</option></arg>
- <arg choice="req">zonefile</arg>
- <arg rep="repeat">key</arg>
+ <arg choice="opt" rep="norepeat"><option>-a</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-e <replaceable class="parameter">end-time</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">output-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-g</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">key</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-M <replaceable class="parameter">domain</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-I <replaceable class="parameter">input-format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-j <replaceable class="parameter">jitter</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-N <replaceable class="parameter">soa-serial-format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-O <replaceable class="parameter">output-format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-Q</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-R</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-S</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">start-time</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-T <replaceable class="parameter">ttl</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-u</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-X <replaceable class="parameter">extended end-time</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-x</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-z</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-3 <replaceable class="parameter">salt</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-H <replaceable class="parameter">iterations</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-A</option></arg>
+ <arg choice="req" rep="norepeat">zonefile</arg>
+ <arg rep="repeat" choice="opt">key</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-signzone</command>
signs a zone. It generates
NSEC and RRSIG records and produces a signed version of the
determined by the presence or absence of a
<filename>keyset</filename> file for each child zone.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>EXAMPLE</title>
+ <refsection><info><title>EXAMPLE</title></info>
+
<para>
The following command signs the <userinput>example.com</userinput>
zone with the DSA key generated by <command>dnssec-keygen</command>
% dnssec-signzone -o example.com db.example.com
db.example.com.signed
%</programlisting>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 4033</citetitle>, <citetitle>RFC 4641</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2012, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-verify">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-verify">
+ <info>
+ <date>2014-01-15</date>
+ </info>
<refentryinfo>
- <date>January 15, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-verify</command>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
- <arg><option>-I <replaceable class="parameter">input-format</replaceable></option></arg>
- <arg><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
- <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-x</option></arg>
- <arg><option>-z</option></arg>
- <arg choice="req">zonefile</arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-I <replaceable class="parameter">input-format</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-x</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-z</option></arg>
+ <arg choice="req" rep="norepeat">zonefile</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-verify</command>
verifies that a zone is fully signed for each algorithm found
in the DNSKEY RRset for the zone, and that the NSEC / NSEC3
chains are complete.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 4033</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007-2009, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.lwresd">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.lwresd">
+ <info>
+ <date>2009-01-20</date>
+ </info>
<refentryinfo>
- <date>January 20, 2009</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>lwresd</command>
- <arg><option>-c <replaceable class="parameter">config-file</replaceable></option></arg>
- <arg><option>-C <replaceable class="parameter">config-file</replaceable></option></arg>
- <arg><option>-d <replaceable class="parameter">debug-level</replaceable></option></arg>
- <arg><option>-f</option></arg>
- <arg><option>-g</option></arg>
- <arg><option>-i <replaceable class="parameter">pid-file</replaceable></option></arg>
- <arg><option>-m <replaceable class="parameter">flag</replaceable></option></arg>
- <arg><option>-n <replaceable class="parameter">#cpus</replaceable></option></arg>
- <arg><option>-P <replaceable class="parameter">port</replaceable></option></arg>
- <arg><option>-p <replaceable class="parameter">port</replaceable></option></arg>
- <arg><option>-s</option></arg>
- <arg><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-u <replaceable class="parameter">user</replaceable></option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-4</option></arg>
- <arg><option>-6</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">config-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-C <replaceable class="parameter">config-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">debug-level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-g</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i <replaceable class="parameter">pid-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">flag</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">#cpus</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P <replaceable class="parameter">port</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">port</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-u <replaceable class="parameter">user</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-4</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-6</option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>lwresd</command>
is the daemon providing name lookup
queries autonomously starting at the root name servers, using
a built-in list of root server hints.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<variablelist>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<refentrytitle>resolver</refentrytitle><manvolnum>5</manvolnum>
</citerefentry>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.named.conf">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.named.conf">
+ <info>
+ <date>2014-01-08</date>
+ </info>
<refentryinfo>
- <date>January 08, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>named.conf</command>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><filename>named.conf</filename> is the configuration file
for
<command>named</command>. Statements are enclosed
<para>
Unix style: # to end of line
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ACL</title>
- <literallayout>
+ <refsection><info><title>ACL</title></info>
+
+ <literallayout class="normal">
acl <replaceable>string</replaceable> { <replaceable>address_match_element</replaceable>; ... };
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>KEY</title>
- <literallayout>
+ <refsection><info><title>KEY</title></info>
+
+ <literallayout class="normal">
key <replaceable>domain_name</replaceable> {
algorithm <replaceable>string</replaceable>;
secret <replaceable>string</replaceable>;
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>MASTERS</title>
- <literallayout>
+ <refsection><info><title>MASTERS</title></info>
+
+ <literallayout class="normal">
masters <replaceable>string</replaceable> <optional> port <replaceable>integer</replaceable> </optional> {
( <replaceable>masters</replaceable> | <replaceable>ipv4_address</replaceable> <optional>port <replaceable>integer</replaceable></optional> |
<replaceable>ipv6_address</replaceable> <optional>port <replaceable>integer</replaceable></optional> ) <optional> key <replaceable>string</replaceable> </optional>; ...
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SERVER</title>
- <literallayout>
+ <refsection><info><title>SERVER</title></info>
+
+ <literallayout class="normal">
server ( <replaceable>ipv4_address<optional>/prefixlen</optional></replaceable> | <replaceable>ipv6_address<optional>/prefixlen</optional></replaceable> ) {
bogus <replaceable>boolean</replaceable>;
edns <replaceable>boolean</replaceable>;
support-ixfr <replaceable>boolean</replaceable>; // obsolete
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>TRUSTED-KEYS</title>
- <literallayout>
+ <refsection><info><title>TRUSTED-KEYS</title></info>
+
+ <literallayout class="normal">
trusted-keys {
<replaceable>domain_name</replaceable> <replaceable>flags</replaceable> <replaceable>protocol</replaceable> <replaceable>algorithm</replaceable> <replaceable>key</replaceable>; ...
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>MANAGED-KEYS</title>
- <literallayout>
+ <refsection><info><title>MANAGED-KEYS</title></info>
+
+ <literallayout class="normal">
managed-keys {
<replaceable>domain_name</replaceable> <constant>initial-key</constant> <replaceable>flags</replaceable> <replaceable>protocol</replaceable> <replaceable>algorithm</replaceable> <replaceable>key</replaceable>; ...
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>CONTROLS</title>
- <literallayout>
+ <refsection><info><title>CONTROLS</title></info>
+
+ <literallayout class="normal">
controls {
inet ( <replaceable>ipv4_address</replaceable> | <replaceable>ipv6_address</replaceable> | * )
<optional> port ( <replaceable>integer</replaceable> | * ) </optional>
unix <replaceable>unsupported</replaceable>; // not implemented
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>LOGGING</title>
- <literallayout>
+ <refsection><info><title>LOGGING</title></info>
+
+ <literallayout class="normal">
logging {
channel <replaceable>string</replaceable> {
file <replaceable>log_file</replaceable>;
category <replaceable>string</replaceable> { <replaceable>string</replaceable>; ... };
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>LWRES</title>
- <literallayout>
+ <refsection><info><title>LWRES</title></info>
+
+ <literallayout class="normal">
lwres {
listen-on <optional> port <replaceable>integer</replaceable> </optional> {
( <replaceable>ipv4_address</replaceable> | <replaceable>ipv6_address</replaceable> ) <optional> port <replaceable>integer</replaceable> </optional>; ...
lwres-clients <replaceable>integer</replaceable>;
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
- <literallayout>
+ <refsection><info><title>OPTIONS</title></info>
+
+ <literallayout class="normal">
options {
avoid-v4-udp-ports { <replaceable>port</replaceable>; ... };
avoid-v6-udp-ports { <replaceable>port</replaceable>; ... };
use-id-pool <replaceable>boolean</replaceable>; // obsolete
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>VIEW</title>
- <literallayout>
+ <refsection><info><title>VIEW</title></info>
+
+ <literallayout class="normal">
view <replaceable>string</replaceable> <replaceable>optional_class</replaceable> {
match-clients { <replaceable>address_match_element</replaceable>; ... };
match-destinations { <replaceable>address_match_element</replaceable>; ... };
max-ixfr-log-size <replaceable>size</replaceable>; // obsolete
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ZONE</title>
- <literallayout>
+ <refsection><info><title>ZONE</title></info>
+
+ <literallayout class="normal">
zone <replaceable>string</replaceable> <replaceable>optional_class</replaceable> {
type ( master | slave | stub | hint | redirect |
forward | delegation-only );
pubkey <replaceable>integer</replaceable> <replaceable>integer</replaceable> <replaceable>integer</replaceable> <replaceable>quoted_string</replaceable>; // obsolete
};
</literallayout>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<para><filename>/etc/named.conf</filename>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2009, 2011, 2013-2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001, 2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.named">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.named">
+ <info>
+ <date>2014-02-19</date>
+ </info>
<refentryinfo>
- <date>February 19, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>named</command>
- <arg><option>-4</option></arg>
- <arg><option>-6</option></arg>
- <arg><option>-c <replaceable class="parameter">config-file</replaceable></option></arg>
- <arg><option>-d <replaceable class="parameter">debug-level</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">string</replaceable></option></arg>
- <arg><option>-E <replaceable class="parameter">engine-name</replaceable></option></arg>
- <arg><option>-f</option></arg>
- <arg><option>-g</option></arg>
- <arg><option>-L <replaceable class="parameter">logfile</replaceable></option></arg>
- <arg><option>-M <replaceable class="parameter">option</replaceable></option></arg>
- <arg><option>-m <replaceable class="parameter">flag</replaceable></option></arg>
- <arg><option>-n <replaceable class="parameter">#cpus</replaceable></option></arg>
- <arg><option>-p <replaceable class="parameter">port</replaceable></option></arg>
- <arg><option>-s</option></arg>
- <arg><option>-S <replaceable class="parameter">#max-socks</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-U <replaceable class="parameter">#listeners</replaceable></option></arg>
- <arg><option>-u <replaceable class="parameter">user</replaceable></option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-X <replaceable class="parameter">lock-file</replaceable></option></arg>
- <arg><option>-x <replaceable class="parameter">cache-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-4</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-6</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">config-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">debug-level</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">string</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-E <replaceable class="parameter">engine-name</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-g</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">logfile</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-M <replaceable class="parameter">option</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">flag</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">#cpus</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">port</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-S <replaceable class="parameter">#max-socks</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-U <replaceable class="parameter">#listeners</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-u <replaceable class="parameter">user</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-X <replaceable class="parameter">lock-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-x <replaceable class="parameter">cache-file</replaceable></option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>named</command>
is a Domain Name System (DNS) server,
part of the BIND 9 distribution from ISC. For more
<filename>/etc/named.conf</filename>, read any initial
data, and listen for queries.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
<term>-D <replaceable class="parameter">string</replaceable></term>
<listitem>
<para>
- Specifies a string that is used to identify a instance of
- <command>named</command> in a process listing. The contents
- of <replaceable class="parameter">string</replaceable> are
- not examined.
+ Specifies a string that is used to identify a instance of
+ <command>named</command> in a process listing. The contents
+ of <replaceable class="parameter">string</replaceable> are
+ not examined.
</para>
</listitem>
</varlistentry>
<term>-M <replaceable class="parameter">option</replaceable></term>
<listitem>
<para>
- Sets the default memory context options. Currently
- the only supported option is
- <replaceable class="parameter">external</replaceable>,
- which causes the internal memory manager to be bypassed
- in favor of system-provided memory allocation functions.
+ Sets the default memory context options. Currently
+ the only supported option is
+ <replaceable class="parameter">external</replaceable>,
+ which causes the internal memory manager to be bypassed
+ in favor of system-provided memory allocation functions.
</para>
</listitem>
</varlistentry>
<term>-m <replaceable class="parameter">flag</replaceable></term>
<listitem>
<para>
- Turn on memory usage debugging flags. Possible flags are
- <replaceable class="parameter">usage</replaceable>,
- <replaceable class="parameter">trace</replaceable>,
- <replaceable class="parameter">record</replaceable>,
- <replaceable class="parameter">size</replaceable>, and
- <replaceable class="parameter">mctx</replaceable>.
- These correspond to the ISC_MEM_DEBUGXXXX flags described in
- <filename><isc/mem.h></filename>.
+ Turn on memory usage debugging flags. Possible flags are
+ <replaceable class="parameter">usage</replaceable>,
+ <replaceable class="parameter">trace</replaceable>,
+ <replaceable class="parameter">record</replaceable>,
+ <replaceable class="parameter">size</replaceable>, and
+ <replaceable class="parameter">mctx</replaceable>.
+ These correspond to the ISC_MEM_DEBUGXXXX flags described in
+ <filename><isc/mem.h></filename>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-S <replaceable class="parameter">#max-socks</replaceable></term>
<listitem>
- <para>
- Allow <command>named</command> to use up to
- <replaceable class="parameter">#max-socks</replaceable> sockets.
+ Allow <command>named</command> to use up to
+ <replaceable class="parameter">#max-socks</replaceable> sockets.
The default value is 4096 on systems built with default
configuration options, and 21000 on systems built with
"configure --with-tuning=large".
- </para>
+ </para>
<warning>
<para>
This option should be unnecessary for the vast majority
of users.
- The use of this option could even be harmful because the
+ The use of this option could even be harmful because the
specified value may exceed the limitation of the
underlying system API.
- It is therefore set only when the default configuration
+ It is therefore set only when the default configuration
causes exhaustion of file descriptors and the
operational environment is known to support the
specified number of sockets.
- Note also that the actual maximum number is normally a little
+ Note also that the actual maximum number is normally a little
fewer than the specified value because
- <command>named</command> reserves some file descriptors
- for its internal use.
+ <command>named</command> reserves some file descriptors
+ for its internal use.
</para>
</warning>
- </listitem>
+ </listitem>
</varlistentry>
<varlistentry>
<term>-t <replaceable class="parameter">directory</replaceable></term>
<listitem>
<para>Chroot
- to <replaceable class="parameter">directory</replaceable> after
+ to <replaceable class="parameter">directory</replaceable> after
processing the command line arguments, but before
reading the configuration file.
</para>
<term>-u <replaceable class="parameter">user</replaceable></term>
<listitem>
<para>Setuid
- to <replaceable class="parameter">user</replaceable> after completing
+ to <replaceable class="parameter">user</replaceable> after completing
privileged operations, such as creating sockets that
listen on privileged ports.
</para>
<note>
<para>
On Linux, <command>named</command> uses the kernel's
- capability mechanism to drop all root privileges
+ capability mechanism to drop all root privileges
except the ability to <function>bind(2)</function> to
a
privileged port and set process resource limits.
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SIGNALS</title>
+ <refsection><info><title>SIGNALS</title></info>
+
<para>
In routine operation, signals should not be used to control
the nameserver; <command>rndc</command> should be used
The result of sending any other signals to the server is undefined.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>CONFIGURATION</title>
+ <refsection><info><title>CONFIGURATION</title></info>
+
<para>
The <command>named</command> configuration file is too complex
to describe in detail here. A complete description is provided
<command>named</command> process.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<variablelist>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citetitle>RFC 1033</citetitle>,
<citetitle>RFC 1034</citetitle>,
<citetitle>RFC 1035</citetitle>,
<citerefentry>
<refentrytitle>named-checkconf</refentrytitle>
- <manvolnum>8</manvolnum>
+ <manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>named-checkzone</refentrytitle>
- <manvolnum>8</manvolnum>
+ <manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>rndc</refentrytitle>
- <manvolnum>8</manvolnum>
+ <manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>lwresd</refentrytitle>
- <manvolnum>8</manvolnum>
+ <manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
- <refentrytitle>named.conf</refentrytitle>
- <manvolnum>5</manvolnum>
+ <refentrytitle>named.conf</refentrytitle>
+ <manvolnum>5</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
-
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2012, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.nsupdate">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.nsupdate">
+ <info>
+ <date>2014-04-18</date>
+ </info>
<refentryinfo>
- <date>April 18, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
+
<refmeta>
<refentrytitle><application>nsupdate</application></refentrytitle>
<manvolnum>1</manvolnum>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>nsupdate</command>
- <arg><option>-d</option></arg>
- <arg><option>-D</option></arg>
- <arg><option>-L <replaceable class="parameter">level</replaceable></option></arg>
- <group>
- <arg><option>-g</option></arg>
- <arg><option>-o</option></arg>
- <arg><option>-l</option></arg>
- <arg><option>-y <replaceable class="parameter"><optional>hmac:</optional>keyname:secret</replaceable></option></arg>
- <arg><option>-k <replaceable class="parameter">keyfile</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">level</replaceable></option></arg>
+ <group choice="opt" rep="norepeat">
+ <arg choice="opt" rep="norepeat"><option>-g</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-o</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-l</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-y <replaceable class="parameter"><optional>hmac:</optional>keyname:secret</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">keyfile</replaceable></option></arg>
</group>
- <arg><option>-t <replaceable class="parameter">timeout</replaceable></option></arg>
- <arg><option>-u <replaceable class="parameter">udptimeout</replaceable></option></arg>
- <arg><option>-r <replaceable class="parameter">udpretries</replaceable></option></arg>
- <arg><option>-R <replaceable class="parameter">randomdev</replaceable></option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-T</option></arg>
- <arg><option>-P</option></arg>
- <arg><option>-V</option></arg>
- <arg>filename</arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">timeout</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-u <replaceable class="parameter">udptimeout</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">udpretries</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-R <replaceable class="parameter">randomdev</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-T</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat">filename</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>nsupdate</command>
is used to submit Dynamic DNS Update requests as defined in RFC 2136
to a name server.
non-standards-compliant variant of GSS-TSIG used by Windows
2000 can be switched on with the <option>-o</option> flag.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>INPUT FORMAT</title>
+ <refsection><info><title>INPUT FORMAT</title></info>
+
<para><command>nsupdate</command>
reads input from
<parameter>filename</parameter>
<varlistentry>
<term>
<command>server</command>
- <arg choice="req">servername</arg>
- <arg choice="opt">port</arg>
+ <arg choice="req" rep="norepeat">servername</arg>
+ <arg choice="opt" rep="norepeat">port</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command>local</command>
- <arg choice="req">address</arg>
- <arg choice="opt">port</arg>
+ <arg choice="req" rep="norepeat">address</arg>
+ <arg choice="opt" rep="norepeat">port</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command>zone</command>
- <arg choice="req">zonename</arg>
+ <arg choice="req" rep="norepeat">zonename</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command>class</command>
- <arg choice="req">classname</arg>
+ <arg choice="req" rep="norepeat">classname</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command>ttl</command>
- <arg choice="req">seconds</arg>
+ <arg choice="req" rep="norepeat">seconds</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command>key</command>
- <arg choice="opt">hmac:</arg><arg choice="req">keyname</arg>
- <arg choice="req">secret</arg>
+ <arg choice="opt" rep="norepeat">hmac:</arg><arg choice="req" rep="norepeat">keyname</arg>
+ <arg choice="req" rep="norepeat">secret</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command>realm</command>
- <arg choice="req"><optional>realm_name</optional></arg>
+ <arg choice="req" rep="norepeat"><optional>realm_name</optional></arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command>check-names</command>
- <arg choice="req"><optional>yes_or_no</optional></arg>
+ <arg choice="req" rep="norepeat"><optional>yes_or_no</optional></arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command><optional>prereq</optional> nxdomain</command>
- <arg choice="req">domain-name</arg>
+ <arg choice="req" rep="norepeat">domain-name</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command><optional>prereq</optional> yxdomain</command>
- <arg choice="req">domain-name</arg>
+ <arg choice="req" rep="norepeat">domain-name</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command><optional>prereq</optional> nxrrset</command>
- <arg choice="req">domain-name</arg>
- <arg choice="opt">class</arg>
- <arg choice="req">type</arg>
+ <arg choice="req" rep="norepeat">domain-name</arg>
+ <arg choice="opt" rep="norepeat">class</arg>
+ <arg choice="req" rep="norepeat">type</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command><optional>prereq</optional> yxrrset</command>
- <arg choice="req">domain-name</arg>
- <arg choice="opt">class</arg>
- <arg choice="req">type</arg>
+ <arg choice="req" rep="norepeat">domain-name</arg>
+ <arg choice="opt" rep="norepeat">class</arg>
+ <arg choice="req" rep="norepeat">type</arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command><optional>prereq</optional> yxrrset</command>
- <arg choice="req">domain-name</arg>
- <arg choice="opt">class</arg>
- <arg choice="req">type</arg>
+ <arg choice="req" rep="norepeat">domain-name</arg>
+ <arg choice="opt" rep="norepeat">class</arg>
+ <arg choice="req" rep="norepeat">type</arg>
<arg choice="req" rep="repeat">data</arg>
</term>
<listitem>
<varlistentry>
<term>
<command><optional>update</optional> del<optional>ete</optional></command>
- <arg choice="req">domain-name</arg>
- <arg choice="opt">ttl</arg>
- <arg choice="opt">class</arg>
- <arg choice="opt">type <arg choice="opt" rep="repeat">data</arg></arg>
+ <arg choice="req" rep="norepeat">domain-name</arg>
+ <arg choice="opt" rep="norepeat">ttl</arg>
+ <arg choice="opt" rep="norepeat">class</arg>
+ <arg choice="opt"
rep="norepeat">type <arg choice="opt" rep="repeat">data</arg></arg>
</term>
<listitem>
<para>
<varlistentry>
<term>
<command><optional>update</optional> add</command>
- <arg choice="req">domain-name</arg>
- <arg choice="req">ttl</arg>
- <arg choice="opt">class</arg>
- <arg choice="req">type</arg>
+ <arg choice="req" rep="norepeat">domain-name</arg>
+ <arg choice="req" rep="norepeat">ttl</arg>
+ <arg choice="opt" rep="norepeat">class</arg>
+ <arg choice="req" rep="norepeat">type</arg>
<arg choice="req" rep="repeat">data</arg>
</term>
<listitem>
Lines beginning with a semicolon are comments and are ignored.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>EXAMPLES</title>
+ <refsection><info><title>EXAMPLES</title></info>
+
<para>
The examples below show how
<command>nsupdate</command>
(The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have
RRSIG, DNSKEY and NSEC records.)
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>FILES</title>
+ <refsection><info><title>FILES</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citetitle>RFC 2136</citetitle>,
<citetitle>RFC 3007</citetitle>,
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>BUGS</title>
+ <refsection><info><title>BUGS</title></info>
+
<para>
The TSIG key is redundantly stored in two separate files.
This is a consequence of nsupdate using the DST library
for its cryptographic operations, and may change in future
releases.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.pkcs11-destroy">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.pkcs11-destroy">
+ <info>
+ <date>2014-01-15</date>
+ </info>
<refentryinfo>
- <date>January 15, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>pkcs11-destroy</command>
- <arg><option>-m <replaceable class="parameter">module</replaceable></option></arg>
- <arg><option>-s <replaceable class="parameter">slot</replaceable></option></arg>
- <group choice="req">
- <arg choice="plain">-i <replaceable class="parameter">ID</replaceable></arg>
- <arg choice="plain">-l <replaceable class="parameter">label</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">module</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">slot</replaceable></option></arg>
+ <group choice="req" rep="norepeat">
+ <arg choice="plain" rep="norepeat">-i <replaceable class="parameter">ID</replaceable></arg>
+ <arg choice="plain" rep="norepeat">-l <replaceable class="parameter">label</replaceable></arg>
</group>
- <arg><option>-p <replaceable class="parameter">PIN</replaceable></option></arg>
- <arg><option>-w <replaceable class="parameter">seconds</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">PIN</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-w <replaceable class="parameter">seconds</replaceable></option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>pkcs11-destroy</command> destroys keys stored in a
PKCS#11 device, identified by their <option>ID</option> or
there is a five second delay to allow the user to interrupt the
process before the destruction takes place.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ARGUMENTS</title>
+ <refsection><info><title>ARGUMENTS</title></info>
+
<variablelist>
<varlistentry>
<term>-m <replaceable class="parameter">module</replaceable></term>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>pkcs11-keygen</refentrytitle><manvolnum>8</manvolnum>
<refentrytitle>pkcs11-tokens</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.pkcs11-keygen">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.pkcs11-keygen">
+ <info>
+ <date>2014-01-15</date>
+ </info>
<refentryinfo>
- <date>January 15, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>pkcs11-keygen</command>
- <arg choice="req">-a <replaceable class="parameter">algorithm</replaceable></arg>
- <arg><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
- <arg><option>-e</option></arg>
- <arg><option>-i <replaceable class="parameter">id</replaceable></option></arg>
- <arg><option>-m <replaceable class="parameter">module</replaceable></option></arg>
- <arg><option>-P</option></arg>
- <arg><option>-p <replaceable class="parameter">PIN</replaceable></option></arg>
- <arg><option>-q</option></arg>
- <arg><option>-S</option></arg>
- <arg><option>-s <replaceable class="parameter">slot</replaceable></option></arg>
- <arg choice="req">label</arg>
+ <arg choice="req" rep="norepeat">-a <replaceable class="parameter">algorithm</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-e</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i <replaceable class="parameter">id</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">module</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">PIN</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-S</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">slot</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">label</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>pkcs11-keygen</command> causes a PKCS#11 device to generate
a new key pair with the given <option>label</option> (which must be
unique) and with <option>keysize</option> bits of prime.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ARGUMENTS</title>
+ <refsection><info><title>ARGUMENTS</title></info>
+
<variablelist>
<varlistentry>
<term>-a <replaceable class="parameter">algorithm</replaceable></term>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>8</manvolnum>
<refentrytitle>dnssec-keyfromlabel</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.pkcs11-list">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.pkcs11-list">
+ <info>
+ <date>2009-10-05</date>
+ </info>
<refentryinfo>
- <date>October 05, 2009</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>pkcs11-list</command>
- <arg><option>-P</option></arg>
- <arg><option>-m <replaceable class="parameter">module</replaceable></option></arg>
- <arg><option>-s <replaceable class="parameter">slot</replaceable></option></arg>
- <arg choice="opt">-i <replaceable class="parameter">ID</replaceable></arg>
- <arg choice="opt">-l <replaceable class="parameter">label</replaceable></arg>
- <arg><option>-p <replaceable class="parameter">PIN</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">module</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">slot</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat">-i <replaceable class="parameter">ID</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-l <replaceable class="parameter">label</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">PIN</replaceable></option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>pkcs11-list</command>
lists the PKCS#11 objects with <option>ID</option> or
<option>label</option> or by default all objects.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ARGUMENTS</title>
+ <refsection><info><title>ARGUMENTS</title></info>
+
<variablelist>
<varlistentry>
<term>-P</term>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>8</manvolnum>
<refentrytitle>pkcs11-tokens</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.pkcs11-tokens">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.pkcs11-tokens">
+ <info>
+ <date>2014-01-15</date>
+ </info>
<refentryinfo>
- <date>January 15, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>pkcs11-tokens</command>
- <arg><option>-m <replaceable class="parameter">module</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">module</replaceable></option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>pkcs11-tokens</command>
lists the PKCS#11 available tokens with defaults from the slot/token
scan performed at application initialization.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ARGUMENTS</title>
+ <refsection><info><title>ARGUMENTS</title></info>
+
<variablelist>
<varlistentry>
<term>-m <replaceable class="parameter">module</replaceable></term>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>8</manvolnum>
<refentrytitle>pkcs11-list</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2012-2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-checkds">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-checkds">
+ <info>
+ <date>2013-01-01</date>
+ </info>
<refentryinfo>
- <date>January 01, 2013</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-checkds</command>
- <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">file</replaceable></option></arg>
- <arg><option>-d <replaceable class="parameter">dig path</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">dsfromkey path</replaceable></option></arg>
- <arg choice="req">zone</arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">dig path</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">dsfromkey path</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">zone</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-dsfromkey</command>
- <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">file</replaceable></option></arg>
- <arg><option>-d <replaceable class="parameter">dig path</replaceable></option></arg>
- <arg><option>-D <replaceable class="parameter">dsfromkey path</replaceable></option></arg>
- <arg choice="req">zone</arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">dig path</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">dsfromkey path</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">zone</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-checkds</command>
verifies the correctness of Delegation Signer (DS) or DNSSEC
Lookaside Validation (DLV) resource records for keys in a specified
zone.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dnssec-dsfromkey</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnssec-coverage">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-coverage">
+ <info>
+ <date>2014-01-11</date>
+ </info>
<refentryinfo>
- <date>January 11, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnssec-coverage</command>
- <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
- <arg><option>-l <replaceable class="parameter">length</replaceable></option></arg>
- <arg><option>-f <replaceable class="parameter">file</replaceable></option></arg>
- <arg><option>-d <replaceable class="parameter">DNSKEY TTL</replaceable></option></arg>
- <arg><option>-m <replaceable class="parameter">max TTL</replaceable></option></arg>
- <arg><option>-r <replaceable class="parameter">interval</replaceable></option></arg>
- <arg><option>-c <replaceable class="parameter">compilezone path</replaceable></option></arg>
- <arg><option>-k</option></arg>
- <arg><option>-z</option></arg>
- <arg choice="opt">zone</arg>
+ <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">length</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">DNSKEY TTL</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">max TTL</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">interval</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">compilezone path</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-z</option></arg>
+ <arg choice="opt" rep="norepeat">zone</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>dnssec-coverage</command>
verifies that the DNSSEC keys for a given zone or a set of zones
have timing metadata set properly to ensure no future lapses in DNSSEC
accurate if all the zones that have keys in a given repository
share the same TTL parameters.)
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>dnssec-checkds</refentrytitle><manvolnum>8</manvolnum>
<refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.rndc.conf">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.rndc.conf">
+ <info>
+ <date>2013-03-14</date>
+ </info>
<refentryinfo>
- <date>March 14, 2013</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>rndc.conf</command>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><filename>rndc.conf</filename> is the configuration file
for <command>rndc</command>, the BIND 9 name server control
utility. This file has a similar structure and syntax to
ship with BIND 9 but is available on many systems. See the
EXAMPLE section for sample command lines for each.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>EXAMPLE</title>
+ <refsection><info><title>EXAMPLE</title></info>
+
<para><programlisting>
options {
</para>
<para><userinput>echo "known plaintext for a secret" | mmencode</userinput>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>NAME SERVER CONFIGURATION</title>
+ <refsection><info><title>NAME SERVER CONFIGURATION</title></info>
+
<para>
The name server must be configured to accept rndc connections and
to recognize the key specified in the <filename>rndc.conf</filename>
See the sections on the <option>controls</option> statement in the
BIND 9 Administrator Reference Manual for details.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>rndc</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2013-2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.rndc">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.rndc">
+ <info>
+ <date>2014-08-15</date>
+ </info>
<refentryinfo>
- <date>August 15, 2014</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>rndc</command>
- <arg><option>-b <replaceable class="parameter">source-address</replaceable></option></arg>
- <arg><option>-c <replaceable class="parameter">config-file</replaceable></option></arg>
- <arg><option>-k <replaceable class="parameter">key-file</replaceable></option></arg>
- <arg><option>-s <replaceable class="parameter">server</replaceable></option></arg>
- <arg><option>-p <replaceable class="parameter">port</replaceable></option></arg>
- <arg><option>-q</option></arg>
- <arg><option>-r</option></arg>
- <arg><option>-V</option></arg>
- <arg><option>-y <replaceable class="parameter">key_id</replaceable></option></arg>
- <arg choice="req">command</arg>
+ <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">source-address</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">config-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-k <replaceable class="parameter">key-file</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-s <replaceable class="parameter">server</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">port</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-q</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-r</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-V</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-y <replaceable class="parameter">key_id</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">command</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>rndc</command>
controls the operation of a name
server. It supersedes the <command>ndc</command> utility
determine how to contact the name server and decide what
algorithm and key it should use.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>COMMANDS</title>
+ <refsection><info><title>COMMANDS</title></info>
+
<para>
A list of commands supported by <command>rndc</command> can
be seen by running <command>rndc</command> without arguments.
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>LIMITATIONS</title>
+ <refsection><info><title>LIMITATIONS</title></info>
+
<para>
There is currently no way to provide the shared secret for a
<option>key_id</option> without using the configuration file.
<para>
Several error messages could be clearer.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>rndc.conf</refentrytitle><manvolnum>5</manvolnum>
</citerefentry>,
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.arpaname">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.arpaname">
+ <info>
+ <date>2009-03-03</date>
+ </info>
<refentryinfo>
- <date>March 03, 2009</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
-
<refmeta>
<refentrytitle><application>arpaname</application></refentrytitle>
<manvolnum>1</manvolnum>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>arpaname</command>
<arg choice="req" rep="repeat"><replaceable class="parameter">ipaddress </replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>arpaname</command> translates IP addresses (IPv4 and
IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
-
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.dnstap-read">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnstap-read">
+ <info>
+ <date>2015-09-13</date>
+ </info>
<refentryinfo>
- <date>September 13, 2015</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>dnstap-read</command>
- <arg><option>-m</option></arg>
- <arg><option>-p</option></arg>
- <arg><option>-y</option></arg>
- <arg choice="req"><replaceable class="parameter">file</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><option>-m</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-y</option></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">file</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>dnstap-read</command>
reads <command>dnstap</command> data from a specified file
format, but if the <option>-y</option> option is specified,
then a longer and more detailed YAML format is used instead.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
<varlistentry>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009-2011, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.genrandom">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.genrandom">
+ <info>
+ <date>2011-08-08</date>
+ </info>
<refentryinfo>
- <date>August 08, 2011</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>genrandom</command>
- <arg><option>-n <replaceable class="parameter">number</replaceable></option></arg>
- <arg choice="req"><replaceable class="parameter">size</replaceable></arg>
- <arg choice="req"><replaceable class="parameter">filename</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">number</replaceable></option></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">size</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">filename</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>genrandom</command>
generates a file or a set of files containing a specified quantity
of pseudo-random data, which can be used as a source of entropy for
other commands on systems with no random device.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ARGUMENTS</title>
+ <refsection><info><title>ARGUMENTS</title></info>
+
<variablelist>
<varlistentry>
<term>-n <replaceable class="parameter">number</replaceable></term>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>rand</refentrytitle><manvolnum>3</manvolnum>
<refentrytitle>arc4random</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!-- Converted by db4-upgrade version 1.0 -->
<!--
- - Copyright (C) 2010, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
+ - Copyright (C) 2010, 2012-2015 Internet Systems Consortium, Inc. ("ISC")
-
- Permission to use, copy, modify, and/or distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.isc-hmac-fixup">
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.isc-hmac-fixup">
+ <info>
+ <date>2013-04-28</date>
+ </info>
<refentryinfo>
- <date>April 28, 2013</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>isc-hmac-fixup</command>
- <arg choice="req"><replaceable class="parameter">algorithm</replaceable></arg>
- <arg choice="req"><replaceable class="parameter">secret</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">algorithm</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">secret</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
Versions of BIND 9 up to and including BIND 9.6 had a bug causing
HMAC-SHA* TSIG keys which were longer than the digest length of the
secret. (If the secret did not require conversion, then it will be
printed without modification.)
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SECURITY CONSIDERATIONS</title>
+ <refsection><info><title>SECURITY CONSIDERATIONS</title></info>
+
<para>
Secrets that have been converted by <command>isc-hmac-fixup</command>
are shortened, but as this is how the HMAC protocol works in
extra length would not significantly increase the function
strength."
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 2104</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- - Copyright (C) 2015 Internet Systems Consortium, Inc. ("ISC")
+ - Copyright (C) 2010, 2012-2015 Internet Systems Consortium, Inc. ("ISC")
-
- Permission to use, copy, modify, and/or distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.mdig">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.mdig">
+ <info>
+ <date>2015-01-05</date>
+ </info>
<refentryinfo>
- <date>January 5, 2015</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
<refentrytitle><application>mdig</application></refentrytitle>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>mdig</command>
- <arg choice="req">@server</arg>
- <arg><option>-f <replaceable class="parameter">filename</replaceable></option></arg>
- <arg><option>-h</option></arg>
- <arg><option>-v</option></arg>
- <arg><option>-4</option></arg>
- <arg><option>-6</option></arg>
- <arg><option>-b <replaceable class="parameter">address</replaceable></option></arg>
- <arg><option>-p <replaceable class="parameter">port#</replaceable></option></arg>
- <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
- <arg><option>-t <replaceable class="parameter">type</replaceable></option></arg>
- <arg><option>-i</option></arg>
- <arg><option>-x <replaceable class="parameter">addr</replaceable></option></arg>
+ <arg choice="req" rep="norepeat">@server</arg>
+ <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">filename</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-v</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-4</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-6</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">address</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">port#</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">type</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-i</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-x <replaceable class="parameter">addr</replaceable></option></arg>
<arg choice="opt" rep="repeat">plusopt</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>mdig</command>
- <arg choice="req">-h</arg>
+ <arg choice="req" rep="norepeat">-h</arg>
</cmdsynopsis>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>mdig</command>
- <arg>@server</arg>
+ <arg choice="opt" rep="norepeat">@server</arg>
<arg choice="req" rep="repeat">global-opt</arg>
<arg choice="req" rep="repeat">
<arg choice="req" rep="repeat">local-opt</arg>
- <arg choice="req">query</arg>
+ <arg choice="req" rep="norepeat">query</arg>
</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>mdig</command>
is a multiple/pipelined query version of <command>dig</command>:
instead of waiting for a response after sending each query,
</para>
<para>
- The <arg choice="req">@server</arg> option is a mandatory global
+ The <arg choice="req" rep="norepeat">@server</arg> option is a mandatory global
option. It is the name or IP address of the name server to query.
(Unlike <command>dig</command>, this value is not retrieved from
<filename>/etc/resolv.conf</filename>.) It can be an IPv4 address
values to options like the timeout interval. They have the
form <option>+keyword=value</option>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ANYWHERE OPTIONS</title>
+ <refsection><info><title>ANYWHERE OPTIONS</title></info>
+
<para>
The <option>-f</option> option makes <command>mdig</command>
The <option>-v</option> causes <command>mdig</command> to
print the version number and exit.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>GLOBAL OPTIONS</title>
+ <refsection><info><title>GLOBAL OPTIONS</title></info>
+
<para>
The <option>-4</option> option forces <command>mdig</command> to
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>LOCAL OPTIONS</title>
+ <refsection><info><title>LOCAL OPTIONS</title></info>
+
<para>
The <option>-c</option> option sets the query class to
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>dig</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,
<citetitle>RFC1035</citetitle>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.named-journalprint">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.named-journalprint">
+ <info>
+ <date>2009-12-04</date>
+ </info>
<refentryinfo>
- <date>December 04, 2009</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>named-journalprint</command>
- <arg choice="req"><replaceable class="parameter">journal</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">journal</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>named-journalprint</command>
prints the contents of a zone journal file in a human-readable
deleted, and continues with the resource record in master-file
format.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.named-rrchecker">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.named-rrchecker">
+ <info>
+ <date>2013-11-12</date>
+ </info>
<refentryinfo>
- <date>November 12, 2013</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
<refentrytitle><application>named-rrchecker</application></refentrytitle>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>named-rrchecker</command>
- <arg><option>-h</option></arg>
- <arg><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
- <arg><option>-p</option></arg>
- <arg><option>-u</option></arg>
- <arg><option>-C</option></arg>
- <arg><option>-T</option></arg>
- <arg><option>-P</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-h</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
+ <arg choice="opt" rep="norepeat"><option>-p</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-u</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-C</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-T</option></arg>
+ <arg choice="opt" rep="norepeat"><option>-P</option></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>named-rrchecker</command>
read a individual DNS resource record from standard input and checks if it
is syntactically correct.
print out the known class, standard type and private type mnemonics
respectively.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citetitle>RFC 1034</citetitle>,
<citetitle>RFC 1035</citetitle>,
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.nsec3hash">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.nsec3hash">
+ <info>
+ <date>2009-03-02</date>
+ </info>
<refentryinfo>
- <date>March 02, 2009</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</docinfo>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>nsec3hash</command>
- <arg choice="req"><replaceable class="parameter">salt</replaceable></arg>
- <arg choice="req"><replaceable class="parameter">algorithm</replaceable></arg>
- <arg choice="req"><replaceable class="parameter">iterations</replaceable></arg>
- <arg choice="req"><replaceable class="parameter">domain</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">salt</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">algorithm</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">iterations</replaceable></arg>
+ <arg choice="req" rep="norepeat"><replaceable class="parameter">domain</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
<command>nsec3hash</command> generates an NSEC3 hash based on
a set of NSEC3 parameters. This can be used to check the validity
of NSEC3 records in a signed zone.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>ARGUMENTS</title>
+ <refsection><info><title>ARGUMENTS</title></info>
+
<variablelist>
<varlistentry>
<term>salt</term>
</listitem>
</varlistentry>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para>
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 5155</citetitle>.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
SO
BIND9_CONFIGARGS
BIND9_SRCID
+BIND9_VERSIONSHORT
BIND9_VERSIONSTRING
BIND9_MAJOR
BIND9_VERSION
ATFBIN
ATFBUILD
IDNLIBS
-XSLT_DB2LATEX_ADMONITIONS
-XSLT_DB2LATEX_STYLE
+XSLT_DBLATEX_FASTBOOK
+XSLT_DBLATEX_STYLE
XSLT_DOCBOOK_MAKETOC_XHTML
XSLT_DOCBOOK_MAKETOC_HTML
XSLT_DOCBOOK_CHUNKTOC_XHTML
XMLLINT
XSLTPROC
W3M
+DBLATEX
PDFLATEX
LATEX
DNSTAPHTML
+for ac_prog in dblatex
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_path_DBLATEX+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ case $DBLATEX in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_DBLATEX="$DBLATEX" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_DBLATEX="$as_dir/$ac_word$ac_exec_ext"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+ ;;
+esac
+fi
+DBLATEX=$ac_cv_path_DBLATEX
+if test -n "$DBLATEX"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $DBLATEX" >&5
+$as_echo "$DBLATEX" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$DBLATEX" && break
+done
+test -n "$DBLATEX" || DBLATEX="dblatex"
+
+
+
#
# Look for w3m
#
#
-# Same dance for db2latex
-#
-
-db2latex_xsl_trees="/usr/local/share/db2latex/xsl /usr/pkg/share/xsl/db2latex"
-
-#
-# Look for stylesheets we need.
+# Same dance for dblatex
#
+dblatex_xsl_trees="/usr/local/share/xml/docbook/stylesheet/dblatex /usr/pkg/share/xml/docbook/stylesheet/dblatex /usr/share/xml/docbook/stylesheet/dblatex"
-
-XSLT_DB2LATEX_STYLE=""
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for docbook.xsl" >&5
-$as_echo_n "checking for docbook.xsl... " >&6; }
-for d in $db2latex_xsl_trees
+XSLT_DBLATEX_STYLE=""
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for xsl/docbook.xsl" >&5
+$as_echo_n "checking for xsl/docbook.xsl... " >&6; }
+for d in $dblatex_xsl_trees
do
- f=$d/docbook.xsl
+ f=$d/xsl/docbook.xsl
if test -f $f
then
- XSLT_DB2LATEX_STYLE=$f
+ XSLT_DBLATEX_STYLE=$f
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $f" >&5
$as_echo "$f" >&6; }
break
fi
done
-if test "X$XSLT_DB2LATEX_STYLE" = "X"
+if test "X$XSLT_DBLATEX_STYLE" = "X"
then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: \"not found\"" >&5
$as_echo "\"not found\"" >&6; };
- XSLT_DB2LATEX_STYLE=docbook.xsl
+ XSLT_DBLATEX_STYLE=xsl/docbook.xsl
fi
-#
-# Look for "admonition" image directory. Can't use NOM_PATH_FILE()
-# because it's a directory, so just do the same things, inline.
-#
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for db2latex xsl figures" >&5
-$as_echo_n "checking for db2latex xsl figures... " >&6; }
-for d in $db2latex_xsl_trees
+XSLT_DBLATEX_FASTBOOK=""
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for xsl/latex_book_fast.xsl" >&5
+$as_echo_n "checking for xsl/latex_book_fast.xsl... " >&6; }
+for d in $dblatex_xsl_trees
do
- if test -d $d/figures
+ f=$d/xsl/latex_book_fast.xsl
+ if test -f $f
then
- XSLT_DB2LATEX_ADMONITIONS=$d/figures
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $d/figures" >&5
-$as_echo "$d/figures" >&6; }
+ XSLT_DBLATEX_FASTBOOK=$f
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $f" >&5
+$as_echo "$f" >&6; }
break
fi
done
-if test "X$XSLT_DB2LATEX_ADMONITIONS" = "X"
+if test "X$XSLT_DBLATEX_FASTBOOK" = "X"
then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: not found" >&5
-$as_echo "not found" >&6; }
- XSLT_DB2LATEX_ADMONITIONS=db2latex/xsl/figures
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: \"not found\"" >&5
+$as_echo "\"not found\"" >&6; };
+ XSLT_DBLATEX_FASTBOOK=xsl/latex_book_fast.xsl
fi
+
#
# IDN support
#
BIND9_VERSIONSTRING="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}${DESCRIPTION:+ }${DESCRIPTION}"
+BIND9_VERSIONSHORT="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}"
+
BIND9_SRCID="SRCID=unset"
if test -f "${srcdir}/srcid"; then
# elsewhere if there's a good reason for doing so.
#
-ac_config_files="$ac_config_files make/Makefile make/mkdep Makefile bin/Makefile bin/check/Makefile bin/confgen/Makefile bin/confgen/unix/Makefile bin/delv/Makefile bin/dig/Makefile bin/dnssec/Makefile bin/named/Makefile bin/named/unix/Makefile bin/nsupdate/Makefile bin/pkcs11/Makefile bin/python/Makefile bin/python/dnssec-checkds.py bin/python/dnssec-coverage.py bin/rndc/Makefile bin/tests/Makefile bin/tests/atomic/Makefile bin/tests/db/Makefile bin/tests/dst/Makefile bin/tests/dst/Kdh.+002+18602.key bin/tests/dst/Kdh.+002+18602.private bin/tests/dst/Kdh.+002+48957.key bin/tests/dst/Kdh.+002+48957.private bin/tests/dst/Ktest.+001+00002.key bin/tests/dst/Ktest.+001+54622.key bin/tests/dst/Ktest.+001+54622.private bin/tests/dst/Ktest.+003+23616.key bin/tests/dst/Ktest.+003+23616.private bin/tests/dst/Ktest.+003+49667.key bin/tests/dst/dst_2_data bin/tests/dst/t2_data_1 bin/tests/dst/t2_data_2 bin/tests/dst/t2_dsasig bin/tests/dst/t2_rsasig bin/tests/hashes/Makefile bin/tests/headerdep_test.sh bin/tests/master/Makefile bin/tests/mem/Makefile bin/tests/names/Makefile bin/tests/net/Makefile bin/tests/pkcs11/Makefile bin/tests/pkcs11/benchmarks/Makefile bin/tests/rbt/Makefile bin/tests/resolver/Makefile bin/tests/sockaddr/Makefile bin/tests/system/Makefile bin/tests/system/builtin/Makefile bin/tests/system/conf.sh bin/tests/system/dlz/prereq.sh bin/tests/system/dlzexternal/Makefile bin/tests/system/dlzexternal/ns1/named.conf bin/tests/system/dyndb/Makefile bin/tests/system/dyndb/driver/Makefile bin/tests/system/filter-aaaa/Makefile bin/tests/system/geoip/Makefile bin/tests/system/inline/checkdsa.sh bin/tests/system/lwresd/Makefile bin/tests/system/pipelined/Makefile bin/tests/system/resolver/Makefile bin/tests/system/rndc/Makefile bin/tests/system/rpz/Makefile bin/tests/system/rsabigexponent/Makefile bin/tests/system/statistics/Makefile bin/tests/system/tkey/Makefile bin/tests/system/tsiggss/Makefile bin/tests/tasks/Makefile bin/tests/timers/Makefile bin/tests/virtual-time/Makefile bin/tests/virtual-time/conf.sh bin/tools/Makefile contrib/scripts/check-secure-delegation.pl contrib/scripts/zone-edit.sh doc/Makefile doc/arm/Makefile doc/doxygen/Doxyfile doc/doxygen/Makefile doc/doxygen/doxygen-input-filter doc/misc/Makefile doc/xsl/Makefile doc/xsl/isc-docbook-chunk.xsl doc/xsl/isc-docbook-html.xsl doc/xsl/isc-docbook-latex.xsl doc/xsl/isc-manpage.xsl doc/xsl/isc-notes-html.xsl doc/xsl/isc-notes-latex.xsl isc-config.sh lib/Makefile lib/bind9/Makefile lib/bind9/include/Makefile lib/bind9/include/bind9/Makefile lib/dns/Makefile lib/dns/include/Makefile lib/dns/include/dns/Makefile lib/dns/include/dst/Makefile lib/dns/tests/Makefile lib/irs/Makefile lib/irs/include/Makefile lib/irs/include/irs/Makefile lib/irs/include/irs/netdb.h lib/irs/include/irs/platform.h lib/isc/$arch/Makefile lib/isc/$arch/include/Makefile lib/isc/$arch/include/isc/Makefile lib/isc/$thread_dir/Makefile lib/isc/$thread_dir/include/Makefile lib/isc/$thread_dir/include/isc/Makefile lib/isc/Makefile lib/isc/include/Makefile lib/isc/include/isc/Makefile lib/isc/include/isc/platform.h lib/isc/include/pk11/Makefile lib/isc/include/pkcs11/Makefile lib/isc/tests/Makefile lib/isc/nls/Makefile lib/isc/unix/Makefile lib/isc/unix/include/Makefile lib/isc/unix/include/isc/Makefile lib/isc/unix/include/pkcs11/Makefile lib/isccc/Makefile lib/isccc/include/Makefile lib/isccc/include/isccc/Makefile lib/isccfg/Makefile lib/isccfg/include/Makefile lib/isccfg/include/isccfg/Makefile lib/lwres/Makefile lib/lwres/include/Makefile lib/lwres/include/lwres/Makefile lib/lwres/include/lwres/netdb.h lib/lwres/include/lwres/platform.h lib/lwres/man/Makefile lib/lwres/tests/Makefile lib/lwres/unix/Makefile lib/lwres/unix/include/Makefile lib/lwres/unix/include/lwres/Makefile lib/tests/Makefile lib/tests/include/Makefile lib/tests/include/tests/Makefile lib/samples/Makefile lib/samples/Makefile-postinstall unit/Makefile unit/unittest.sh"
+ac_config_files="$ac_config_files make/Makefile make/mkdep Makefile bin/Makefile bin/check/Makefile bin/confgen/Makefile bin/confgen/unix/Makefile bin/delv/Makefile bin/dig/Makefile bin/dnssec/Makefile bin/named/Makefile bin/named/unix/Makefile bin/nsupdate/Makefile bin/pkcs11/Makefile bin/python/Makefile bin/python/dnssec-checkds.py bin/python/dnssec-coverage.py bin/rndc/Makefile bin/tests/Makefile bin/tests/atomic/Makefile bin/tests/db/Makefile bin/tests/dst/Makefile bin/tests/dst/Kdh.+002+18602.key bin/tests/dst/Kdh.+002+18602.private bin/tests/dst/Kdh.+002+48957.key bin/tests/dst/Kdh.+002+48957.private bin/tests/dst/Ktest.+001+00002.key bin/tests/dst/Ktest.+001+54622.key bin/tests/dst/Ktest.+001+54622.private bin/tests/dst/Ktest.+003+23616.key bin/tests/dst/Ktest.+003+23616.private bin/tests/dst/Ktest.+003+49667.key bin/tests/dst/dst_2_data bin/tests/dst/t2_data_1 bin/tests/dst/t2_data_2 bin/tests/dst/t2_dsasig bin/tests/dst/t2_rsasig bin/tests/hashes/Makefile bin/tests/headerdep_test.sh bin/tests/master/Makefile bin/tests/mem/Makefile bin/tests/names/Makefile bin/tests/net/Makefile bin/tests/pkcs11/Makefile bin/tests/pkcs11/benchmarks/Makefile bin/tests/rbt/Makefile bin/tests/resolver/Makefile bin/tests/sockaddr/Makefile bin/tests/system/Makefile bin/tests/system/builtin/Makefile bin/tests/system/conf.sh bin/tests/system/dlz/prereq.sh bin/tests/system/dlzexternal/Makefile bin/tests/system/dlzexternal/ns1/named.conf bin/tests/system/dyndb/Makefile bin/tests/system/dyndb/driver/Makefile bin/tests/system/filter-aaaa/Makefile bin/tests/system/geoip/Makefile bin/tests/system/inline/checkdsa.sh bin/tests/system/lwresd/Makefile bin/tests/system/pipelined/Makefile bin/tests/system/resolver/Makefile bin/tests/system/rndc/Makefile bin/tests/system/rpz/Makefile bin/tests/system/rsabigexponent/Makefile bin/tests/system/statistics/Makefile bin/tests/system/tkey/Makefile bin/tests/system/tsiggss/Makefile bin/tests/tasks/Makefile bin/tests/timers/Makefile bin/tests/virtual-time/Makefile bin/tests/virtual-time/conf.sh bin/tools/Makefile contrib/scripts/check-secure-delegation.pl contrib/scripts/zone-edit.sh doc/Makefile doc/arm/Makefile doc/doxygen/Doxyfile doc/doxygen/Makefile doc/doxygen/doxygen-input-filter doc/misc/Makefile doc/tex/Makefile doc/tex/armstyle.sty doc/xsl/Makefile doc/xsl/isc-docbook-chunk.xsl doc/xsl/isc-docbook-html.xsl doc/xsl/isc-manpage.xsl doc/xsl/isc-notes-html.xsl isc-config.sh lib/Makefile lib/bind9/Makefile lib/bind9/include/Makefile lib/bind9/include/bind9/Makefile lib/dns/Makefile lib/dns/include/Makefile lib/dns/include/dns/Makefile lib/dns/include/dst/Makefile lib/dns/tests/Makefile lib/irs/Makefile lib/irs/include/Makefile lib/irs/include/irs/Makefile lib/irs/include/irs/netdb.h lib/irs/include/irs/platform.h lib/isc/$arch/Makefile lib/isc/$arch/include/Makefile lib/isc/$arch/include/isc/Makefile lib/isc/$thread_dir/Makefile lib/isc/$thread_dir/include/Makefile lib/isc/$thread_dir/include/isc/Makefile lib/isc/Makefile lib/isc/include/Makefile lib/isc/include/isc/Makefile lib/isc/include/isc/platform.h lib/isc/include/pk11/Makefile lib/isc/include/pkcs11/Makefile lib/isc/tests/Makefile lib/isc/nls/Makefile lib/isc/unix/Makefile lib/isc/unix/include/Makefile lib/isc/unix/include/isc/Makefile lib/isc/unix/include/pkcs11/Makefile lib/isccc/Makefile lib/isccc/include/Makefile lib/isccc/include/isccc/Makefile lib/isccfg/Makefile lib/isccfg/include/Makefile lib/isccfg/include/isccfg/Makefile lib/lwres/Makefile lib/lwres/include/Makefile lib/lwres/include/lwres/Makefile lib/lwres/include/lwres/netdb.h lib/lwres/include/lwres/platform.h lib/lwres/man/Makefile lib/lwres/tests/Makefile lib/lwres/unix/Makefile lib/lwres/unix/include/Makefile lib/lwres/unix/include/lwres/Makefile lib/tests/Makefile lib/tests/include/Makefile lib/tests/include/tests/Makefile lib/samples/Makefile lib/samples/Makefile-postinstall unit/Makefile unit/unittest.sh"
#
"doc/doxygen/Makefile") CONFIG_FILES="$CONFIG_FILES doc/doxygen/Makefile" ;;
"doc/doxygen/doxygen-input-filter") CONFIG_FILES="$CONFIG_FILES doc/doxygen/doxygen-input-filter" ;;
"doc/misc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/misc/Makefile" ;;
+ "doc/tex/Makefile") CONFIG_FILES="$CONFIG_FILES doc/tex/Makefile" ;;
+ "doc/tex/armstyle.sty") CONFIG_FILES="$CONFIG_FILES doc/tex/armstyle.sty" ;;
"doc/xsl/Makefile") CONFIG_FILES="$CONFIG_FILES doc/xsl/Makefile" ;;
"doc/xsl/isc-docbook-chunk.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-docbook-chunk.xsl" ;;
"doc/xsl/isc-docbook-html.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-docbook-html.xsl" ;;
- "doc/xsl/isc-docbook-latex.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-docbook-latex.xsl" ;;
"doc/xsl/isc-manpage.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-manpage.xsl" ;;
"doc/xsl/isc-notes-html.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-notes-html.xsl" ;;
- "doc/xsl/isc-notes-latex.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-notes-latex.xsl" ;;
"isc-config.sh") CONFIG_FILES="$CONFIG_FILES isc-config.sh" ;;
"lib/Makefile") CONFIG_FILES="$CONFIG_FILES lib/Makefile" ;;
"lib/bind9/Makefile") CONFIG_FILES="$CONFIG_FILES lib/bind9/Makefile" ;;
AC_PATH_PROGS(PDFLATEX, pdflatex, pdflatex)
AC_SUBST(PDFLATEX)
+AC_PATH_PROGS(DBLATEX, dblatex, dblatex)
+AC_SUBST(DBLATEX)
+
#
# Look for w3m
#
NOM_PATH_FILE(XSLT_DOCBOOK_MAKETOC_XHTML, xhtml/maketoc.xsl, $docbook_xsl_trees)
#
-# Same dance for db2latex
-#
-
-db2latex_xsl_trees="/usr/local/share/db2latex/xsl /usr/pkg/share/xsl/db2latex"
-
-#
-# Look for stylesheets we need.
-#
-
-NOM_PATH_FILE(XSLT_DB2LATEX_STYLE, docbook.xsl, $db2latex_xsl_trees)
-
-#
-# Look for "admonition" image directory. Can't use NOM_PATH_FILE()
-# because it's a directory, so just do the same things, inline.
+# Same dance for dblatex
#
-
-AC_MSG_CHECKING(for db2latex xsl figures)
-for d in $db2latex_xsl_trees
-do
- if test -d $d/figures
- then
- XSLT_DB2LATEX_ADMONITIONS=$d/figures
- AC_MSG_RESULT($d/figures)
- break
- fi
-done
-if test "X$XSLT_DB2LATEX_ADMONITIONS" = "X"
-then
- AC_MSG_RESULT(not found)
- XSLT_DB2LATEX_ADMONITIONS=db2latex/xsl/figures
-fi
-AC_SUBST(XSLT_DB2LATEX_ADMONITIONS)
+dblatex_xsl_trees="/usr/local/share/xml/docbook/stylesheet/dblatex /usr/pkg/share/xml/docbook/stylesheet/dblatex /usr/share/xml/docbook/stylesheet/dblatex"
+NOM_PATH_FILE(XSLT_DBLATEX_STYLE, xsl/docbook.xsl, $dblatex_xsl_trees)
+NOM_PATH_FILE(XSLT_DBLATEX_FASTBOOK, xsl/latex_book_fast.xsl, $dblatex_xsl_trees)
#
# IDN support
AC_SUBST(BIND9_MAJOR)
BIND9_VERSIONSTRING="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}${DESCRIPTION:+ }${DESCRIPTION}"
AC_SUBST(BIND9_VERSIONSTRING)
+BIND9_VERSIONSHORT="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}"
+AC_SUBST(BIND9_VERSIONSHORT)
BIND9_SRCID="SRCID=unset"
if test -f "${srcdir}/srcid"; then
doc/doxygen/Makefile
doc/doxygen/doxygen-input-filter
doc/misc/Makefile
+ doc/tex/Makefile
+ doc/tex/armstyle.sty
doc/xsl/Makefile
doc/xsl/isc-docbook-chunk.xsl
doc/xsl/isc-docbook-html.xsl
- doc/xsl/isc-docbook-latex.xsl
doc/xsl/isc-manpage.xsl
doc/xsl/isc-notes-html.xsl
- doc/xsl/isc-notes-latex.xsl
isc-config.sh
lib/Makefile
lib/bind9/Makefile
# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
# PERFORMANCE OF THIS SOFTWARE.
-# $Id: Makefile.in,v 1.11 2007/06/19 23:47:13 tbox Exp $
-
# This Makefile is a placeholder. It exists merely to make
# sure that its directory gets created in the object directory
# tree when doing a build using separate object directories.
VPATH = @srcdir@
top_srcdir = @top_srcdir@
-SUBDIRS = arm misc xsl doxygen
+SUBDIRS = arm misc xsl doxygen tex
TARGETS =
@BIND9_MAKE_RULES@
--- /dev/null
+noteversion.xml
+pkgversion.xml
+releaseinfo.xml
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000-2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<book xmlns:xi="http://www.w3.org/2001/XInclude">
- <title>BIND 9 Administrator Reference Manual</title>
-
- <bookinfo>
+<!-- Converted by db4-upgrade version 1.0 -->
+<book xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <title>BIND 9 Administrator Reference Manual</title>
<copyright>
<year>2004</year>
<year>2005</year>
<year>2003</year>
<holder>Internet Software Consortium.</holder>
</copyright>
- <xi:include href="releaseinfo.xml"/>
- </bookinfo>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="releaseinfo.xml"/>
+ </info>
- <chapter id="Bv9ARM.ch01">
- <title>Introduction</title>
+ <chapter xml:id="Bv9ARM.ch01"><info><title>Introduction</title></info>
+
<para>
The Internet Domain Name System (<acronym>DNS</acronym>)
consists of the syntax
hierarchical databases.
</para>
- <sect1>
- <title>Scope of Document</title>
+ <section><info><title>Scope of Document</title></info>
+
<para>
The Berkeley Internet Name Domain
<acronym>BIND</acronym> version 9 software package for
system administrators.
</para>
- <xi:include href="pkgversion.xml"/>
- </sect1>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="pkgversion.xml"/>
+ </section>
- <sect1>
- <title>Organization of This Document</title>
+ <section><info><title>Organization of This Document</title></info>
+
<para>
In this document, <emphasis>Chapter 1</emphasis> introduces
the basic <acronym>DNS</acronym> and <acronym>BIND</acronym> concepts. <emphasis>Chapter 2</emphasis>
and the Domain Name
System.
</para>
- </sect1>
- <sect1>
- <title>Conventions Used in This Document</title>
+ </section>
+ <section><info><title>Conventions Used in This Document</title></info>
+
<para>
In this document, we use the following general typographic
</tgroup>
</informaltable>
</para>
- </sect1>
- <sect1>
- <title>The Domain Name System (<acronym>DNS</acronym>)</title>
+ </section>
+ <section><info><title>The Domain Name System (<acronym>DNS</acronym>)</title></info>
+
<para>
The purpose of this document is to explain the installation
and upkeep of the <acronym>BIND</acronym> (Berkeley Internet
(<acronym>DNS</acronym>) as they relate to <acronym>BIND</acronym>.
</para>
- <sect2>
- <title>DNS Fundamentals</title>
+ <section><info><title>DNS Fundamentals</title></info>
+
<para>
The Domain Name System (DNS) is a hierarchical, distributed
from ISC as a separate download.
</para>
- </sect2><sect2>
- <title>Domains and Domain Names</title>
+ </section><section><info><title>Domains and Domain Names</title></info>
+
<para>
The data stored in the DNS is identified by <emphasis>domain names</emphasis> that are organized as a tree according to
the DNS protocol, please refer to the standards documents listed in
<xref linkend="rfcs"/>.
</para>
- </sect2>
+ </section>
- <sect2>
- <title>Zones</title>
+ <section><info><title>Zones</title></info>
+
<para>
To properly operate a name server, it is important to understand
the difference between a <emphasis>zone</emphasis>
be a slave server for your <emphasis>domain</emphasis>, you are
actually asking for slave service for some collection of zones.
</para>
- </sect2>
+ </section>
- <sect2>
- <title>Authoritative Name Servers</title>
+ <section><info><title>Authoritative Name Servers</title></info>
+
<para>
Each zone is served by at least
<command>dig</command> (<xref linkend="diagnostic_tools"/>).
</para>
- <sect3>
- <title>The Primary Master</title>
+ <section><info><title>The Primary Master</title></info>
+
<para>
The authoritative server where the master copy of the zone
by humans at all, but may instead be the result of
<emphasis>dynamic update</emphasis> operations.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Slave Servers</title>
+ <section><info><title>Slave Servers</title></info>
+
<para>
The other authoritative servers, the <emphasis>slave</emphasis>
servers (also known as <emphasis>secondary</emphasis> servers)
to transfer it from another slave. In other words, a slave server
may itself act as a master to a subordinate slave server.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Stealth Servers</title>
+ <section><info><title>Stealth Servers</title></info>
+
<para>
Usually all of the zone's authoritative servers are listed in
with the outside world.
</para>
- </sect3>
+ </section>
- </sect2>
- <sect2>
+ </section>
+ <section><info><title>Caching Name Servers</title></info>
- <title>Caching Name Servers</title>
+
<!--
- Terminology here is inconsistent. Probably ought to
Time To Live (TTL) field associated with each resource record.
</para>
- <sect3>
- <title>Forwarding</title>
+ <section><info><title>Forwarding</title></info>
+
<para>
Even a caching name server does not necessarily perform
that can do it, and that server would query the Internet <acronym>DNS</acronym> servers
on the internal server's behalf.
</para>
- </sect3>
+ </section>
- </sect2>
+ </section>
- <sect2>
- <title>Name Servers in Multiple Roles</title>
+ <section><info><title>Name Servers in Multiple Roles</title></info>
+
<para>
The <acronym>BIND</acronym> name server can
be placed inside a firewall.
</para>
- </sect2>
- </sect1>
+ </section>
+ </section>
</chapter>
- <chapter id="Bv9ARM.ch02">
- <title><acronym>BIND</acronym> Resource Requirements</title>
+ <chapter xml:id="Bv9ARM.ch02"><info><title><acronym>BIND</acronym> Resource Requirements</title></info>
+
- <sect1>
- <title>Hardware requirements</title>
+ <section><info><title>Hardware requirements</title></info>
+
<para>
<acronym>DNS</acronym> hardware requirements have
full utilization of
multiprocessor systems for installations that need it.
</para>
- </sect1>
- <sect1>
- <title>CPU Requirements</title>
+ </section>
+ <section><info><title>CPU Requirements</title></info>
+
<para>
CPU requirements for <acronym>BIND</acronym> 9 range from
i486-class machines
machines if you intend to process many dynamic updates and DNSSEC
signed zones, serving many thousands of queries per second.
</para>
- </sect1>
+ </section>
- <sect1>
- <title>Memory Requirements</title>
+ <section><info><title>Memory Requirements</title></info>
+
<para>
The memory of the server has to be large enough to fit the
cache and zones loaded off disk. The <command>max-cache-size</command>
limit the amount
of memory used by the mechanism.
It is still good practice to have enough memory to load
- all zone and cache data into memory — unfortunately, the best
+ all zone and cache data into memory — unfortunately, the best
way
to determine this for a given installation is to watch the name server
in operation. After a few weeks the server process should reach
- Add something here about leaving overhead for attacks?
- How much overhead? Percentage?
-->
- </sect1>
+ </section>
- <sect1>
- <title>Name Server Intensive Environment Issues</title>
+ <section><info><title>Name Server Intensive Environment Issues</title></info>
+
<para>
For name server intensive environments, there are two alternative
configurations that may be used. The first is where clients and
this has the disadvantage of making many more external queries,
as none of the name servers share their cached data.
</para>
- </sect1>
+ </section>
- <sect1>
- <title>Supported Operating Systems</title>
+ <section><info><title>Supported Operating Systems</title></info>
+
<para>
ISC <acronym>BIND</acronym> 9 compiles and runs on a large
number
directory
of the BIND 9 source distribution.
</para>
- </sect1>
+ </section>
</chapter>
- <chapter id="Bv9ARM.ch03">
- <title>Name Server Configuration</title>
+ <chapter xml:id="Bv9ARM.ch03"><info><title>Name Server Configuration</title></info>
+
<para>
In this chapter we provide some suggested configurations along
with guidelines for their use. We suggest reasonable values for
certain option settings.
</para>
- <sect1 id="sample_configuration">
- <title>Sample Configurations</title>
- <sect2>
- <title>A Caching-only Name Server</title>
+ <section xml:id="sample_configuration"><info><title>Sample Configurations</title></info>
+
+ <section><info><title>A Caching-only Name Server</title></info>
+
<para>
The following sample configuration is appropriate for a caching-only
name server for use by clients internal to a corporation. All
};
</programlisting>
- </sect2>
+ </section>
- <sect2>
- <title>An Authoritative-only Name Server</title>
+ <section><info><title>An Authoritative-only Name Server</title></info>
+
<para>
This sample configuration is for an authoritative-only server
that is the master server for "<filename>example.com</filename>"
};
</programlisting>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1>
- <title>Load Balancing</title>
+ <section><info><title>Load Balancing</title></info>
+
<!--
- Add explanation of why load balancing is fragile at best
- and completely pointless in the general case.
<xref endterm="rrset_ordering_title" linkend="rrset_ordering"/>.
</para>
- </sect1>
+ </section>
- <sect1>
- <title>Name Server Operations</title>
+ <section><info><title>Name Server Operations</title></info>
+
- <sect2>
- <title>Tools for Use With the Name Server Daemon</title>
+ <section><info><title>Tools for Use With the Name Server Daemon</title></info>
+
<para>
This section describes several indispensable diagnostic,
administrative and monitoring tools available to the system
administrator for controlling and debugging the name server
daemon.
</para>
- <sect3 id="diagnostic_tools">
- <title>Diagnostic Tools</title>
+ <section xml:id="diagnostic_tools"><info><title>Diagnostic Tools</title></info>
+
<para>
The <command>dig</command>, <command>host</command>, and
<command>nslookup</command> programs are all command
<variablelist>
<varlistentry>
- <term id="dig"><command>dig</command></term>
+ <term xml:id="dig"><command>dig</command></term>
<listitem>
<para>
The domain information groper (<command>dig</command>)
accessible
from the command line.
</para>
- <cmdsynopsis label="Usage">
+ <cmdsynopsis label="Usage" sepchar=" ">
<command>dig</command>
- <arg>@<replaceable>server</replaceable></arg>
- <arg choice="plain"><replaceable>domain</replaceable></arg>
- <arg><replaceable>query-type</replaceable></arg>
- <arg><replaceable>query-class</replaceable></arg>
- <arg>+<replaceable>query-option</replaceable></arg>
- <arg>-<replaceable>dig-option</replaceable></arg>
- <arg>%<replaceable>comment</replaceable></arg>
+ <arg choice="opt" rep="norepeat">@<replaceable>server</replaceable></arg>
+ <arg choice="plain" rep="norepeat"><replaceable>domain</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><replaceable>query-type</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><replaceable>query-class</replaceable></arg>
+ <arg choice="opt" rep="norepeat">+<replaceable>query-option</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-<replaceable>dig-option</replaceable></arg>
+ <arg choice="opt" rep="norepeat">%<replaceable>comment</replaceable></arg>
</cmdsynopsis>
<para>
The usual simple use of <command>dig</command> will take the form
functionality
can be extended with the use of options.
</para>
- <cmdsynopsis label="Usage">
+ <cmdsynopsis label="Usage" sepchar=" ">
<command>host</command>
- <arg>-aCdlnrsTwv</arg>
- <arg>-c <replaceable>class</replaceable></arg>
- <arg>-N <replaceable>ndots</replaceable></arg>
- <arg>-t <replaceable>type</replaceable></arg>
- <arg>-W <replaceable>timeout</replaceable></arg>
- <arg>-R <replaceable>retries</replaceable></arg>
- <arg>-m <replaceable>flag</replaceable></arg>
- <arg>-4</arg>
- <arg>-6</arg>
- <arg choice="plain"><replaceable>hostname</replaceable></arg>
- <arg><replaceable>server</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-aCdlnrsTwv</arg>
+ <arg choice="opt" rep="norepeat">-c <replaceable>class</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-N <replaceable>ndots</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-t <replaceable>type</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-W <replaceable>timeout</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-R <replaceable>retries</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-m <replaceable>flag</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-4</arg>
+ <arg choice="opt" rep="norepeat">-6</arg>
+ <arg choice="plain" rep="norepeat"><replaceable>hostname</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><replaceable>server</replaceable></arg>
</cmdsynopsis>
<para>
For more information and a list of available commands and
the name and requested information for a host or
domain.
</para>
- <cmdsynopsis label="Usage">
+ <cmdsynopsis label="Usage" sepchar=" ">
<command>nslookup</command>
- <arg rep="repeat">-option</arg>
- <group>
- <arg><replaceable>host-to-find</replaceable></arg>
- <arg>- <arg>server</arg></arg>
+ <arg rep="repeat" choice="opt">-option</arg>
+ <group choice="opt" rep="norepeat">
+ <arg choice="opt" rep="norepeat"><replaceable>host-to-find</replaceable></arg>
+ <arg choice="opt" rep="norepeat">- <arg choice="opt" rep="norepeat">server</arg></arg>
</group>
</cmdsynopsis>
<para>
</varlistentry>
</variablelist>
- </sect3>
+ </section>
- <sect3 id="admin_tools">
- <title>Administrative Tools</title>
+ <section xml:id="admin_tools"><info><title>Administrative Tools</title></info>
+
<para>
Administrative tools play an integral part in the management
of a server.
</para>
<variablelist>
- <varlistentry id="named-checkconf" xreflabel="Named Configuration Checking application">
+ <varlistentry xml:id="named-checkconf" xreflabel="Named Configuration Checking application">
<term><command>named-checkconf</command></term>
<listitem>
The <command>named-checkconf</command> program
checks the syntax of a <filename>named.conf</filename> file.
</para>
- <cmdsynopsis label="Usage">
+ <cmdsynopsis label="Usage" sepchar=" ">
<command>named-checkconf</command>
- <arg>-jvz</arg>
- <arg>-t <replaceable>directory</replaceable></arg>
- <arg><replaceable>filename</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-jvz</arg>
+ <arg choice="opt" rep="norepeat">-t <replaceable>directory</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><replaceable>filename</replaceable></arg>
</cmdsynopsis>
</listitem>
</varlistentry>
- <varlistentry id="named-checkzone" xreflabel="Zone Checking application">
+ <varlistentry xml:id="named-checkzone" xreflabel="Zone Checking application">
<term><command>named-checkzone</command></term>
<listitem>
checks a master file for
syntax and consistency.
</para>
- <cmdsynopsis label="Usage">
+ <cmdsynopsis label="Usage" sepchar=" ">
<command>named-checkzone</command>
- <arg>-djqvD</arg>
- <arg>-c <replaceable>class</replaceable></arg>
- <arg>-o <replaceable>output</replaceable></arg>
- <arg>-t <replaceable>directory</replaceable></arg>
- <arg>-w <replaceable>directory</replaceable></arg>
- <arg>-k <replaceable>(ignore|warn|fail)</replaceable></arg>
- <arg>-n <replaceable>(ignore|warn|fail)</replaceable></arg>
- <arg>-W <replaceable>(ignore|warn)</replaceable></arg>
- <arg choice="plain"><replaceable>zone</replaceable></arg>
- <arg><replaceable>filename</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-djqvD</arg>
+ <arg choice="opt" rep="norepeat">-c <replaceable>class</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-o <replaceable>output</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-t <replaceable>directory</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-w <replaceable>directory</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-k <replaceable>(ignore|warn|fail)</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-n <replaceable>(ignore|warn|fail)</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-W <replaceable>(ignore|warn)</replaceable></arg>
+ <arg choice="plain" rep="norepeat"><replaceable>zone</replaceable></arg>
+ <arg choice="opt" rep="norepeat"><replaceable>filename</replaceable></arg>
</cmdsynopsis>
</listitem>
</varlistentry>
- <varlistentry id="named-compilezone" xreflabel="Zone Compilation application">
+ <varlistentry xml:id="named-compilezone" xreflabel="Zone Compilation application">
<term><command>named-compilezone</command></term>
<listitem>
<para>
</para>
</listitem>
</varlistentry>
- <varlistentry id="rndc" xreflabel="Remote Name Daemon Control application">
+ <varlistentry xml:id="rndc" xreflabel="Remote Name Daemon Control application">
<term><command>rndc</command></term>
<listitem>
options
it will display a usage message as follows:
</para>
- <cmdsynopsis label="Usage">
+ <cmdsynopsis label="Usage" sepchar=" ">
<command>rndc</command>
- <arg>-c <replaceable>config</replaceable></arg>
- <arg>-s <replaceable>server</replaceable></arg>
- <arg>-p <replaceable>port</replaceable></arg>
- <arg>-y <replaceable>key</replaceable></arg>
- <arg choice="plain"><replaceable>command</replaceable></arg>
- <arg rep="repeat"><replaceable>command</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-c <replaceable>config</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-s <replaceable>server</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-p <replaceable>port</replaceable></arg>
+ <arg choice="opt" rep="norepeat">-y <replaceable>key</replaceable></arg>
+ <arg choice="plain" rep="norepeat"><replaceable>command</replaceable></arg>
+ <arg rep="repeat" choice="opt"><replaceable>command</replaceable></arg>
</cmdsynopsis>
<para>See <xref linkend="man.rndc"/> for details of
</varlistentry>
</variablelist>
- </sect3>
- </sect2>
- <sect2>
+ </section>
+ </section>
+ <section><info><title>Signals</title></info>
- <title>Signals</title>
+
<para>
Certain UNIX signals cause the name server to take specific
actions, as described in the following table. These signals can
</tbody>
</tgroup>
</informaltable>
- </sect2>
- </sect1>
+ </section>
+ </section>
</chapter>
- <chapter id="Bv9ARM.ch04">
- <title>Advanced DNS Features</title>
+ <chapter xml:id="Bv9ARM.ch04"><info><title>Advanced DNS Features</title></info>
+
- <sect1 id="notify">
+ <section xml:id="notify"><info><title>Notify</title></info>
- <title>Notify</title>
+
<para>
<acronym>DNS</acronym> NOTIFY is a mechanism that allows master
servers to notify their slave servers of changes to a zone's data. In
zones that it loads.
</note>
- </sect1>
+ </section>
- <sect1 id="dynamic_update">
- <title>Dynamic Update</title>
+ <section xml:id="dynamic_update"><info><title>Dynamic Update</title></info>
+
<para>
Dynamic Update is a method for adding, replacing or deleting
signatures and an explicit server policy.
</para>
- <sect2 id="journal">
- <title>The journal file</title>
+ <section xml:id="journal"><info><title>The journal file</title></info>
+
<para>
All changes made to a zone using dynamic update are stored
<para>
The zone files of dynamic zones cannot normally be edited by
hand because they are not guaranteed to contain the most recent
- dynamic changes — those are only in the journal file.
+ dynamic changes — those are only in the journal file.
The only way to ensure that the zone file of a dynamic zone
is up to date is to run <command>rndc stop</command>.
</para>
<command>rndc sync -clean</command>.
</para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1 id="incremental_zone_transfers">
- <title>Incremental Zone Transfers (IXFR)</title>
+ <section xml:id="incremental_zone_transfers"><info><title>Incremental Zone Transfers (IXFR)</title></info>
+
<para>
The incremental zone transfer (IXFR) protocol is a way for
IXFR, see the description of the <command>request-ixfr</command> clause
of the <command>server</command> statement.
</para>
- </sect1>
+ </section>
- <sect1>
- <title>Split DNS</title>
+ <section><info><title>Split DNS</title></info>
+
<para>
Setting up different views, or visibility, of the DNS space to
internal and external resolvers is usually referred to as a
on the Internet. Split DNS can also be used to allow mail from outside
back in to the internal network.
</para>
- <sect2>
- <title>Example split DNS setup</title>
+ <section><info><title>Example split DNS setup</title></info>
+
<para>
Let's say a company named <emphasis>Example, Inc.</emphasis>
(<literal>example.com</literal>)
nameserver 172.16.72.4
</programlisting>
- </sect2>
- </sect1>
- <sect1 id="tsig">
- <title>TSIG</title>
+ </section>
+ </section>
+ <section xml:id="tsig"><info><title>TSIG</title></info>
+
<para>
This is a short guide to setting up Transaction SIGnatures
(TSIG) based transaction security in <acronym>BIND</acronym>. It describes changes
of the <command>key</command>.
</para>
- <sect2>
- <title>Generate Shared Keys for Each Pair of Hosts</title>
+ <section><info><title>Generate Shared Keys for Each Pair of Hosts</title></info>
+
<para>
A shared secret is generated to be shared between <emphasis>host1</emphasis> and <emphasis>host2</emphasis>.
An arbitrary key name is chosen: "host1-host2.". The key name must
be the same on both hosts.
</para>
- <sect3>
- <title>Automatic Generation</title>
+ <section><info><title>Automatic Generation</title></info>
+
<para>
The following command will generate a 128-bit (16 byte) HMAC-SHA256
key as described above. Longer keys are better, but shorter keys
The string "<literal>La/E5CjG9O+os1jq0a2jdA==</literal>" can
be used as the shared secret.
</para>
- </sect3>
- <sect3>
- <title>Manual Generation</title>
+ </section>
+ <section><info><title>Manual Generation</title></info>
+
<para>
The shared secret is simply a random sequence of bits, encoded
in base-64. Most ASCII strings are valid base-64 strings (assuming
Also, a known string can be run through <command>mmencode</command> or
a similar program to generate base-64 encoded data.
</para>
- </sect3>
- </sect2>
- <sect2>
- <title>Copying the Shared Secret to Both Machines</title>
+ </section>
+ </section>
+ <section><info><title>Copying the Shared Secret to Both Machines</title></info>
+
<para>
This is beyond the scope of DNS. A secure transport mechanism
should be used. This could be secure FTP, ssh, telephone, etc.
</para>
- </sect2>
- <sect2>
- <title>Informing the Servers of the Key's Existence</title>
+ </section>
+ <section><info><title>Informing the Servers of the Key's Existence</title></info>
+
<para>
Imagine <emphasis>host1</emphasis> and <emphasis>host 2</emphasis>
are
signature. If the signature is successfully verified, the
response is signed by the same key.
</para>
- </sect2>
+ </section>
- <sect2>
- <title>Instructing the Server to Use the Key</title>
+ <section><info><title>Instructing the Server to Use the Key</title></info>
+
<para>
Since keys are shared between two hosts only, the server must
be told when keys are to be used. The following is added to the <filename>named.conf</filename> file
configuration file (with <emphasis>host1</emphasis>'s address) for <emphasis>host2</emphasis> to
sign request messages to <emphasis>host1</emphasis>.
</para>
- </sect2>
- <sect2>
- <title>TSIG Key Based Access Control</title>
+ </section>
+ <section><info><title>TSIG Key Based Access Control</title></info>
+
<para>
<acronym>BIND</acronym> allows IP addresses and ranges
to be specified in ACL
the more flexible <command>update-policy</command> statement.
</para>
- </sect2>
- <sect2>
- <title>Errors</title>
+ </section>
+ <section><info><title>Errors</title></info>
+
<para>
The processing of TSIG signed messages can result in
NOTAUTH (not authenticated).
</para>
- </sect2>
- </sect1>
- <sect1>
- <title>TKEY</title>
+ </section>
+ </section>
+ <section><info><title>TKEY</title></info>
+
<para><command>TKEY</command>
is a mechanism for automatically generating a shared secret
and the shared secret is derived by both participants.
</para>
- </sect1>
- <sect1>
- <title>SIG(0)</title>
+ </section>
+ <section><info><title>SIG(0)</title></info>
+
<para>
<acronym>BIND</acronym> 9 partially supports DNSSEC SIG(0)
generates SIG(0) signed messages is <command>nsupdate</command>.
</para>
- </sect1>
- <sect1 id="DNSSEC">
- <title>DNSSEC</title>
+ </section>
+ <section xml:id="DNSSEC"><info><title>DNSSEC</title></info>
+
<para>
Cryptographic authentication of DNS information is possible
zone key of another zone above this one in the DNS tree.
</para>
- <sect2>
- <title>Generating Keys</title>
+ <section><info><title>Generating Keys</title></info>
+
<para>
The <command>dnssec-keygen</command> program is used to
<command>$INCLUDE</command> statements.
</para>
- </sect2>
- <sect2>
- <title>Signing the Zone</title>
+ </section>
+ <section><info><title>Signing the Zone</title></info>
+
<para>
The <command>dnssec-signzone</command> program is used
secure entry point to the zone.
</para>
- </sect2>
+ </section>
- <sect2>
- <title>Configuring Servers</title>
+ <section><info><title>Configuring Servers</title></info>
+
<para>
To enable <command>named</command> to respond appropriately
This referred to the zone, not the response.)
</para>
</note>
- </sect2>
-
- </sect1>
+ </section>
+ </section>
- <xi:include href="dnssec.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="dnssec.xml"/>
- <xi:include href="managed-keys.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="managed-keys.xml"/>
- <xi:include href="pkcs11.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="pkcs11.xml"/>
- <xi:include href="dlz.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="dlz.xml"/>
- <xi:include href="dyndb.xml"/>
-
- <sect1>
- <title>IPv6 Support in <acronym>BIND</acronym> 9</title>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="dyndb.xml"/>
+ <section><info><title>IPv6 Support in <acronym>BIND</acronym> 9</title></info>
<para>
<acronym>BIND</acronym> 9 fully supports all currently
defined forms of IPv6 name to address and address to name
see <xref linkend="ipv6addresses"/>.
</para>
- <sect2>
- <title>Address Lookups Using AAAA Records</title>
+ <section><info><title>Address Lookups Using AAAA Records</title></info>
+
<para>
The IPv6 AAAA record is a parallel to the IPv4 A record,
a AAAA, with <literal>::ffff:192.168.42.1</literal> as
the address.
</para>
- </sect2>
- <sect2>
- <title>Address to Name Lookups Using Nibble Format</title>
+ </section>
+ <section><info><title>Address to Name Lookups Using Nibble Format</title></info>
+
<para>
When looking up an address in nibble format, the address
host.example.com. )
</programlisting>
- </sect2>
- </sect1>
+ </section>
+ </section>
</chapter>
- <chapter id="Bv9ARM.ch05">
- <title>The <acronym>BIND</acronym> 9 Lightweight Resolver</title>
- <sect1>
- <title>The Lightweight Resolver Library</title>
+ <chapter xml:id="Bv9ARM.ch05"><info><title>The <acronym>BIND</acronym> 9 Lightweight Resolver</title></info>
+
+ <section><info><title>The Lightweight Resolver Library</title></info>
+
<para>
Traditionally applications have been linked with a stub resolver
library that sends recursive DNS queries to a local caching name
a simple UDP-based protocol, the "lightweight resolver protocol"
that is distinct from and simpler than the full DNS protocol.
</para>
- </sect1>
- <sect1 id="lwresd">
- <title>Running a Resolver Daemon</title>
+ </section>
+ <section xml:id="lwresd"><info><title>Running a Resolver Daemon</title></info>
+
<para>
To use the lightweight resolver interface, the system must
<option>lwres-tasks</option> and <option>lwres-clients</option>
statements in the configuration.
</para>
- </sect1>
+ </section>
</chapter>
- <chapter id="Bv9ARM.ch06">
- <title><acronym>BIND</acronym> 9 Configuration Reference</title>
+ <chapter xml:id="Bv9ARM.ch06"><info><title><acronym>BIND</acronym> 9 Configuration Reference</title></info>
+
<para>
<acronym>BIND</acronym> 9 configuration is broadly similar
using the shell script
<filename>contrib/named-bootconf/named-bootconf.sh</filename>.
</para>
- <sect1 id="configuration_file_elements">
- <title>Configuration File Elements</title>
+ <section xml:id="configuration_file_elements"><info><title>Configuration File Elements</title></info>
+
<para>
Following is a list of elements used throughout the <acronym>BIND</acronym> configuration
file documentation:
</tbody>
</tgroup>
</informaltable>
- <sect2 id="address_match_lists">
- <title>Address Match Lists</title>
- <sect3>
- <title>Syntax</title>
+ <section xml:id="address_match_lists"><info><title>Address Match Lists</title></info>
+
+ <section><info><title>Syntax</title></info>
+
<programlisting><varname>address_match_list</varname> = address_match_list_element ;
<optional> address_match_list_element; ... </optional>
key key_id | acl_name | { address_match_list } )
</programlisting>
- </sect3>
- <sect3>
- <title>Definition and Usage</title>
+ </section>
+ <section><info><title>Definition and Usage</title></info>
+
<para>
Address match lists are primarily used to determine access
control for various server operations. They are also used in
that problem by having 1.2.3.13 blocked by the negation, but
all other 1.2.3.* hosts fall through.
</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2>
- <title>Comment Syntax</title>
+ <section><info><title>Comment Syntax</title></info>
+
<para>
The <acronym>BIND</acronym> 9 comment syntax allows for
in the C, C++, or shell/perl style.
</para>
- <sect3>
- <title>Syntax</title>
+ <section><info><title>Syntax</title></info>
+
<para>
<programlisting>/* This is a <acronym>BIND</acronym> comment as in C */</programlisting>
<programlisting># This is a <acronym>BIND</acronym> comment as in common UNIX shells
# and perl</programlisting>
</para>
- </sect3>
- <sect3>
- <title>Definition and Usage</title>
+ </section>
+ <section><info><title>Definition and Usage</title></info>
+
<para>
Comments may appear anywhere that whitespace may appear in
a <acronym>BIND</acronym> configuration file.
statement.
</para>
</warning>
- </sect3>
- </sect2>
- </sect1>
+ </section>
+ </section>
+ </section>
- <sect1 id="Configuration_File_Grammar">
- <title>Configuration File Grammar</title>
+ <section xml:id="Configuration_File_Grammar"><info><title>Configuration File Grammar</title></info>
+
<para>
A <acronym>BIND</acronym> 9 configuration consists of
configuration.
</para>
- <sect2>
- <title><command>acl</command> Statement Grammar</title>
+ <section><info><title><command>acl</command> Statement Grammar</title></info>
+
<programlisting><command>acl</command> acl-name {
address_match_list
};
</programlisting>
- </sect2>
- <sect2 id="acl">
- <title><command>acl</command> Statement Definition and
- Usage</title>
+ </section>
+ <section xml:id="acl"><info><title><command>acl</command> Statement Definition and
+ Usage</title></info>
+
<para>
The <command>acl</command> statement assigns a symbolic
</tbody>
</tgroup>
</informaltable>
- </sect2>
- <sect2>
- <title><command>controls</command> Statement Grammar</title>
+ </section>
+ <section><info><title><command>controls</command> Statement Grammar</title></info>
+
<programlisting><command>controls</command> {
[ inet ( ip_addr | * ) [ port ip_port ]
};
</programlisting>
- </sect2>
+ </section>
- <sect2 id="controls_statement_definition_and_usage">
- <title><command>controls</command> Statement Definition and
- Usage</title>
+ <section xml:id="controls_statement_definition_and_usage"><info><title><command>controls</command> Statement Definition and
+ Usage</title></info>
+
<para>
The <command>controls</command> statement declares control
<command>controls { };</command>.
</para>
- </sect2>
- <sect2>
- <title><command>include</command> Statement Grammar</title>
+ </section>
+ <section><info><title><command>include</command> Statement Grammar</title></info>
+
<programlisting><command>include</command> <replaceable>filename</replaceable>;</programlisting>
- </sect2>
- <sect2>
- <title><command>include</command> Statement Definition and
- Usage</title>
+ </section>
+ <section><info><title><command>include</command> Statement Definition and
+ Usage</title></info>
+
<para>
The <command>include</command> statement inserts the
that are readable only by the name server.
</para>
- </sect2>
- <sect2>
- <title><command>key</command> Statement Grammar</title>
+ </section>
+ <section><info><title><command>key</command> Statement Grammar</title></info>
+
<programlisting><command>key</command> <replaceable>key_id</replaceable> {
algorithm <replaceable>algorithm_id</replaceable>;
};
</programlisting>
- </sect2>
+ </section>
- <sect2>
- <title><command>key</command> Statement Definition and Usage</title>
+ <section><info><title><command>key</command> Statement Definition and Usage</title></info>
+
<para>
The <command>key</command> statement defines a shared
encoded string.
</para>
- </sect2>
- <sect2>
- <title><command>logging</command> Statement Grammar</title>
+ </section>
+ <section><info><title><command>logging</command> Statement Grammar</title></info>
+
<programlisting><command>logging</command> {
[ <command>channel</command> <replaceable>channel_name</replaceable> {
};
</programlisting>
- </sect2>
+ </section>
- <sect2>
- <title><command>logging</command> Statement Definition and
- Usage</title>
+ <section><info><title><command>logging</command> Statement Definition and
+ Usage</title></info>
+
<para>
The <command>logging</command> statement configures a
was specified.
</para>
- <sect3>
- <title>The <command>channel</command> Phrase</title>
+ <section><info><title>The <command>channel</command> Phrase</title></info>
+
<para>
All log output goes to one or more <emphasis>channels</emphasis>;
the default logging by pointing categories at channels you have
defined.
</para>
- </sect3>
+ </section>
- <sect3 id="the_category_phrase">
- <title>The <command>category</command> Phrase</title>
+ <section xml:id="the_category_phrase"><info><title>The <command>category</command> Phrase</title></info>
+
<para>
There are many categories, so you can send the logs you want
of the types of log information they contain. More
categories may be added in future <acronym>BIND</acronym> releases.
</para>
- <xi:include href="logging-categories.xml"/>
- </sect3>
- <sect3>
- <title>The <command>query-errors</command> Category</title>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="logging-categories.xml"/>
+ </section>
+ <section><info><title>The <command>query-errors</command> Category</title></info>
<para>
The <command>query-errors</command> category is
specifically intended for debugging purposes: To identify
This is because any unexpected results can be difficult to
debug in the recursion case.
</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2>
- <title><command>lwres</command> Statement Grammar</title>
+ <section><info><title><command>lwres</command> Statement Grammar</title></info>
+
<para>
This is the grammar of the <command>lwres</command>
};
</programlisting>
- </sect2>
- <sect2>
- <title><command>lwres</command> Statement Definition and Usage</title>
+ </section>
+ <section><info><title><command>lwres</command> Statement Definition and Usage</title></info>
+
<para>
The <command>lwres</command> statement configures the
resolver can handle at any one time equals
<option>lwres-tasks</option> times <option>lwres-clients</option>.
</para>
- </sect2>
- <sect2>
- <title><command>masters</command> Statement Grammar</title>
+ </section>
+ <section><info><title><command>masters</command> Statement Grammar</title></info>
+
<programlisting>
<command>masters</command> <replaceable>name</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>dscp <replaceable>ip_dscp</replaceable></optional> { ( <replaceable>masters_list</replaceable> |
<replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> };
</programlisting>
- </sect2>
+ </section>
- <sect2>
- <title><command>masters</command> Statement Definition and
- Usage</title>
+ <section><info><title><command>masters</command> Statement Definition and
+ Usage</title></info>
+
<para><command>masters</command>
lists allow for a common set of masters to be easily used by
multiple stub and slave zones in their <command>masters</command>
or <command>also-notify</command> lists.
</para>
- </sect2>
+ </section>
- <sect2>
- <title><command>options</command> Statement Grammar</title>
+ <section><info><title><command>options</command> Statement Grammar</title></info>
+
<para>
This is the grammar of the <command>options</command>
};
</programlisting>
- </sect2>
+ </section>
- <sect2 id="options">
- <title><command>options</command> Statement Definition and
- Usage</title>
+ <section xml:id="options"><info><title><command>options</command> Statement Definition and
+ Usage</title></info>
+
<para>
The <command>options</command> statement sets up global
uses
<command>libfstrm</command> (a lightweight high-speed
framing library, see
- <ulink url="https://github.com/farsightsec/fstrm"
- >https://github.com/farsightsec/fstrm</ulink>) to send
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://github.com/farsightsec/fstrm">https://github.com/farsightsec/fstrm</link>) to send
event payloads which are encoded using Protocol Buffers
(<command>libprotobuf-c</command>, a mechanism for
serializing structured data developed
by Google, Inc.; see
- <ulink url="https://developers.google.com/protocol-buffers/"
- >https://developers.google.com/protocol-buffers</ulink>).
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers</link>).
</para>
<para>
To enable <command>dnstap</command> at compile time,
</para>
<para>
For more information on <command>dnstap</command>, see
- <ulink url="http://dnstap.info"
- >http://dnstap.info</ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://dnstap.info">http://dnstap.info</link>.
</para>
</listitem>
</varlistentry>
The PID file is used by programs that want to send signals to
the running
name server. Specifying <command>pid-file none</command> disables the
- use of a PID file — no file will be written and any
+ use of a PID file — no file will be written and any
existing one will be removed. Note that <command>none</command>
is a keyword, not a filename, and therefore is not enclosed
in
</listitem>
</varlistentry>
- <varlistentry id="root_delegation_only">
+ <varlistentry xml:id="root_delegation_only">
<term><command>root-delegation-only</command></term>
<listitem>
<para>
installed along with <acronym>BIND</acronym> 9, and is
current as of the release date. If the DLV key expires, a
new copy of <filename>bind.keys</filename> can be downloaded
- from <ulink url="https://www.isc.org/solutions/dlv/"
- >https://www.isc.org/solutions/dlv/</ulink>.
+ from <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://www.isc.org/solutions/dlv/">https://www.isc.org/solutions/dlv/</link>.
</para>
<para>
(To prevent problems if <filename>bind.keys</filename> is
</varlistentry>
</variablelist>
- <sect3 id="boolean_options">
- <title>Boolean Options</title>
+ <section xml:id="boolean_options"><info><title>Boolean Options</title></info>
+
<variablelist>
</variablelist>
- </sect3>
+ </section>
- <sect3>
- <title>Forwarding</title>
+ <section><info><title>Forwarding</title></info>
+
<para>
The forwarding facility can be used to create a large site-wide
cache on a few servers, reducing traffic over links to external
This option is only meaningful if the
forwarders list is not empty. A value of <varname>first</varname>,
the default, causes the server to query the forwarders
- first — and
+ first — and
if that doesn't answer the question, the server will then
look for
the answer itself. If <varname>only</varname> is
or have a different <command>forward only/first</command> behavior,
or not forward at all, see <xref linkend="zone_statement_grammar"/>.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Dual-stack Servers</title>
+ <section><info><title>Dual-stack Servers</title></info>
+
<para>
Dual-stack servers are used as servers of last resort to work
around
</listitem>
</varlistentry>
</variablelist>
- </sect3>
+ </section>
- <sect3 id="access_control">
- <title>Access Control</title>
+ <section xml:id="access_control"><info><title>Access Control</title></info>
+
<para>
Access to the server can be restricted based on the IP address
</varlistentry>
</variablelist>
- </sect3>
+ </section>
- <sect3>
- <title>Interfaces</title>
+ <section><info><title>Interfaces</title></info>
+
<para>
The interfaces and ports that the server will answer queries
from may be specified using the <command>listen-on</command> option. <command>listen-on</command> takes
<programlisting>listen-on-v6 { none; };
</programlisting>
- </sect3>
+ </section>
- <sect3 id="query_address">
- <title>Query Address</title>
+ <section xml:id="query_address"><info><title>Query Address</title></info>
+
<para>
If the server doesn't know the answer to a question, it will
query other name servers. <command>query-source</command> specifies
<command>notify-source</command>.
</para>
</note>
- </sect3>
+ </section>
- <sect3 id="zone_transfers">
- <title>Zone Transfers</title>
+ <section xml:id="zone_transfers"><info><title>Zone Transfers</title></info>
+
<para>
<acronym>BIND</acronym> has mechanisms in place to
facilitate zone transfers
</variablelist>
- </sect3>
+ </section>
- <sect3>
- <title>UDP Port Lists</title>
+ <section><info><title>UDP Port Lists</title></info>
+
<para>
<command>use-v4-udp-ports</command>,
<command>avoid-v4-udp-ports</command>,
sense; they are provided for backward compatibility and
to possibly simplify the port specification.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Operating System Resource Limits</title>
+ <section><info><title>Operating System Resource Limits</title></info>
+
<para>
The server's usage of many system resources can be limited.
</variablelist>
- </sect3>
+ </section>
- <sect3 id="server_resource_limits">
- <title>Server Resource Limits</title>
+ <section xml:id="server_resource_limits"><info><title>Server Resource Limits</title></info>
+
<para>
The following options set limits on the server's
</listitem>
</varlistentry>
- <varlistentry id="clients-per-query">
+ <varlistentry xml:id="clients-per-query">
<term><command>clients-per-query</command></term>
<term><command>max-clients-per-query</command></term>
<listitem>
</listitem>
</varlistentry>
- <varlistentry id="fetches-per-zone">
+ <varlistentry xml:id="fetches-per-zone">
<term><command>fetches-per-zone</command></term>
<listitem>
<para>
</listitem>
</varlistentry>
- <varlistentry id="fetches-per-server">
+ <varlistentry xml:id="fetches-per-server">
<term><command>fetches-per-server</command></term>
<listitem>
<para>
</variablelist>
- </sect3>
+ </section>
- <sect3>
- <title>Periodic Task Intervals</title>
+ <section><info><title>Periodic Task Intervals</title></info>
+
<variablelist>
</variablelist>
- </sect3>
+ </section>
- <sect3 id="topology">
- <title>Topology</title>
+ <section xml:id="topology"><info><title>Topology</title></info>
+
<para>
All other things being equal, when the server chooses a name
is not implemented in <acronym>BIND</acronym> 9.
</simpara>
</note>
- </sect3>
+ </section>
- <sect3 id="the_sortlist_statement">
+ <section xml:id="the_sortlist_statement"><info><title>The <command>sortlist</command> Statement</title></info>
- <title>The <command>sortlist</command> Statement</title>
+
<para>
The response to a DNS query may consist of multiple resource
};
</programlisting>
- </sect3>
- <sect3 id="rrset_ordering">
- <title id="rrset_ordering_title">RRset Ordering</title>
+ </section>
+ <section xml:id="rrset_ordering"><info><title xml:id="rrset_ordering_title">RRset Ordering</title></info>
+
<para>
When multiple records are returned in an answer it may be
useful to configure the order of the records placed into the
</para>
<para>
If multiple <command>rrset-order</command> statements
- appear, they are not combined — the last one applies.
+ appear, they are not combined — the last one applies.
</para>
<para>
By default, all records are returned in random order.
the "configure" command line.
</simpara>
</note>
- </sect3>
+ </section>
- <sect3 id="tuning">
- <title>Tuning</title>
+ <section xml:id="tuning"><info><title>Tuning</title></info>
+
<variablelist>
<para>
Specifies the number of days into the future when
DNSSEC signatures automatically generated as a
- result of dynamic updates (<xref
- linkend="dynamic_update"/>) will expire. There
+ result of dynamic updates (<xref linkend="dynamic_update"/>) will expire. There
is an optional second field which specifies how
long before expiry that the signatures will be
regenerated. If not specified, the signatures will
</listitem>
</varlistentry>
- <varlistentry id="max-recursion-depth">
+ <varlistentry xml:id="max-recursion-depth">
<term><command>max-recursion-depth</command></term>
<listitem>
<para>
</listitem>
</varlistentry>
- <varlistentry id="max-recursion-queries">
+ <varlistentry xml:id="max-recursion-queries">
<term><command>max-recursion-queries</command></term>
<listitem>
<para>
</varlistentry>
</variablelist>
- </sect3>
+ </section>
- <sect3 id="builtin">
- <title>Built-in server information zones</title>
+ <section xml:id="builtin"><info><title>Built-in server information zones</title></info>
+
<para>
The server provides some helpful diagnostic information
</variablelist>
- </sect3>
+ </section>
- <sect3 id="empty">
- <title>Built-in Empty Zones</title>
+ <section xml:id="empty"><info><title>Built-in Empty Zones</title></info>
+
<para>
The <command>named</command> server has some built-in
empty zones (SOA and NS records only).
</listitem>
</varlistentry>
</variablelist>
- </sect3>
+ </section>
- <sect3 id="acache">
- <title>Additional Section Caching</title>
+ <section xml:id="acache"><info><title>Additional Section Caching</title></info>
+
<para>
The additional section cache, also called <command>acache</command>,
</variablelist>
- </sect3>
+ </section>
- <sect3>
- <title>Content Filtering</title>
+ <section><info><title>Content Filtering</title></info>
+
<para>
<acronym>BIND</acronym> 9 provides the ability to filter
out DNS responses from external DNS servers containing
to get access to an internal node of your local network
that couldn't be externally accessed otherwise.
See the paper available at
- <ulink url="http://portal.acm.org/citation.cfm?id=1315245.1315298">
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://portal.acm.org/citation.cfm?id=1315245.1315298">
http://portal.acm.org/citation.cfm?id=1315245.1315298
- </ulink>
+ </link>
for more details about the attacks.
</para>
Filtering out DNS records containing this address
spuriously can break such applications.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Response Policy Zone (RPZ) Rewriting</title>
+ <section><info><title>Response Policy Zone (RPZ) Rewriting</title></info>
+
<para>
<acronym>BIND</acronym> 9 includes a limited
mechanism to modify DNS responses for requests
<command>DISABLED</command> actions) must be chosen.
Triggers or the records that encode them are chosen for the
rewriting in the following order:
- <orderedlist>
+ <orderedlist inheritnum="ignore" continuation="restarts">
<listitem>Choose the triggered record in the zone that appears
first in the <command>response-policy</command> option.
</listitem>
turn off rewrite logging for a particular response policy
zone. By default, all rewrites are logged.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Response Rate Limiting</title>
+ <section><info><title>Response Rate Limiting</title></info>
+
<para>
Excessive almost identical UDP <emphasis>responses</emphasis>
can be controlled by configuring a
Responses that truncated by rate limits are included in
<command>RateSlipped</command> and <command>RespTruncated</command>.
</para>
- </sect3>
+ </section>
- <sect3 title="NXDOMAIN Redirection">
+ <section title="NXDOMAIN Redirection"><info/>
<para>
Named supports NXDOMAIN redirection via two methods:
<itemizedlist>
If both a redirect zone and a redirect namespace are configured,
the redirect zone is tried first.
</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2 id="server_statement_grammar">
- <title><command>server</command> Statement Grammar</title>
+ <section xml:id="server_statement_grammar"><info><title><command>server</command> Statement Grammar</title></info>
+
<programlisting><command>server</command> <replaceable>ip_addr[/prefixlen]</replaceable> {
<optional> bogus <replaceable>yes_or_no</replaceable> ; </optional>
};
</programlisting>
- </sect2>
+ </section>
- <sect2 id="server_statement_definition_and_usage">
- <title><command>server</command> Statement Definition and
- Usage</title>
+ <section xml:id="server_statement_definition_and_usage"><info><title><command>server</command> Statement Definition and
+ Usage</title></info>
+
<para>
The <command>server</command> statement defines
determine that COOKIE is not supported by the remote server
and not add a COOKIE EDNS option to requests.
</para>
- </sect2>
+ </section>
- <sect2 id="statschannels">
- <title><command>statistics-channels</command> Statement Grammar</title>
+ <section xml:id="statschannels"><info><title><command>statistics-channels</command> Statement Grammar</title></info>
+
<programlisting><command>statistics-channels</command> {
[ inet ( ip_addr | * ) [ port ip_port ]
[ inet ...; ]
};
</programlisting>
- </sect2>
+ </section>
- <sect2>
- <title><command>statistics-channels</command> Statement Definition and
- Usage</title>
+ <section><info><title><command>statistics-channels</command> Statement Definition and
+ Usage</title></info>
+
<para>
The <command>statistics-channels</command> statement
depending on the URI used to access them. For example, if
the statistics channel is configured to listen on 127.0.0.1
port 8888, then the statistics are accessible in XML format at
- <ulink url="http://127.0.0.1:8888/"
- >http://127.0.0.1:8888/</ulink> or
- <ulink url="http://127.0.0.1:8888/xml"
- >http://127.0.0.1:8888/xml</ulink>. A CSS file is
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/">http://127.0.0.1:8888/</link> or
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml">http://127.0.0.1:8888/xml</link>. A CSS file is
included which can format the XML statistics into tables
when viewed with a stylesheet-capable browser, and into
charts and graphs using the Google Charts API when using a
<para>
Applications that depend on a particular XML schema
can request
- <ulink url="http://127.0.0.1:8888/xml/v2"
- >http://127.0.0.1:8888/xml/v2</ulink> for version 2
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v2">http://127.0.0.1:8888/xml/v2</link> for version 2
of the statistics XML schema or
- <ulink url="http://127.0.0.1:8888/xml/v3"
- >http://127.0.0.1:8888/xml/v3</ulink> for version 3.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3">http://127.0.0.1:8888/xml/v3</link> for version 3.
If the requested schema is supported by the server, then
it will respond; if not, it will return a "page not found"
error.
<para>
Broken-out subsets of the statistics can be viewed at
- <ulink url="http://127.0.0.1:8888/xml/v3/status"
- >http://127.0.0.1:8888/xml/v3/status</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3/status">http://127.0.0.1:8888/xml/v3/status</link>
(server uptime and last reconfiguration time),
- <ulink url="http://127.0.0.1:8888/xml/v3/server"
- >http://127.0.0.1:8888/xml/v3/server</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3/server">http://127.0.0.1:8888/xml/v3/server</link>
(server and resolver statistics),
- <ulink url="http://127.0.0.1:8888/xml/v3/zones"
- >http://127.0.0.1:8888/xml/v3/zones</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3/zones">http://127.0.0.1:8888/xml/v3/zones</link>
(zone statistics),
- <ulink url="http://127.0.0.1:8888/xml/v3/net"
- >http://127.0.0.1:8888/xml/v3/net</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3/net">http://127.0.0.1:8888/xml/v3/net</link>
(network status and socket statistics),
- <ulink url="http://127.0.0.1:8888/xml/v3/mem"
- >http://127.0.0.1:8888/xml/v3/mem</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3/mem">http://127.0.0.1:8888/xml/v3/mem</link>
(memory manager statistics),
- <ulink url="http://127.0.0.1:8888/xml/v3/tasks"
- >http://127.0.0.1:8888/xml/v3/tasks</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3/tasks">http://127.0.0.1:8888/xml/v3/tasks</link>
(task manager statistics), and
- <ulink url="http://127.0.0.1:8888/xml/v3/traffic"
- >http://127.0.0.1:8888/xml/v3/traffic</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/xml/v3/traffic">http://127.0.0.1:8888/xml/v3/traffic</link>
(traffic sizes).
</para>
<para>
The full set of statistics can also be read in JSON format at
- <ulink url="http://127.0.0.1:8888/json"
- >http://127.0.0.1:8888/json</ulink>,
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json">http://127.0.0.1:8888/json</link>,
with the broken-out subsets at
- <ulink url="http://127.0.0.1:8888/json/v1/status"
- >http://127.0.0.1:8888/json/v1/status</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json/v1/status">http://127.0.0.1:8888/json/v1/status</link>
(server uptime and last reconfiguration time),
- <ulink url="http://127.0.0.1:8888/json/v1/server"
- >http://127.0.0.1:8888/json/v1/server</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json/v1/server">http://127.0.0.1:8888/json/v1/server</link>
(server and resolver statistics),
- <ulink url="http://127.0.0.1:8888/json/v1/zones"
- >http://127.0.0.1:8888/json/v1/zones</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json/v1/zones">http://127.0.0.1:8888/json/v1/zones</link>
(zone statistics),
- <ulink url="http://127.0.0.1:8888/json/v1/net"
- >http://127.0.0.1:8888/json/v1/net</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json/v1/net">http://127.0.0.1:8888/json/v1/net</link>
(network status and socket statistics),
- <ulink url="http://127.0.0.1:8888/json/v1/mem"
- >http://127.0.0.1:8888/json/v1/mem</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json/v1/mem">http://127.0.0.1:8888/json/v1/mem</link>
(memory manager statistics),
- <ulink url="http://127.0.0.1:8888/json/v1/tasks"
- >http://127.0.0.1:8888/json/v1/tasks</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json/v1/tasks">http://127.0.0.1:8888/json/v1/tasks</link>
(task manager statistics), and
- <ulink url="http://127.0.0.1:8888/json/v1/traffic"
- >http://127.0.0.1:8888/json/v1/traffic</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://127.0.0.1:8888/json/v1/traffic">http://127.0.0.1:8888/json/v1/traffic</link>
(traffic sizes).
</para>
- </sect2>
+ </section>
- <sect2 id="trusted-keys">
- <title><command>trusted-keys</command> Statement Grammar</title>
+ <section xml:id="trusted-keys"><info><title><command>trusted-keys</command> Statement Grammar</title></info>
+
<programlisting><command>trusted-keys</command> {
<replaceable>string</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ;
};
</programlisting>
- </sect2>
- <sect2>
- <title><command>trusted-keys</command> Statement Definition
- and Usage</title>
+ </section>
+ <section><info><title><command>trusted-keys</command> Statement Definition
+ and Usage</title></info>
+
<para>
The <command>trusted-keys</command> statement defines
- DNSSEC security roots. DNSSEC is described in <xref
- linkend="DNSSEC"/>. A security root is defined when the
+ DNSSEC security roots. DNSSEC is described in <xref linkend="DNSSEC"/>. A security root is defined when the
public key for a non-authoritative zone is known, but
cannot be securely obtained through DNS, either because
it is the DNS root zone or because its parent zone is
Validation below specified names can be temporarily disabled
by using <command>rndc nta</command>.
</para>
- </sect2>
+ </section>
- <sect2>
- <title><command>managed-keys</command> Statement Grammar</title>
+ <section><info><title><command>managed-keys</command> Statement Grammar</title></info>
+
<programlisting><command>managed-keys</command> {
<replaceable>name</replaceable> initial-key <replaceable>flags</replaceable> <replaceable>protocol</replaceable> <replaceable>algorithm</replaceable> <replaceable>key-data</replaceable> ;
};
</programlisting>
- </sect2>
- <sect2 id="managed-keys">
- <title><command>managed-keys</command> Statement Definition
- and Usage</title>
+ </section>
+ <section xml:id="managed-keys"><info><title><command>managed-keys</command> Statement Definition
+ and Usage</title></info>
+
<para>
The <command>managed-keys</command> statement, like
<command>trusted-keys</command>, defines DNSSEC
maintenance process is built into <command>named</command>,
and can be overridden from <command>bindkeys-file</command>.
</para>
- </sect2>
+ </section>
- <sect2 id="view_statement_grammar">
- <title><command>view</command> Statement Grammar</title>
+ <section xml:id="view_statement_grammar"><info><title><command>view</command> Statement Grammar</title></info>
+
<programlisting><command>view</command> <replaceable>view_name</replaceable>
<optional><replaceable>class</replaceable></optional> {
};
</programlisting>
- </sect2>
- <sect2>
- <title><command>view</command> Statement Definition and Usage</title>
+ </section>
+ <section><info><title><command>view</command> Statement Definition and Usage</title></info>
+
<para>
The <command>view</command> statement is a powerful
means that only recursive
requests from matching clients will match that view.
The order of the <command>view</command> statements is
- significant —
+ significant —
a client request will be resolved in the context of the first
<command>view</command> that it matches.
</para>
};
</programlisting>
- </sect2>
- <sect2 id="zone_statement_grammar">
- <title><command>zone</command>
- Statement Grammar</title>
+ </section>
+ <section xml:id="zone_statement_grammar"><info><title><command>zone</command>
+ Statement Grammar</title></info>
+
<programlisting><command>zone</command> <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
type master;
</programlisting>
- </sect2>
- <sect2>
- <title><command>zone</command> Statement Definition and Usage</title>
- <sect3>
- <title>Zone Types</title>
-
+ </section>
+ <section><info><title><command>zone</command> Statement Definition and Usage</title></info>
+
+ <section><info><title>Zone Types</title></info>
<para>
The <command>type</command> keyword is required
for the <command>zone</command> configuration unless
<varname>slave</varname>, <varname>static-stub</varname>,
and <varname>stub</varname>.
</para>
-
+
<informaltable colsep="0" rowsep="0">
<tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table">
<!--colspec colname="1" colnum="1" colsep="0" colwidth="1.108in"/-->
</tbody>
</tgroup>
</informaltable>
- </sect3>
+ </section>
- <sect3>
- <title>Class</title>
+ <section><info><title>Class</title></info>
+
<para>
The zone's name may optionally be followed by a class. If
a class is not specified, class <literal>IN</literal> (for <varname>Internet</varname>),
Another MIT development is Chaosnet, a LAN protocol created
in the mid-1970s. Zone data for it can be specified with the <literal>CHAOS</literal> class.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Zone Options</title>
+ <section><info><title>Zone Options</title></info>
+
<variablelist>
</variablelist>
- </sect3>
- <sect3 id="dynamic_update_policies">
- <title>Dynamic Update Policies</title>
+ </section>
+ <section xml:id="dynamic_update_policies"><info><title>Dynamic Update Policies</title></info>
+
<para><acronym>BIND</acronym> 9 supports two alternative
methods of granting clients the right to perform
dynamic updates to a zone, configured by the
all records associated with a name, the rules are
checked for each existing record type.
</para>
- </sect3>
+ </section>
- <sect3>
- <title>Multiple views</title>
+ <section><info><title>Multiple views</title></info>
+
<para>
When multiple views are in use, a zone may be
referenced by more than one of them. Often, the views
An <command>in-view</command> zone is not intended to reference
a <command>forward</command> zone.
</para>
- </sect3>
+ </section>
- </sect2>
- </sect1>
- <sect1>
- <title>Zone File</title>
- <sect2 id="types_of_resource_records_and_when_to_use_them">
- <title>Types of Resource Records and When to Use Them</title>
+ </section>
+ </section>
+ <section><info><title>Zone File</title></info>
+
+ <section xml:id="types_of_resource_records_and_when_to_use_them"><info><title>Types of Resource Records and When to Use Them</title></info>
+
<para>
This section, largely borrowed from RFC 1034, describes the
concept of a Resource Record (RR) and explains when each is used.
identified
and implemented in the DNS. These are also included.
</para>
- <sect3>
- <title>Resource Records</title>
+ <section><info><title>Resource Records</title></info>
+
<para>
A domain name identifies a node. Each node has a set of
frequently
used as "pointers" to other data in the DNS.
</para>
- </sect3>
- <sect3>
- <title>Textual expression of RRs</title>
+ </section>
+ <section><info><title>Textual expression of RRs</title></info>
+
<para>
RRs are represented in binary form in the packets of the DNS
protocol, and are usually represented in highly encoded form
This example shows two addresses for
<literal>XX.LCS.MIT.EDU</literal>, each of a different class.
</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2>
- <title>Discussion of MX Records</title>
+ <section><info><title>Discussion of MX Records</title></info>
+
<para>
As described above, domain servers store information as a
chosen randomly. If no servers at a given priority are responding,
the mail transport agent will fall back to the next largest
priority.
- Priority numbers do not have any absolute meaning — they are
+ Priority numbers do not have any absolute meaning — they are
relevant
only respective to other MX records for that domain name. The
domain
name given is the machine to which the mail will be delivered.
It <emphasis>must</emphasis> have an associated address record
- (A or AAAA) — CNAME is not sufficient.
+ (A or AAAA) — CNAME is not sufficient.
</para>
<para>
For a given domain, if there is both a CNAME record and an
any order), and if neither of those succeed, delivery to <literal>mail.backup.org</literal> will
be attempted.
</para>
- </sect2>
- <sect2 id="Setting_TTLs">
- <title>Setting TTLs</title>
+ </section>
+ <section xml:id="Setting_TTLs"><info><title>Setting TTLs</title></info>
+
<para>
The time-to-live of the RR field is a 32-bit integer represented
in units of seconds, and is primarily used by resolvers when they
All of these TTLs default to units of seconds, though units
can be explicitly specified, for example, <literal>1h30m</literal>.
</para>
- </sect2>
- <sect2>
- <title>Inverse Mapping in IPv4</title>
+ </section>
+ <section><info><title>Inverse Mapping in IPv4</title></info>
+
<para>
Reverse name resolution (that is, translation from IP address
to name) is achieved by means of the <emphasis>in-addr.arpa</emphasis> domain
<note>
<para>
The <command>$ORIGIN</command> lines in the examples
- are for providing context to the examples only — they do not
+ are for providing context to the examples only — they do not
necessarily
appear in the actual usage. They are only used here to indicate
that the example is relative to the listed origin.
</para>
</note>
- </sect2>
- <sect2>
- <title>Other Zone File Directives</title>
+ </section>
+ <section><info><title>Other Zone File Directives</title></info>
+
<para>
The Master File Format was initially defined in RFC 1035 and
has subsequently been extended. While the Master File Format
Master File Directives include <command>$ORIGIN</command>, <command>$INCLUDE</command>,
and <command>$TTL.</command>
</para>
- <sect3>
- <title>The <command>@</command> (at-sign)</title>
+ <section><info><title>The <command>@</command> (at-sign)</title></info>
+
<para>
When used in the label (or name) field, the asperand or
at-sign (@) symbol represents the current origin.
<<varname>zone_name</varname>> (followed by
trailing dot).
</para>
- </sect3>
- <sect3>
- <title>The <command>$ORIGIN</command> Directive</title>
+ </section>
+ <section><info><title>The <command>$ORIGIN</command> Directive</title></info>
+
<para>
Syntax: <command>$ORIGIN</command>
<replaceable>domain-name</replaceable>
WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
</programlisting>
- </sect3>
- <sect3>
- <title>The <command>$INCLUDE</command> Directive</title>
+ </section>
+ <section><info><title>The <command>$INCLUDE</command> Directive</title></info>
+
<para>
Syntax: <command>$INCLUDE</command>
<replaceable>filename</replaceable>
feature, or both.
</para>
</note>
- </sect3>
- <sect3>
- <title>The <command>$TTL</command> Directive</title>
+ </section>
+ <section><info><title>The <command>$TTL</command> Directive</title></info>
+
<para>
Syntax: <command>$TTL</command>
<replaceable>default-ttl</replaceable>
<para><command>$TTL</command>
is defined in RFC 2308.
</para>
- </sect3>
- </sect2>
- <sect2>
- <title><acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive</title>
+ </section>
+ </section>
+ <section><info><title><acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive</title></info>
+
<para>
Syntax: <command>$GENERATE</command>
<replaceable>range</replaceable>
<para>
BIND 8 does not support the optional TTL and CLASS fields.
</para>
- </sect2>
+ </section>
- <sect2 id="zonefile_format">
- <title>Additional File Formats</title>
+ <section xml:id="zonefile_format"><info><title>Additional File Formats</title></info>
+
<para>
In addition to the standard textual format, BIND 9
supports the ability to read or dump to zone files in
portable backup of such a file, conversion to
<constant>text</constant> format is recommended.
</para>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1 id="statistics">
- <title>BIND9 Statistics</title>
+ <section xml:id="statistics"><info><title>BIND9 Statistics</title></info>
+
<para>
<acronym>BIND</acronym> 9 maintains lots of statistics
information and provides several interfaces for users to
(see <xref linkend="statschannels"/>.)
</para>
- <sect3 id="statsfile">
- <title>The Statistics File</title>
+ <section xml:id="statsfile"><info><title>The Statistics File</title></info>
+
<para>
The text format statistics dump begins with a line, like:
</para>
<para>
<command>--- Statistics Dump --- (973798949)</command>
</para>
- </sect3>
+ </section>
- <sect2 id="statistics_counters">
- <title>Statistics Counters</title>
+ <section xml:id="statistics_counters"><info><title>Statistics Counters</title></info>
+
<para>
The following tables summarize statistics counters that
<acronym>BIND</acronym> 9 provides.
<acronym>BIND</acronym> 8 statistics, if applicable.
</para>
- <sect3>
- <title>Name Server Statistics Counters</title>
+ <section><info><title>Name Server Statistics Counters</title></info>
+
<informaltable colsep="0" rowsep="0">
<tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table">
<para><command>ReqEdns0</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ReqBadEDNSVer</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ReqTSIG</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ReqSIG0</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ReqBadSIG</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>RespTruncated</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>RespEDNS0</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>RespTSIG</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>RespSIG0</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QrySuccess</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryAuthAns</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryReferral</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryNxrrset</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryDropped</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryFailure</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryNXRedir</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryNXRedirRLookup</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>XfrReqDone</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>UpdateReqFwd</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>UpdateRespFwd</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>UpdateFwdFail</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>UpdateDone</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>UpdateFail</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>UpdateBadPrereq</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>RateDropped</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>RateSlipped</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>RPZRewrites</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
</tbody>
</tgroup>
</informaltable>
- </sect3>
+ </section>
- <sect3>
- <title>Zone Maintenance Statistics Counters</title>
+ <section><info><title>Zone Maintenance Statistics Counters</title></info>
+
<informaltable colsep="0" rowsep="0">
<tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
</tbody>
</tgroup>
</informaltable>
- </sect3>
+ </section>
- <sect3>
- <title>Resolver Statistics Counters</title>
+ <section><info><title>Resolver Statistics Counters</title></info>
+
<informaltable colsep="0" rowsep="0">
<tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table">
<para><command>EDNS0Fail</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>Truncated</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QueryAbort</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QuerySockFail</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QueryTimeout</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>GlueFetchv4Fail</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>GlueFetchv6Fail</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ValAttempt</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ValOk</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ValNegOk</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>ValFail</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
<para><command>QryRTTnn</command></para>
</entry>
<entry colname="2">
- <para><command></command></para>
+ <para><command/></para>
</entry>
<entry colname="3">
<para>
</tgroup>
</informaltable>
- </sect3>
+ </section>
- <sect3>
- <title>Socket I/O Statistics Counters</title>
+ <section><info><title>Socket I/O Statistics Counters</title></info>
+
<para>
Socket I/O statistics counters are defined per socket
</tbody>
</tgroup>
</informaltable>
- </sect3>
- <sect3>
- <title>Compatibility with <emphasis>BIND</emphasis> 8 Counters</title>
+ </section>
+ <section><info><title>Compatibility with <emphasis>BIND</emphasis> 8 Counters</title></info>
+
<para>
Most statistics counters that were available
in <command>BIND</command> 8 are also supported in
</listitem>
</varlistentry>
</variablelist>
- </sect3>
- </sect2>
- </sect1>
+ </section>
+ </section>
+ </section>
</chapter>
- <chapter id="Bv9ARM.ch07">
- <title><acronym>BIND</acronym> 9 Security Considerations</title>
- <sect1 id="Access_Control_Lists">
- <title>Access Control Lists</title>
+ <chapter xml:id="Bv9ARM.ch07"><info><title><acronym>BIND</acronym> 9 Security Considerations</title></info>
+
+ <section xml:id="Access_Control_Lists"><info><title>Access Control Lists</title></info>
+
<para>
Access Control Lists (ACLs) are address match lists that
you can set up and nickname for future use in
will only matches when <emphasis>both</emphasis> conditions
are true.
</para>
- </sect1>
+ </section>
- <sect1>
- <title><command>Chroot</command> and <command>Setuid</command></title>
+ <section><info><title><command>Chroot</command> and <command>Setuid</command></title></info>
+
<para>
On UNIX servers, it is possible to run <acronym>BIND</acronym>
in a <emphasis>chrooted</emphasis> environment (using
<userinput>/usr/local/sbin/named -u 202 -t /var/named</userinput>
</para>
- <sect2>
- <title>The <command>chroot</command> Environment</title>
+ <section><info><title>The <command>chroot</command> Environment</title></info>
+
<para>
In order for a <command>chroot</command> environment
<filename>/dev/log</filename>, and
<filename>/etc/localtime</filename>.
</para>
- </sect2>
+ </section>
- <sect2>
- <title>Using the <command>setuid</command> Function</title>
+ <section><info><title>Using the <command>setuid</command> Function</title></info>
+
<para>
Prior to running the <command>named</command> daemon,
unprivileged user, it will not be able to bind to new restricted
ports if the server is reloaded.
</note>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1 id="dynamic_update_security">
- <title>Dynamic Update Security</title>
+ <section xml:id="dynamic_update_security"><info><title>Dynamic Update Security</title></info>
+
<para>
Access to the dynamic
all.
</para>
- </sect1>
+ </section>
</chapter>
- <chapter id="Bv9ARM.ch08">
- <title>Troubleshooting</title>
- <sect1>
- <title>Common Problems</title>
- <sect2>
- <title>It's not working; how can I figure out what's wrong?</title>
+ <chapter xml:id="Bv9ARM.ch08"><info><title>Troubleshooting</title></info>
+
+ <section><info><title>Common Problems</title></info>
+
+ <section><info><title>It's not working; how can I figure out what's wrong?</title></info>
+
<para>
The best solution to solving installation and
what went wrong and how to fix the problem.
</para>
- </sect2>
- </sect1>
- <sect1>
- <title>Incrementing and Changing the Serial Number</title>
+ </section>
+ </section>
+ <section><info><title>Incrementing and Changing the Serial Number</title></info>
+
<para>
- Zone serial numbers are just numbers — they aren't
+ Zone serial numbers are just numbers — they aren't
date related. A lot of people set them to a number that
represents a date, usually of the form YYYYMMDDRR.
Occasionally they will make a mistake and set them to a
it to be, and reload the zone again.
</para>
- </sect1>
- <sect1>
- <title>Where Can I Get Help?</title>
+ </section>
+ <section><info><title>Where Can I Get Help?</title></info>
+
<para>
The Internet Systems Consortium
<para>
To discuss arrangements for support, contact
- <ulink url="mailto:info@isc.org">info@isc.org</ulink> or visit the
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="mailto:info@isc.org">info@isc.org</link> or visit the
<acronym>ISC</acronym> web page at
- <ulink url="http://www.isc.org/services/support/"
- >http://www.isc.org/services/support/</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.isc.org/services/support/">http://www.isc.org/services/support/</link>
to read more.
</para>
- </sect1>
+ </section>
</chapter>
- <appendix id="Bv9ARM.ch09">
- <title>Release Notes</title>
- <xi:include href="notes.xml"/>
+ <appendix xml:id="Bv9ARM.ch09"><info><title>Release Notes</title></info>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="notes.xml"/>
</appendix>
- <appendix id="Bv9ARM.ch10">
- <title>A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym></title>
- <para id="historical_dns_information">
+ <appendix xml:id="Bv9ARM.ch10"><info><title>A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym></title></info>
+
+ <section xml:id="dns_history"><info><title>DNS</title></info>
+ <para>
Although the "official" beginning of the Domain Name
System occurred in 1984 with the publication of RFC 920, the
core of the new system was described in 1983 in RFCs 882 and
Administration
(DARPA).
</para>
+ </section>
+
+ <section xml:id="bind_history"><info><title>BIND</title></info>
<para>
Versions of <acronym>BIND</acronym> through
4.8.3 were maintained by the Computer
during that time: Doug Kingston, Craig Partridge, Smoot
Carl-Mitchell,
Mike Muuss, Jim Bloom and Mike Schwartz. <acronym>BIND</acronym> maintenance was subsequently
- handled by Mike Karels and Øivind Kure.
+ handled by Mike Karels and Øivind Kure.
</para>
<para>
<acronym>BIND</acronym> versions 4.9 and 4.9.1 were
of several corporations, and by the tireless work efforts of
numerous individuals.
</para>
+ </section>
</appendix>
- <appendix id="Bv9ARM.ch11">
- <title>General <acronym>DNS</acronym> Reference Information</title>
- <sect1 id="ipv6addresses">
- <title>IPv6 addresses (AAAA)</title>
+ <appendix xml:id="Bv9ARM.ch11"><info><title>General <acronym>DNS</acronym> Reference Information</title></info>
+
+ <section xml:id="ipv6addresses"><info><title>IPv6 addresses (AAAA)</title></info>
+
<para>
IPv6 addresses are 128-bit identifiers for interfaces and
sets of interfaces which were introduced in the <acronym>DNS</acronym> to facilitate
string
of zeros that can fit, and can be used only once in an address.
</para>
- </sect1>
- <sect1 id="bibliography">
- <title>Bibliography (and Suggested Reading)</title>
- <sect2 id="rfcs">
- <title>Request for Comments (RFCs)</title>
+ </section>
+ <section xml:id="bibliography"><info><title>Bibliography (and Suggested Reading)</title></info>
+
+ <section xml:id="rfcs"><info><title>Request for Comments (RFCs)</title></info>
+
<para>
Specification documents for the Internet protocol suite, including
the <acronym>DNS</acronym>, are published as part of
Engineering Steering Group (IESG). RFCs can be obtained online via FTP at:
</para>
<para>
- <ulink url="ftp://www.isi.edu/in-notes/">
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="ftp://www.isi.edu/in-notes/">
ftp://www.isi.edu/in-notes/RFC<replaceable>xxxx</replaceable>.txt
- </ulink>
+ </link>
</para>
<para>
(where <replaceable>xxxx</replaceable> is
the number of the RFC). RFCs are also available via the Web at:
</para>
<para>
- <ulink url="http://www.ietf.org/rfc/"
- >http://www.ietf.org/rfc/</ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.ietf.org/rfc/">http://www.ietf.org/rfc/</link>.
</para>
<bibliography>
- <bibliodiv>
+ <bibliodiv><info><title>Standards</title></info>
<!-- one of (BIBLIOENTRY BIBLIOMIXED) -->
- <title>Standards</title>
+
<biblioentry>
<abbrev>RFC974</abbrev>
- <author>
- <surname>Partridge</surname>
- <firstname>C.</firstname>
- </author>
- <title>Mail Routing and the Domain System</title>
+ <author><personname><surname>Partridge</surname><firstname>C.</firstname></personname></author>
+ <citetitle>Mail Routing and the Domain System</citetitle>
<pubdate>January 1986</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1034</abbrev>
- <author>
- <surname>Mockapetris</surname>
- <firstname>P.V.</firstname>
- </author>
- <title>Domain Names — Concepts and Facilities</title>
+ <author><personname><surname>Mockapetris</surname><firstname>P.V.</firstname></personname></author>
+ <citetitle>Domain Names — Concepts and Facilities</citetitle>
<pubdate>November 1987</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1035</abbrev>
- <author>
- <surname>Mockapetris</surname>
- <firstname>P. V.</firstname>
- </author> <title>Domain Names — Implementation and
- Specification</title>
+ <author><personname><surname>Mockapetris</surname><firstname>P. V.</firstname></personname></author> <citetitle>Domain Names — Implementation and
+ Specification</citetitle>
<pubdate>November 1987</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv id="proposed_standards" xreflabel="Proposed Standards">
+ <bibliodiv xml:id="proposed_standards" xreflabel="Proposed Standards"><info><title>Proposed Standards</title></info>
- <title>Proposed Standards</title>
+
<!-- one of (BIBLIOENTRY BIBLIOMIXED) -->
<biblioentry>
<abbrev>RFC2181</abbrev>
- <author>
- <surname>Elz</surname>
- <firstname>R., R. Bush</firstname>
- </author>
- <title>Clarifications to the <acronym>DNS</acronym>
- Specification</title>
+ <author><personname><surname>Elz</surname><firstname>R., R. Bush</firstname></personname></author>
+ <citetitle>Clarifications to the <acronym>DNS</acronym>
+ Specification</citetitle>
<pubdate>July 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2308</abbrev>
- <author>
- <surname>Andrews</surname>
- <firstname>M.</firstname>
- </author>
- <title>Negative Caching of <acronym>DNS</acronym>
- Queries</title>
+ <author><personname><surname>Andrews</surname><firstname>M.</firstname></personname></author>
+ <citetitle>Negative Caching of <acronym>DNS</acronym>
+ Queries</citetitle>
<pubdate>March 1998</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1995</abbrev>
- <author>
- <surname>Ohta</surname>
- <firstname>M.</firstname>
- </author>
- <title>Incremental Zone Transfer in <acronym>DNS</acronym></title>
+ <author><personname><surname>Ohta</surname><firstname>M.</firstname></personname></author>
+ <citetitle>Incremental Zone Transfer in <acronym>DNS</acronym></citetitle>
<pubdate>August 1996</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1996</abbrev>
- <author>
- <surname>Vixie</surname>
- <firstname>P.</firstname>
- </author>
- <title>A Mechanism for Prompt Notification of Zone Changes</title>
+ <author><personname><surname>Vixie</surname><firstname>P.</firstname></personname></author>
+ <citetitle>A Mechanism for Prompt Notification of Zone Changes</citetitle>
<pubdate>August 1996</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2136</abbrev>
<authorgroup>
- <author>
- <surname>Vixie</surname>
- <firstname>P.</firstname>
- </author>
- <author>
- <firstname>S.</firstname>
- <surname>Thomson</surname>
- </author>
- <author>
- <firstname>Y.</firstname>
- <surname>Rekhter</surname>
- </author>
- <author>
- <firstname>J.</firstname>
- <surname>Bound</surname>
- </author>
+ <author><personname><surname>Vixie</surname><firstname>P.</firstname></personname></author>
+ <author><personname><firstname>S.</firstname><surname>Thomson</surname></personname></author>
+ <author><personname><firstname>Y.</firstname><surname>Rekhter</surname></personname></author>
+ <author><personname><firstname>J.</firstname><surname>Bound</surname></personname></author>
</authorgroup>
- <title>Dynamic Updates in the Domain Name System</title>
+ <citetitle>Dynamic Updates in the Domain Name System</citetitle>
<pubdate>April 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2671</abbrev>
<authorgroup>
- <author>
- <firstname>P.</firstname>
- <surname>Vixie</surname>
- </author>
+ <author><personname><firstname>P.</firstname><surname>Vixie</surname></personname></author>
</authorgroup>
- <title>Extension Mechanisms for DNS (EDNS0)</title>
+ <citetitle>Extension Mechanisms for DNS (EDNS0)</citetitle>
<pubdate>August 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2672</abbrev>
<authorgroup>
- <author>
- <firstname>M.</firstname>
- <surname>Crawford</surname>
- </author>
+ <author><personname><firstname>M.</firstname><surname>Crawford</surname></personname></author>
</authorgroup>
- <title>Non-Terminal DNS Name Redirection</title>
+ <citetitle>Non-Terminal DNS Name Redirection</citetitle>
<pubdate>August 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2845</abbrev>
<authorgroup>
- <author>
- <surname>Vixie</surname>
- <firstname>P.</firstname>
- </author>
- <author>
- <firstname>O.</firstname>
- <surname>Gudmundsson</surname>
- </author>
- <author>
- <firstname>D.</firstname>
- <surname>Eastlake</surname>
- <lineage>3rd</lineage>
- </author>
- <author>
- <firstname>B.</firstname>
- <surname>Wellington</surname>
- </author>
+ <author><personname><surname>Vixie</surname><firstname>P.</firstname></personname></author>
+ <author><personname><firstname>O.</firstname><surname>Gudmundsson</surname></personname></author>
+ <author><personname><firstname>D.</firstname><surname>Eastlake</surname><lineage>3rd</lineage></personname></author>
+ <author><personname><firstname>B.</firstname><surname>Wellington</surname></personname></author>
</authorgroup>
- <title>Secret Key Transaction Authentication for <acronym>DNS</acronym> (TSIG)</title>
+ <citetitle>Secret Key Transaction Authentication for <acronym>DNS</acronym> (TSIG)</citetitle>
<pubdate>May 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2930</abbrev>
<authorgroup>
- <author>
- <firstname>D.</firstname>
- <surname>Eastlake</surname>
- <lineage>3rd</lineage>
- </author>
+ <author><personname><firstname>D.</firstname><surname>Eastlake</surname><lineage>3rd</lineage></personname></author>
</authorgroup>
- <title>Secret Key Establishment for DNS (TKEY RR)</title>
+ <citetitle>Secret Key Establishment for DNS (TKEY RR)</citetitle>
<pubdate>September 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2931</abbrev>
<authorgroup>
- <author>
- <firstname>D.</firstname>
- <surname>Eastlake</surname>
- <lineage>3rd</lineage>
- </author>
+ <author><personname><firstname>D.</firstname><surname>Eastlake</surname><lineage>3rd</lineage></personname></author>
</authorgroup>
- <title>DNS Request and Transaction Signatures (SIG(0)s)</title>
+ <citetitle>DNS Request and Transaction Signatures (SIG(0)s)</citetitle>
<pubdate>September 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3007</abbrev>
<authorgroup>
- <author>
- <firstname>B.</firstname>
- <surname>Wellington</surname>
- </author>
+ <author><personname><firstname>B.</firstname><surname>Wellington</surname></personname></author>
</authorgroup>
- <title>Secure Domain Name System (DNS) Dynamic Update</title>
+ <citetitle>Secure Domain Name System (DNS) Dynamic Update</citetitle>
<pubdate>November 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3645</abbrev>
<authorgroup>
- <author>
- <firstname>S.</firstname>
- <surname>Kwan</surname>
- </author>
- <author>
- <firstname>P.</firstname>
- <surname>Garg</surname>
- </author>
- <author>
- <firstname>J.</firstname>
- <surname>Gilroy</surname>
- </author>
- <author>
- <firstname>L.</firstname>
- <surname>Esibov</surname>
- </author>
- <author>
- <firstname>J.</firstname>
- <surname>Westhead</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Hall</surname>
- </author>
+ <author><personname><firstname>S.</firstname><surname>Kwan</surname></personname></author>
+ <author><personname><firstname>P.</firstname><surname>Garg</surname></personname></author>
+ <author><personname><firstname>J.</firstname><surname>Gilroy</surname></personname></author>
+ <author><personname><firstname>L.</firstname><surname>Esibov</surname></personname></author>
+ <author><personname><firstname>J.</firstname><surname>Westhead</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Hall</surname></personname></author>
</authorgroup>
- <title>Generic Security Service Algorithm for Secret
+ <citetitle>Generic Security Service Algorithm for Secret
Key Transaction Authentication for DNS
- (GSS-TSIG)</title>
+ (GSS-TSIG)</citetitle>
<pubdate>October 2003</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title><acronym>DNS</acronym> Security Proposed Standards</title>
+ <bibliodiv><info><title><acronym>DNS</acronym> Security Proposed Standards</title></info>
+
<biblioentry>
<abbrev>RFC3225</abbrev>
<authorgroup>
- <author>
- <firstname>D.</firstname>
- <surname>Conrad</surname>
- </author>
+ <author><personname><firstname>D.</firstname><surname>Conrad</surname></personname></author>
</authorgroup>
- <title>Indicating Resolver Support of DNSSEC</title>
+ <citetitle>Indicating Resolver Support of DNSSEC</citetitle>
<pubdate>December 2001</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3833</abbrev>
<authorgroup>
- <author>
- <firstname>D.</firstname>
- <surname>Atkins</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Austein</surname>
- </author>
+ <author><personname><firstname>D.</firstname><surname>Atkins</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Austein</surname></personname></author>
</authorgroup>
- <title>Threat Analysis of the Domain Name System (DNS)</title>
+ <citetitle>Threat Analysis of the Domain Name System (DNS)</citetitle>
<pubdate>August 2004</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC4033</abbrev>
<authorgroup>
- <author>
- <firstname>R.</firstname>
- <surname>Arends</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Austein</surname>
- </author>
- <author>
- <firstname>M.</firstname>
- <surname>Larson</surname>
- </author>
- <author>
- <firstname>D.</firstname>
- <surname>Massey</surname>
- </author>
- <author>
- <firstname>S.</firstname>
- <surname>Rose</surname>
- </author>
+ <author><personname><firstname>R.</firstname><surname>Arends</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Austein</surname></personname></author>
+ <author><personname><firstname>M.</firstname><surname>Larson</surname></personname></author>
+ <author><personname><firstname>D.</firstname><surname>Massey</surname></personname></author>
+ <author><personname><firstname>S.</firstname><surname>Rose</surname></personname></author>
</authorgroup>
- <title>DNS Security Introduction and Requirements</title>
+ <citetitle>DNS Security Introduction and Requirements</citetitle>
<pubdate>March 2005</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC4034</abbrev>
<authorgroup>
- <author>
- <firstname>R.</firstname>
- <surname>Arends</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Austein</surname>
- </author>
- <author>
- <firstname>M.</firstname>
- <surname>Larson</surname>
- </author>
- <author>
- <firstname>D.</firstname>
- <surname>Massey</surname>
- </author>
- <author>
- <firstname>S.</firstname>
- <surname>Rose</surname>
- </author>
+ <author><personname><firstname>R.</firstname><surname>Arends</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Austein</surname></personname></author>
+ <author><personname><firstname>M.</firstname><surname>Larson</surname></personname></author>
+ <author><personname><firstname>D.</firstname><surname>Massey</surname></personname></author>
+ <author><personname><firstname>S.</firstname><surname>Rose</surname></personname></author>
</authorgroup>
- <title>Resource Records for the DNS Security Extensions</title>
+ <citetitle>Resource Records for the DNS Security Extensions</citetitle>
<pubdate>March 2005</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC4035</abbrev>
<authorgroup>
- <author>
- <firstname>R.</firstname>
- <surname>Arends</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Austein</surname>
- </author>
- <author>
- <firstname>M.</firstname>
- <surname>Larson</surname>
- </author>
- <author>
- <firstname>D.</firstname>
- <surname>Massey</surname>
- </author>
- <author>
- <firstname>S.</firstname>
- <surname>Rose</surname>
- </author>
+ <author><personname><firstname>R.</firstname><surname>Arends</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Austein</surname></personname></author>
+ <author><personname><firstname>M.</firstname><surname>Larson</surname></personname></author>
+ <author><personname><firstname>D.</firstname><surname>Massey</surname></personname></author>
+ <author><personname><firstname>S.</firstname><surname>Rose</surname></personname></author>
</authorgroup>
- <title>Protocol Modifications for the DNS
- Security Extensions</title>
+ <citetitle>Protocol Modifications for the DNS
+ Security Extensions</citetitle>
<pubdate>March 2005</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title>Other Important RFCs About <acronym>DNS</acronym>
- Implementation</title>
+ <bibliodiv><info><title>Other Important RFCs About <acronym>DNS</acronym>
+ Implementation</title></info>
+
<biblioentry>
<abbrev>RFC1535</abbrev>
- <author>
- <surname>Gavron</surname>
- <firstname>E.</firstname>
- </author>
- <title>A Security Problem and Proposed Correction With Widely
- Deployed <acronym>DNS</acronym> Software</title>
+ <author><personname><surname>Gavron</surname><firstname>E.</firstname></personname></author>
+ <citetitle>A Security Problem and Proposed Correction With Widely
+ Deployed <acronym>DNS</acronym> Software</citetitle>
<pubdate>October 1993</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1536</abbrev>
<authorgroup>
- <author>
- <surname>Kumar</surname>
- <firstname>A.</firstname>
- </author>
- <author>
- <firstname>J.</firstname>
- <surname>Postel</surname>
- </author>
- <author>
- <firstname>C.</firstname>
- <surname>Neuman</surname>
- </author>
- <author>
- <firstname>P.</firstname>
- <surname>Danzig</surname>
- </author>
- <author>
- <firstname>S.</firstname>
- <surname>Miller</surname>
- </author>
+ <author><personname><surname>Kumar</surname><firstname>A.</firstname></personname></author>
+ <author><personname><firstname>J.</firstname><surname>Postel</surname></personname></author>
+ <author><personname><firstname>C.</firstname><surname>Neuman</surname></personname></author>
+ <author><personname><firstname>P.</firstname><surname>Danzig</surname></personname></author>
+ <author><personname><firstname>S.</firstname><surname>Miller</surname></personname></author>
</authorgroup>
- <title>Common <acronym>DNS</acronym> Implementation
- Errors and Suggested Fixes</title>
+ <
citetitle>Common <acronym>DNS</acronym> Implementation
+ Errors and Suggested Fixes</citetitle>
<pubdate>October 1993</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1982</abbrev>
<authorgroup>
- <author>
- <surname>Elz</surname>
- <firstname>R.</firstname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Bush</surname>
- </author>
+ <author><personname><surname>Elz</surname><firstname>R.</firstname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Bush</surname></personname></author>
</authorgroup>
- <title>Serial Number Arithmetic</title>
+ <citetitle>Serial Number Arithmetic</citetitle>
<pubdate>August 1996</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC4074</abbrev>
<authorgroup>
- <author>
- <surname>Morishita</surname>
- <firstname>Y.</firstname>
- </author>
- <author>
- <firstname>T.</firstname>
- <surname>Jinmei</surname>
- </author>
+ <author><personname><surname>Morishita</surname><firstname>Y.</firstname></personname></author>
+ <author><personname><firstname>T.</firstname><surname>Jinmei</surname></personname></author>
</authorgroup>
- <title>Common Misbehaviour Against <acronym>DNS</acronym>
- Queries for IPv6 Addresses</title>
+ <
citetitle>Common Misbehaviour Against <acronym>DNS</acronym>
+ Queries for IPv6 Addresses</citetitle>
<pubdate>May 2005</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title>Resource Record Types</title>
+ <bibliodiv><info><title>Resource Record Types</title></info>
+
<biblioentry>
<abbrev>RFC1183</abbrev>
<authorgroup>
- <author>
- <surname>Everhart</surname>
- <firstname>C.F.</firstname>
- </author>
- <author>
- <firstname>L. A.</firstname>
- <surname>Mamakos</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Ullmann</surname>
- </author>
- <author>
- <firstname>P.</firstname>
- <surname>Mockapetris</surname>
- </author>
+ <author><personname><surname>Everhart</surname><firstname>C.F.</firstname></personname></author>
+ <author><personname><firstname>L. A.</firstname><surname>Mamakos</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Ullmann</surname></personname></author>
+ <author><personname><firstname>P.</firstname><surname>Mockapetris</surname></personname></author>
</authorgroup>
- <title>New <acronym>DNS</acronym> RR Definitions</title>
+ <citetitle>New <acronym>DNS</acronym> RR Definitions</citetitle>
<pubdate>October 1990</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1706</abbrev>
<authorgroup>
- <author>
- <surname>Manning</surname>
- <firstname>B.</firstname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Colella</surname>
- </author>
+ <author><personname><surname>Manning</surname><firstname>B.</firstname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Colella</surname></personname></author>
</authorgroup>
- <title><acronym>DNS</acronym> NSAP Resource Records</title>
+ <citetitle><acronym>DNS</acronym> NSAP Resource Records</citetitle>
<pubdate>October 1994</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2168</abbrev>
<authorgroup>
- <author>
- <surname>Daniel</surname>
- <firstname>R.</firstname>
- </author>
- <author>
- <firstname>M.</firstname>
- <surname>Mealling</surname>
- </author>
+ <author><personname><surname>Daniel</surname><firstname>R.</firstname></personname></author>
+ <author><personname><firstname>M.</firstname><surname>Mealling</surname></personname></author>
</authorgroup>
- <title>Resolution of Uniform Resource Identifiers using
- the Domain Name System</title>
+ <citetitle>Resolution of Uniform Resource Identifiers using
+ the Domain Name System</citetitle>
<pubdate>June 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1876</abbrev>
<authorgroup>
- <author>
- <surname>Davis</surname>
- <firstname>C.</firstname>
- </author>
- <author>
- <firstname>P.</firstname>
- <surname>Vixie</surname>
- </author>
- <author>
- <firstname>T.</firstname>
- <firstname>Goodwin</firstname>
- </author>
- <author>
- <firstname>I.</firstname>
- <surname>Dickinson</surname>
- </author>
+ <author><personname><surname>Davis</surname><firstname>C.</firstname></personname></author>
+ <author><personname><firstname>P.</firstname><surname>Vixie</surname></personname></author>
+ <author><personname><firstname>T.</firstname><firstname>Goodwin</firstname></personname></author>
+ <author><personname><firstname>I.</firstname><surname>Dickinson</surname></personname></author>
</authorgroup>
- <title>A Means for Expressing Location Information in the
+ <citetitle>A Means for Expressing Location Information in the
Domain
- Name System</title>
+ Name System</citetitle>
<pubdate>January 1996</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2052</abbrev>
<authorgroup>
- <author>
- <surname>Gulbrandsen</surname>
- <firstname>A.</firstname>
- </author>
- <author>
- <firstname>P.</firstname>
- <surname>Vixie</surname>
- </author>
+ <author><personname><surname>Gulbrandsen</surname><firstname>A.</firstname></personname></author>
+ <author><personname><firstname>P.</firstname><surname>Vixie</surname></personname></author>
</authorgroup>
- <title>A <acronym>DNS</acronym> RR for Specifying the
+ <
citetitle>A <acronym>DNS</acronym> RR for Specifying the
Location of
- Services</title>
+ Services</citetitle>
<pubdate>October 1996</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2163</abbrev>
- <author>
- <surname>Allocchio</surname>
- <firstname>A.</firstname>
- </author>
- <title>Using the Internet <acronym>DNS</acronym> to
+ <author><personname><surname>Allocchio</surname><firstname>A.</firstname></personname></author>
+ <citetitle>Using the Internet <acronym>DNS</acronym> to
Distribute MIXER
- Conformant Global Address Mapping</title>
+ Conformant Global Address Mapping</citetitle>
<pubdate>January 1998</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2230</abbrev>
- <author>
- <surname>Atkinson</surname>
- <firstname>R.</firstname>
- </author>
- <title>Key Exchange Delegation Record for the <acronym>DNS</acronym></title>
+ <author><personname><surname>Atkinson</surname><firstname>R.</firstname></personname></author>
+ <citetitle>Key Exchange Delegation Record for the <acronym>DNS</acronym></citetitle>
<pubdate>October 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2536</abbrev>
- <author>
- <surname>Eastlake</surname>
- <firstname>D.</firstname>
- <lineage>3rd</lineage>
- </author>
- <title>DSA KEYs and SIGs in the Domain Name System (DNS)</title>
+ <author><personname><surname>Eastlake</surname><firstname>D.</firstname><lineage>3rd</lineage></personname></author>
+ <citetitle>DSA KEYs and SIGs in the Domain Name System (DNS)</citetitle>
<pubdate>March 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2537</abbrev>
- <author>
- <surname>Eastlake</surname>
- <firstname>D.</firstname>
- <lineage>3rd</lineage>
- </author>
- <title>RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</title>
+ <author><personname><surname>Eastlake</surname><firstname>D.</firstname><lineage>3rd</lineage></personname></author>
+ <citetitle>RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</citetitle>
<pubdate>March 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2538</abbrev>
<authorgroup>
- <author>
- <surname>Eastlake</surname>
- <firstname>D.</firstname>
- <lineage>3rd</lineage>
- </author>
- <author>
- <surname>Gudmundsson</surname>
- <firstname>O.</firstname>
- </author>
+ <author><personname><surname>Eastlake</surname><firstname>D.</firstname><lineage>3rd</lineage></personname></author>
+ <author><personname><surname>Gudmundsson</surname><firstname>O.</firstname></personname></author>
</authorgroup>
- <title>Storing Certificates in the Domain Name System (DNS)</title>
+ <citetitle>Storing Certificates in the Domain Name System (DNS)</citetitle>
<pubdate>March 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2539</abbrev>
<authorgroup>
- <author>
- <surname>Eastlake</surname>
- <firstname>D.</firstname>
- <lineage>3rd</lineage>
- </author>
+ <author><personname><surname>Eastlake</surname><firstname>D.</firstname><lineage>3rd</lineage></personname></author>
</authorgroup>
- <title>Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</title>
+ <citetitle>Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</citetitle>
<pubdate>March 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2540</abbrev>
<authorgroup>
- <author>
- <surname>Eastlake</surname>
- <firstname>D.</firstname>
- <lineage>3rd</lineage>
- </author>
+ <author><personname><surname>Eastlake</surname><firstname>D.</firstname><lineage>3rd</lineage></personname></author>
</authorgroup>
- <title>Detached Domain Name System (DNS) Information</title>
+ <citetitle>Detached Domain Name System (DNS) Information</citetitle>
<pubdate>March 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2782</abbrev>
- <author>
- <surname>Gulbrandsen</surname>
- <firstname>A.</firstname>
- </author>
- <author>
- <surname>Vixie</surname>
- <firstname>P.</firstname>
- </author>
- <author>
- <surname>Esibov</surname>
- <firstname>L.</firstname>
- </author>
- <title>A DNS RR for specifying the location of services (DNS SRV)</title>
+ <author><personname><surname>Gulbrandsen</surname><firstname>A.</firstname></personname></author>
+ <author><personname><surname>Vixie</surname><firstname>P.</firstname></personname></author>
+ <author><personname><surname>Esibov</surname><firstname>L.</firstname></personname></author>
+ <citetitle>A DNS RR for specifying the location of services (DNS SRV)</citetitle>
<pubdate>February 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2915</abbrev>
- <author>
- <surname>Mealling</surname>
- <firstname>M.</firstname>
- </author>
- <author>
- <surname>Daniel</surname>
- <firstname>R.</firstname>
- </author>
- <title>The Naming Authority Pointer (NAPTR) DNS Resource Record</title>
+ <author><personname><surname>Mealling</surname><firstname>M.</firstname></personname></author>
+ <author><personname><surname>Daniel</surname><firstname>R.</firstname></personname></author>
+ <citetitle>The Naming Authority Pointer (NAPTR) DNS Resource Record</citetitle>
<pubdate>September 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3110</abbrev>
- <author>
- <surname>Eastlake</surname>
- <firstname>D.</firstname>
- <lineage>3rd</lineage>
- </author>
- <title>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</title>
+ <author><personname><surname>Eastlake</surname><firstname>D.</firstname><lineage>3rd</lineage></personname></author>
+ <citetitle>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</citetitle>
<pubdate>May 2001</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3123</abbrev>
- <author>
- <surname>Koch</surname>
- <firstname>P.</firstname>
- </author>
- <title>A DNS RR Type for Lists of Address Prefixes (APL RR)</title>
+ <author><personname><surname>Koch</surname><firstname>P.</firstname></personname></author>
+ <citetitle>A DNS RR Type for Lists of Address Prefixes (APL RR)</citetitle>
<pubdate>June 2001</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3596</abbrev>
<authorgroup>
- <author>
- <surname>Thomson</surname>
- <firstname>S.</firstname>
- </author>
- <author>
- <firstname>C.</firstname>
- <surname>Huitema</surname>
- </author>
- <author>
- <firstname>V.</firstname>
- <surname>Ksinant</surname>
- </author>
- <author>
- <firstname>M.</firstname>
- <surname>Souissi</surname>
- </author>
+ <author><personname><surname>Thomson</surname><firstname>S.</firstname></personname></author>
+ <author><personname><firstname>C.</firstname><surname>Huitema</surname></personname></author>
+ <author><personname><firstname>V.</firstname><surname>Ksinant</surname></personname></author>
+ <author><personname><firstname>M.</firstname><surname>Souissi</surname></personname></author>
</authorgroup>
- <title><acronym>DNS</acronym> Extensions to support IP
- version 6</title>
+ <
citetitle><acronym>DNS</acronym> Extensions to support IP
+ version 6</citetitle>
<pubdate>October 2003</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3597</abbrev>
- <author>
- <surname>Gustafsson</surname>
- <firstname>A.</firstname>
- </author>
- <title>Handling of Unknown DNS Resource Record (RR) Types</title>
+ <author><personname><surname>Gustafsson</surname><firstname>A.</firstname></personname></author>
+ <citetitle>Handling of Unknown DNS Resource Record (RR) Types</citetitle>
<pubdate>September 2003</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title><acronym>DNS</acronym> and the Internet</title>
+ <bibliodiv><info><title><acronym>DNS</acronym> and the Internet</title></info>
+
<biblioentry>
<abbrev>RFC1101</abbrev>
- <author>
- <surname>Mockapetris</surname>
- <firstname>P. V.</firstname>
- </author>
- <title><acronym>DNS</acronym> Encoding of Network Names
- and Other Types</title>
+ <author><personname><surname>Mockapetris</surname><firstname>P. V.</firstname></personname></author>
+ <citetitle><acronym>DNS</acronym> Encoding of Network Names
+ and Other Types</citetitle>
<pubdate>April 1989</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1123</abbrev>
- <author>
- <surname>Braden</surname>
- <surname>R.</surname>
- </author>
- <title>Requirements for Internet Hosts - Application and
- Support</title>
+ <author><personname><surname>Braden</surname><surname>R.</surname></personname></author>
+ <citetitle>Requirements for Internet Hosts - Application and
+ Support</citetitle>
<pubdate>October 1989</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1591</abbrev>
- <author>
- <surname>Postel</surname>
- <firstname>J.</firstname>
- </author>
- <title>Domain Name System Structure and Delegation</title>
+ <author><personname><surname>Postel</surname><firstname>J.</firstname></personname></author>
+ <citetitle>Domain Name System Structure and Delegation</citetitle>
<pubdate>March 1994</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2317</abbrev>
<authorgroup>
- <author>
- <surname>Eidnes</surname>
- <firstname>H.</firstname>
- </author>
- <author>
- <firstname>G.</firstname>
- <surname>de Groot</surname>
- </author>
- <author>
- <firstname>P.</firstname>
- <surname>Vixie</surname>
- </author>
+ <author><personname><surname>Eidnes</surname><firstname>H.</firstname></personname></author>
+ <author><personname><firstname>G.</firstname><surname>de Groot</surname></personname></author>
+ <author><personname><firstname>P.</firstname><surname>Vixie</surname></personname></author>
</authorgroup>
- <title>Classless IN-ADDR.ARPA Delegation</title>
+ <citetitle>Classless IN-ADDR.ARPA Delegation</citetitle>
<pubdate>March 1998</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2826</abbrev>
<authorgroup>
- <author>
- <surname>Internet Architecture Board</surname>
- </author>
+ <author><personname><surname>Internet Architecture Board</surname></personname></author>
</authorgroup>
- <title>IAB Technical Comment on the Unique DNS Root</title>
+ <citetitle>IAB Technical Comment on the Unique DNS Root</citetitle>
<pubdate>May 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2929</abbrev>
<authorgroup>
- <author>
- <surname>Eastlake</surname>
- <firstname>D.</firstname>
- <lineage>3rd</lineage>
- </author>
- <author>
- <surname>Brunner-Williams</surname>
- <firstname>E.</firstname>
- </author>
- <author>
- <surname>Manning</surname>
- <firstname>B.</firstname>
- </author>
+ <author><personname><surname>Eastlake</surname><firstname>D.</firstname><lineage>3rd</lineage></personname></author>
+ <author><personname><surname>Brunner-Williams</surname><firstname>E.</firstname></personname></author>
+ <author><personname><surname>Manning</surname><firstname>B.</firstname></personname></author>
</authorgroup>
- <title>Domain Name System (DNS) IANA Considerations</title>
+ <citetitle>Domain Name System (DNS) IANA Considerations</citetitle>
<pubdate>September 2000</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title><acronym>DNS</acronym> Operations</title>
+ <bibliodiv><info><title><acronym>DNS</acronym> Operations</title></info>
+
<biblioentry>
<abbrev>RFC1033</abbrev>
- <author>
- <surname>Lottor</surname>
- <firstname>M.</firstname>
- </author>
- <title>Domain administrators operations guide</title>
+ <author><personname><surname>Lottor</surname><firstname>M.</firstname></personname></author>
+ <citetitle>Domain administrators operations guide</citetitle>
<pubdate>November 1987</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1537</abbrev>
- <author>
- <surname>Beertema</surname>
- <firstname>P.</firstname>
- </author>
- <title>Common <acronym>DNS</acronym> Data File
- Configuration Errors</title>
+ <author><personname><surname>Beertema</surname><firstname>P.</firstname></personname></author>
+ <citetitle>Common <acronym>DNS</acronym> Data File
+ Configuration Errors</citetitle>
<pubdate>October 1993</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1912</abbrev>
- <author>
- <surname>Barr</surname>
- <firstname>D.</firstname>
- </author>
- <title>Common <acronym>DNS</acronym> Operational and
- Configuration Errors</title>
+ <author><personname><surname>Barr</surname><firstname>D.</firstname></personname></author>
+ <citetitle>Common <acronym>DNS</acronym> Operational and
+ Configuration Errors</citetitle>
<pubdate>February 1996</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2010</abbrev>
<authorgroup>
- <author>
- <surname>Manning</surname>
- <firstname>B.</firstname>
- </author>
- <author>
- <firstname>P.</firstname>
- <surname>Vixie</surname>
- </author>
+ <author><personname><surname>Manning</surname><firstname>B.</firstname></personname></author>
+ <author><personname><firstname>P.</firstname><surname>Vixie</surname></personname></author>
</authorgroup>
- <title>Operational Criteria for Root Name Servers</title>
+ <citetitle>Operational Criteria for Root Name Servers</citetitle>
<pubdate>October 1996</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2219</abbrev>
<authorgroup>
- <author>
- <surname>Hamilton</surname>
- <firstname>M.</firstname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Wright</surname>
- </author>
+ <author><personname><surname>Hamilton</surname><firstname>M.</firstname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Wright</surname></personname></author>
</authorgroup>
- <title>Use of <acronym>DNS</acronym> Aliases for
- Network Services</title>
+ <
citetitle>Use of <acronym>DNS</acronym> Aliases for
+ Network Services</citetitle>
<pubdate>October 1997</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title>Internationalized Domain Names</title>
+ <bibliodiv><info><title>Internationalized Domain Names</title></info>
+
<biblioentry>
<abbrev>RFC2825</abbrev>
<authorgroup>
- <author>
- <surname>IAB</surname>
- </author>
- <author>
- <surname>Daigle</surname>
- <firstname>R.</firstname>
- </author>
+ <author><personname><surname>IAB</surname></personname></author>
+ <author><personname><surname>Daigle</surname><firstname>R.</firstname></personname></author>
</authorgroup>
- <title>A Tangled Web: Issues of I18N, Domain Names,
- and the Other Internet protocols</title>
+ <citetitle>A Tangled Web: Issues of I18N, Domain Names,
+ and the Other Internet protocols</citetitle>
<pubdate>May 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3490</abbrev>
<authorgroup>
- <author>
- <surname>Faltstrom</surname>
- <firstname>P.</firstname>
- </author>
- <author>
- <surname>Hoffman</surname>
- <firstname>P.</firstname>
- </author>
- <author>
- <surname>Costello</surname>
- <firstname>A.</firstname>
- </author>
+ <author><personname><surname>Faltstrom</surname><firstname>P.</firstname></personname></author>
+ <author><personname><surname>Hoffman</surname><firstname>P.</firstname></personname></author>
+ <author><personname><surname>Costello</surname><firstname>A.</firstname></personname></author>
</authorgroup>
- <title>Internationalizing Domain Names in Applications (IDNA)</title>
+ <citetitle>Internationalizing Domain Names in Applications (IDNA)</citetitle>
<pubdate>March 2003</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3491</abbrev>
<authorgroup>
- <author>
- <surname>Hoffman</surname>
- <firstname>P.</firstname>
- </author>
- <author>
- <surname>Blanchet</surname>
- <firstname>M.</firstname>
- </author>
+ <author><personname><surname>Hoffman</surname><firstname>P.</firstname></personname></author>
+ <author><personname><surname>Blanchet</surname><firstname>M.</firstname></personname></author>
</authorgroup>
- <title>Nameprep: A Stringprep Profile for Internationalized Domain Names</title>
+ <citetitle>Nameprep: A Stringprep Profile for Internationalized Domain Names</citetitle>
<pubdate>March 2003</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3492</abbrev>
<authorgroup>
- <author>
- <surname>Costello</surname>
- <firstname>A.</firstname>
- </author>
+ <author><personname><surname>Costello</surname><firstname>A.</firstname></personname></author>
</authorgroup>
- <title>Punycode: A Bootstring encoding of Unicode
+ <citetitle>Punycode: A Bootstring encoding of Unicode
for Internationalized Domain Names in
- Applications (IDNA)</title>
+ Applications (IDNA)</citetitle>
<pubdate>March 2003</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title>Other <acronym>DNS</acronym>-related RFCs</title>
+ <bibliodiv><info><title>Other <acronym>DNS</acronym>-related RFCs</title></info>
+
<note>
<para>
Note: the following list of RFCs, although
</note>
<biblioentry>
<abbrev>RFC1464</abbrev>
- <author>
- <surname>Rosenbaum</surname>
- <firstname>R.</firstname>
- </author>
- <title>Using the Domain Name System To Store Arbitrary String
- Attributes</title>
+ <author><personname><surname>Rosenbaum</surname><firstname>R.</firstname></personname></author>
+ <citetitle>Using the Domain Name System To Store Arbitrary String
+ Attributes</citetitle>
<pubdate>May 1993</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1713</abbrev>
- <author>
- <surname>Romao</surname>
- <firstname>A.</firstname>
- </author>
- <title>Tools for <acronym>DNS</acronym> Debugging</title>
+ <author><personname><surname>Romao</surname><firstname>A.</firstname></personname></author>
+ <citetitle>Tools for <acronym>DNS</acronym> Debugging</citetitle>
<pubdate>November 1994</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC1794</abbrev>
- <author>
- <surname>Brisco</surname>
- <firstname>T.</firstname>
- </author>
- <title><acronym>DNS</acronym> Support for Load
- Balancing</title>
+ <author><personname><surname>Brisco</surname><firstname>T.</firstname></personname></author>
+ <citetitle><acronym>DNS</acronym> Support for Load
+ Balancing</citetitle>
<pubdate>April 1995</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2240</abbrev>
- <author>
- <surname>Vaughan</surname>
- <firstname>O.</firstname>
- </author>
- <title>A Legal Basis for Domain Name Allocation</title>
+ <author><personname><surname>Vaughan</surname><firstname>O.</firstname></personname></author>
+ <citetitle>A Legal Basis for Domain Name Allocation</citetitle>
<pubdate>November 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2345</abbrev>
<authorgroup>
- <author>
- <surname>Klensin</surname>
- <firstname>J.</firstname>
- </author>
- <author>
- <firstname>T.</firstname>
- <surname>Wolf</surname>
- </author>
- <author>
- <firstname>G.</firstname>
- <surname>Oglesby</surname>
- </author>
+ <author><personname><surname>Klensin</surname><firstname>J.</firstname></personname></author>
+ <author><personname><firstname>T.</firstname><surname>Wolf</surname></personname></author>
+ <author><personname><firstname>G.</firstname><surname>Oglesby</surname></personname></author>
</authorgroup>
- <title>Domain Names and Company Name Retrieval</title>
+ <citetitle>Domain Names and Company Name Retrieval</citetitle>
<pubdate>May 1998</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2352</abbrev>
- <author>
- <surname>Vaughan</surname>
- <firstname>O.</firstname>
- </author>
- <title>A Convention For Using Legal Names as Domain Names</title>
+ <author><personname><surname>Vaughan</surname><firstname>O.</firstname></personname></author>
+ <citetitle>A Convention For Using Legal Names as Domain Names</citetitle>
<pubdate>May 1998</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3071</abbrev>
<authorgroup>
- <author>
- <surname>Klensin</surname>
- <firstname>J.</firstname>
- </author>
+ <author><personname><surname>Klensin</surname><firstname>J.</firstname></personname></author>
</authorgroup>
- <title>Reflections on the DNS, RFC 1591, and Categories of Domains</title>
+ <citetitle>Reflections on the DNS, RFC 1591, and Categories of Domains</citetitle>
<pubdate>February 2001</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3258</abbrev>
<authorgroup>
- <author>
- <surname>Hardie</surname>
- <firstname>T.</firstname>
- </author>
+ <author><personname><surname>Hardie</surname><firstname>T.</firstname></personname></author>
</authorgroup>
- <title>Distributing Authoritative Name Servers via
- Shared Unicast Addresses</title>
+ <citetitle>Distributing Authoritative Name Servers via
+ Shared Unicast Addresses</citetitle>
<pubdate>April 2002</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3901</abbrev>
<authorgroup>
- <author>
- <surname>Durand</surname>
- <firstname>A.</firstname>
- </author>
- <author>
- <firstname>J.</firstname>
- <surname>Ihren</surname>
- </author>
+ <author><personname><surname>Durand</surname><firstname>A.</firstname></personname></author>
+ <author><personname><firstname>J.</firstname><surname>Ihren</surname></personname></author>
</authorgroup>
- <title>DNS IPv6 Transport Operational Guidelines</title>
+ <citetitle>DNS IPv6 Transport Operational Guidelines</citetitle>
<pubdate>September 2004</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title>Obsolete and Unimplemented Experimental RFC</title>
+ <bibliodiv><info><title>Obsolete and Unimplemented Experimental RFC</title></info>
+
<biblioentry>
<abbrev>RFC1712</abbrev>
<authorgroup>
- <author>
- <surname>Farrell</surname>
- <firstname>C.</firstname>
- </author>
- <author>
- <firstname>M.</firstname>
- <surname>Schulze</surname>
- </author>
- <author>
- <firstname>S.</firstname>
- <surname>Pleitner</surname>
- </author>
- <author>
- <firstname>D.</firstname>
- <surname>Baldoni</surname>
- </author>
+ <author><personname><surname>Farrell</surname><firstname>C.</firstname></personname></author>
+ <author><personname><firstname>M.</firstname><surname>Schulze</surname></personname></author>
+ <author><personname><firstname>S.</firstname><surname>Pleitner</surname></personname></author>
+ <author><personname><firstname>D.</firstname><surname>Baldoni</surname></personname></author>
</authorgroup>
- <title><acronym>DNS</acronym> Encoding of Geographical
- Location</title>
+ <
citetitle><acronym>DNS</acronym> Encoding of Geographical
+ Location</citetitle>
<pubdate>November 1994</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2673</abbrev>
<authorgroup>
- <author>
- <surname>Crawford</surname>
- <firstname>M.</firstname>
- </author>
+ <author><personname><surname>Crawford</surname><firstname>M.</firstname></personname></author>
</authorgroup>
- <title>Binary Labels in the Domain Name System</title>
+ <citetitle>Binary Labels in the Domain Name System</citetitle>
<pubdate>August 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2874</abbrev>
<authorgroup>
- <author>
- <surname>Crawford</surname>
- <firstname>M.</firstname>
- </author>
- <author>
- <surname>Huitema</surname>
- <firstname>C.</firstname>
- </author>
+ <author><personname><surname>Crawford</surname><firstname>M.</firstname></personname></author>
+ <author><personname><surname>Huitema</surname><firstname>C.</firstname></personname></author>
</authorgroup>
- <title>DNS Extensions to Support IPv6 Address Aggregation
- and Renumbering</title>
+ <citetitle>DNS Extensions to Support IPv6 Address Aggregation
+ and Renumbering</citetitle>
<pubdate>July 2000</pubdate>
</biblioentry>
</bibliodiv>
- <bibliodiv>
- <title>Obsoleted DNS Security RFCs</title>
+ <bibliodiv><info><title>Obsoleted DNS Security RFCs</title></info>
+
<note>
<para>
Most of these have been consolidated into RFC4033,
<biblioentry>
<abbrev>RFC2065</abbrev>
<authorgroup>
- <author>
- <surname>Eastlake</surname>
- <lineage>3rd</lineage>
- <firstname>D.</firstname>
- </author>
- <author>
- <firstname>C.</firstname>
- <surname>Kaufman</surname>
- </author>
+ <author><personname><surname>Eastlake</surname><lineage>3rd</lineage><firstname>D.</firstname></personname></author>
+ <author><personname><firstname>C.</firstname><surname>Kaufman</surname></personname></author>
</authorgroup>
- <title>Domain Name System Security Extensions</title>
+ <citetitle>Domain Name System Security Extensions</citetitle>
<pubdate>January 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2137</abbrev>
- <author>
- <surname>Eastlake</surname>
- <lineage>3rd</lineage>
- <firstname>D.</firstname>
- </author>
- <title>Secure Domain Name System Dynamic Update</title>
+ <author><personname><surname>Eastlake</surname><lineage>3rd</lineage><firstname>D.</firstname></personname></author>
+ <citetitle>Secure Domain Name System Dynamic Update</citetitle>
<pubdate>April 1997</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC2535</abbrev>
<authorgroup>
- <author>
- <surname>Eastlake</surname>
- <lineage>3rd</lineage>
- <firstname>D.</firstname>
- </author>
+ <author><personname><surname>Eastlake</surname><lineage>3rd</lineage><firstname>D.</firstname></personname></author>
</authorgroup>
- <title>Domain Name System Security Extensions</title>
+ <citetitle>Domain Name System Security Extensions</citetitle>
<pubdate>March 1999</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3008</abbrev>
<authorgroup>
- <author>
- <surname>Wellington</surname>
- <firstname>B.</firstname>
- </author>
+ <author><personname><surname>Wellington</surname><firstname>B.</firstname></personname></author>
</authorgroup>
- <title>Domain Name System Security (DNSSEC)
- Signing Authority</title>
+ <citetitle>Domain Name System Security (DNSSEC)
+ Signing Authority</citetitle>
<pubdate>November 2000</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3090</abbrev>
<authorgroup>
- <author>
- <surname>Lewis</surname>
- <firstname>E.</firstname>
- </author>
+ <author><personname><surname>Lewis</surname><firstname>E.</firstname></personname></author>
</authorgroup>
- <title>DNS Security Extension Clarification on Zone Status</title>
+ <citetitle>DNS Security Extension Clarification on Zone Status</citetitle>
<pubdate>March 2001</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3445</abbrev>
<authorgroup>
- <author>
- <surname>Massey</surname>
- <firstname>D.</firstname>
- </author>
- <author>
- <surname>Rose</surname>
- <firstname>S.</firstname>
- </author>
+ <author><personname><surname>Massey</surname><firstname>D.</firstname></personname></author>
+ <author><personname><surname>Rose</surname><firstname>S.</firstname></personname></author>
</authorgroup>
- <title>Limiting the Scope of the KEY Resource Record (RR)</title>
+ <citetitle>Limiting the Scope of the KEY Resource Record (RR)</citetitle>
<pubdate>December 2002</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3655</abbrev>
<authorgroup>
- <author>
- <surname>Wellington</surname>
- <firstname>B.</firstname>
- </author>
- <author>
- <surname>Gudmundsson</surname>
- <firstname>O.</firstname>
- </author>
+ <author><personname><surname>Wellington</surname><firstname>B.</firstname></personname></author>
+ <author><personname><surname>Gudmundsson</surname><firstname>O.</firstname></personname></author>
</authorgroup>
- <title>Redefinition of DNS Authenticated Data (AD) bit</title>
+ <citetitle>Redefinition of DNS Authenticated Data (AD) bit</citetitle>
<pubdate>November 2003</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3658</abbrev>
<authorgroup>
- <author>
- <surname>Gudmundsson</surname>
- <firstname>O.</firstname>
- </author>
+ <author><personname><surname>Gudmundsson</surname><firstname>O.</firstname></personname></author>
</authorgroup>
- <title>Delegation Signer (DS) Resource Record (RR)</title>
+ <citetitle>Delegation Signer (DS) Resource Record (RR)</citetitle>
<pubdate>December 2003</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3755</abbrev>
<authorgroup>
- <author>
- <surname>Weiler</surname>
- <firstname>S.</firstname>
- </author>
+ <author><personname><surname>Weiler</surname><firstname>S.</firstname></personname></author>
</authorgroup>
- <title>Legacy Resolver Compatibility for Delegation Signer (DS)</title>
+ <citetitle>Legacy Resolver Compatibility for Delegation Signer (DS)</citetitle>
<pubdate>May 2004</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3757</abbrev>
<authorgroup>
- <author>
- <surname>Kolkman</surname>
- <firstname>O.</firstname>
- </author>
- <author>
- <surname>Schlyter</surname>
- <firstname>J.</firstname>
- </author>
- <author>
- <surname>Lewis</surname>
- <firstname>E.</firstname>
- </author>
+ <author><personname><surname>Kolkman</surname><firstname>O.</firstname></personname></author>
+ <author><personname><surname>Schlyter</surname><firstname>J.</firstname></personname></author>
+ <author><personname><surname>Lewis</surname><firstname>E.</firstname></personname></author>
</authorgroup>
- <title>Domain Name System KEY (DNSKEY) Resource Record
- (RR) Secure Entry Point (SEP) Flag</title>
+ <citetitle>Domain Name System KEY (DNSKEY) Resource Record
+ (RR) Secure Entry Point (SEP) Flag</citetitle>
<pubdate>April 2004</pubdate>
</biblioentry>
<biblioentry>
<abbrev>RFC3845</abbrev>
<authorgroup>
- <author>
- <surname>Schlyter</surname>
- <firstname>J.</firstname>
- </author>
+ <author><personname><surname>Schlyter</surname><firstname>J.</firstname></personname></author>
</authorgroup>
- <title>DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</title>
+ <citetitle>DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</citetitle>
<pubdate>August 2004</pubdate>
</biblioentry>
</bibliodiv>
</bibliography>
- </sect2>
- <sect2 id="internet_drafts">
- <title>Internet Drafts</title>
+ </section>
+ <section xml:id="internet_drafts"><info><title>Internet Drafts</title></info>
+
<para>
Internet Drafts (IDs) are rough-draft working documents of
the Internet Engineering Task Force. They are, in essence, RFCs
they are "works in progress." IDs have a lifespan of six months
after which they are deleted unless updated by their authors.
</para>
- </sect2>
- <sect2>
- <title>Other Documents About <acronym>BIND</acronym></title>
+ </section>
+ <section><info><title>Other Documents About <acronym>BIND</acronym></title></info>
+
<para/>
<bibliography>
<biblioentry>
<authorgroup>
- <author>
- <surname>Albitz</surname>
- <firstname>Paul</firstname>
- </author>
- <author>
- <firstname>Cricket</firstname>
- <surname>Liu</surname>
- </author>
+ <author><personname><surname>Albitz</surname><firstname>Paul</firstname></personname></author>
+ <author><personname><firstname>Cricket</firstname><surname>Liu</surname></personname></author>
</authorgroup>
- <title><acronym>DNS</acronym> and <acronym>BIND</acronym></title>
+ <citetitle><acronym>DNS</acronym> and <acronym>BIND</acronym></citetitle>
<copyright>
<year>1998</year>
<holder>Sebastopol, CA: O'Reilly and Associates</holder>
</copyright>
</biblioentry>
</bibliography>
- </sect2>
- </sect1>
+ </section>
+ </section>
</appendix>
- <appendix id="Bv9ARM.ch12">
- <title>BIND 9 DNS Library Support</title>
- <xi:include href="libdns.xml"/>
+ <appendix xml:id="Bv9ARM.ch12"><info><title>BIND 9 DNS Library Support</title></info>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libdns.xml"/>
</appendix>
- <reference id="Bv9ARM.ch13">
- <title>Manual pages</title>
- <xi:include href="../../bin/dig/dig.docbook"/>
- <xi:include href="../../bin/dig/host.docbook"/>
- <xi:include href="../../bin/delv/delv.docbook"/>
- <xi:include href="../../bin/python/dnssec-checkds.docbook"/>
- <xi:include href="../../bin/python/dnssec-coverage.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-dsfromkey.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-importkey.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-keyfromlabel.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-keygen.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-revoke.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-settime.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-signzone.docbook"/>
- <xi:include href="../../bin/dnssec/dnssec-verify.docbook"/>
- <xi:include href="../../bin/check/named-checkconf.docbook"/>
- <xi:include href="../../bin/check/named-checkzone.docbook"/>
- <xi:include href="../../bin/named/named.docbook"/>
- <xi:include href="../../bin/named/named.conf.docbook"/>
- <xi:include href="../../bin/named/lwresd.docbook"/>
- <xi:include href="../../bin/tools/named-journalprint.docbook"/>
- <xi:include href="../../bin/tools/named-rrchecker.docbook"/>
- <xi:include href="../../bin/nsupdate/nsupdate.docbook"/>
- <xi:include href="../../bin/rndc/rndc.docbook"/>
- <xi:include href="../../bin/rndc/rndc.conf.docbook"/>
- <xi:include href="../../bin/confgen/rndc-confgen.docbook"/>
- <xi:include href="../../bin/confgen/ddns-confgen.docbook"/>
- <xi:include href="../../bin/tools/arpaname.docbook"/>
- <xi:include href="../../bin/tools/dnstap-read.docbook"/>
- <xi:include href="../../bin/tools/genrandom.docbook"/>
- <xi:include href="../../bin/tools/isc-hmac-fixup.docbook"/>
- <xi:include href="../../bin/tools/named-journalprint.docbook"/>
- <xi:include href="../../bin/tools/named-rrchecker.docbook"/>
- <xi:include href="../../bin/tools/nsec3hash.docbook"/>
+ <reference xml:id="Bv9ARM.ch13"><info><title>Manual pages</title></info>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dig/dig.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dig/host.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/delv/delv.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/python/dnssec-checkds.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/python/dnssec-coverage.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-dsfromkey.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-importkey.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-keyfromlabel.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-keygen.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-revoke.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-settime.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-signzone.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/dnssec/dnssec-verify.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/named/lwresd.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/named/named.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/named/named.conf.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/check/named-checkconf.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/check/named-checkzone.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/tools/named-journalprint.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/tools/named-rrchecker.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/nsupdate/nsupdate.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/rndc/rndc.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/rndc/rndc.conf.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/confgen/rndc-confgen.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/confgen/ddns-confgen.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/tools/arpaname.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/tools/dnstap-read.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/tools/genrandom.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/tools/isc-hmac-fixup.docbook"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../bin/tools/nsec3hash.docbook"/>
</reference>
</book>
-
-<!--
- - Local variables:
- - mode: sgml
- - End:
- -->
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 1. Introduction</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="next" href="Bv9ARM.ch02.html" title="Chapter 2. BIND Resource Requirements">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch01"></a>Chapter 1. Introduction</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch01"></a>Chapter 1. Introduction</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2563509">Scope of Document</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2563533">Organization of This Document</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2564629">Conventions Used in This Document</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch01.html#id2564810">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
+<dl class="toc">
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.4">Scope of Document</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.5">Organization of This Document</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6">Conventions Used in This Document</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch01.html#id-1.2.7">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2564832">DNS Fundamentals</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2564934">Domains and Domain Names</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567271">Zones</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567348">Authoritative Name Servers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567589">Caching Name Servers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567651">Name Servers in Multiple Roles</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.4">DNS Fundamentals</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.5">Domains and Domain Names</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.6">Zones</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.7">Authoritative Name Servers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.8">Caching Name Servers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.9">Name Servers in Multiple Roles</a></span></dt>
</dl></dd>
</dl>
</div>
-<p>
+
+ <p>
The Internet Domain Name System (<acronym class="acronym">DNS</acronym>)
consists of the syntax
to specify the names of entities in the Internet in a hierarchical
group of distributed
hierarchical databases.
</p>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2563509"></a>Scope of Document</h2></div></div></div>
-<p>
+<a name="id-1.2.4"></a>Scope of Document</h2></div></div></div>
+
+
+ <p>
The Berkeley Internet Name Domain
(<acronym class="acronym">BIND</acronym>) implements a
domain name server for a number of operating systems. This
<acronym class="acronym">BIND</acronym> version 9 software package for
system administrators.
</p>
-<p>This version of the manual corresponds to BIND version 9.11.</p>
-</div>
-<div class="sect1" lang="en">
+ <p>This version of the manual corresponds to BIND version 9.11.</p>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2563533"></a>Organization of This Document</h2></div></div></div>
-<p>
+<a name="id-1.2.5"></a>Organization of This Document</h2></div></div></div>
+
+ <p>
In this document, <span class="emphasis"><em>Chapter 1</em></span> introduces
the basic <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym> concepts. <span class="emphasis"><em>Chapter 2</em></span>
describes resource requirements for running <acronym class="acronym">BIND</acronym> in various
and the Domain Name
System.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2564629"></a>Conventions Used in This Document</h2></div></div></div>
-<p>
+<a name="id-1.2.6"></a>Conventions Used in This Document</h2></div></div></div>
+
+
+ <p>
In this document, we use the following general typographic
conventions:
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="3.000in" class="1">
+<col width="2.625in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+
+ <p>
The following conventions are used in descriptions of the
<acronym class="acronym">BIND</acronym> configuration file:</p>
-<div class="informaltable"><table border="1">
+<div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="3.000in" class="1">
+<col width="2.625in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
+</table>
+ </div>
<p>
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2564810"></a>The Domain Name System (<acronym class="acronym">DNS</acronym>)</h2></div></div></div>
-<p>
+<a name="id-1.2.7"></a>The Domain Name System (<acronym class="acronym">DNS</acronym>)</h2></div></div></div>
+
+ <p>
The purpose of this document is to explain the installation
and upkeep of the <acronym class="acronym">BIND</acronym> (Berkeley Internet
Name Domain) software package, and we
begin by reviewing the fundamentals of the Domain Name System
(<acronym class="acronym">DNS</acronym>) as they relate to <acronym class="acronym">BIND</acronym>.
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2564832"></a>DNS Fundamentals</h3></div></div></div>
-<p>
+<a name="id-1.2.7.4"></a>DNS Fundamentals</h3></div></div></div>
+
+
+ <p>
The Domain Name System (DNS) is a hierarchical, distributed
database. It stores information for mapping Internet host names to
IP
addresses and vice versa, mail routing information, and other data
used by Internet applications.
</p>
-<p>
+
+ <p>
Clients look up information in the DNS by calling a
<span class="emphasis"><em>resolver</em></span> library, which sends queries to one or
more <span class="emphasis"><em>name servers</em></span> and interprets the responses.
The <acronym class="acronym">BIND</acronym> 9 software distribution
contains a
- name server, <span><strong class="command">named</strong></span>, and a resolver
- library, <span><strong class="command">liblwres</strong></span>. The older
- <span><strong class="command">libbind</strong></span> resolver library is also available
+ name server, <span class="command"><strong>named</strong></span>, and a resolver
+ library, <span class="command"><strong>liblwres</strong></span>. The older
+ <span class="command"><strong>libbind</strong></span> resolver library is also available
from ISC as a separate download.
</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2564934"></a>Domains and Domain Names</h3></div></div></div>
-<p>
+<a name="id-1.2.7.5"></a>Domains and Domain Names</h3></div></div></div>
+
+
+ <p>
The data stored in the DNS is identified by <span class="emphasis"><em>domain names</em></span> that are organized as a tree according to
organizational or administrative boundaries. Each node of the tree,
called a <span class="emphasis"><em>domain</em></span>, is given a label. The domain
separated by dots. A label need only be unique within its parent
domain.
</p>
-<p>
+
+ <p>
For example, a domain name for a host at the
company <span class="emphasis"><em>Example, Inc.</em></span> could be
<code class="literal">ourhost.example.com</code>,
<code class="literal">ourhost</code> is the
name of the host.
</p>
-<p>
+
+ <p>
For administrative purposes, the name space is partitioned into
areas called <span class="emphasis"><em>zones</em></span>, each starting at a node and
extending down to the leaf nodes or to nodes where other zones
The data for each zone is stored in a <span class="emphasis"><em>name server</em></span>, which answers queries about the zone using the
<span class="emphasis"><em>DNS protocol</em></span>.
</p>
-<p>
+
+ <p>
The data associated with each domain name is stored in the
form of <span class="emphasis"><em>resource records</em></span> (<acronym class="acronym">RR</acronym>s).
Some of the supported resource record types are described in
- <a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them" title="Types of Resource Records and When to Use Them">the section called “Types of Resource Records and When to Use Them”</a>.
+ <a class="xref" href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them" title="Types of Resource Records and When to Use Them">the section called “Types of Resource Records and When to Use Them”</a>.
</p>
-<p>
+
+ <p>
For more detailed information about the design of the DNS and
the DNS protocol, please refer to the standards documents listed in
- <a href="Bv9ARM.ch11.html#rfcs" title="Request for Comments (RFCs)">the section called “Request for Comments (RFCs)”</a>.
+ <a class="xref" href="Bv9ARM.ch11.html#rfcs" title="Request for Comments (RFCs)">the section called “Request for Comments (RFCs)”</a>.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2567271"></a>Zones</h3></div></div></div>
-<p>
+<a name="id-1.2.7.6"></a>Zones</h3></div></div></div>
+
+ <p>
To properly operate a name server, it is important to understand
the difference between a <span class="emphasis"><em>zone</em></span>
and a <span class="emphasis"><em>domain</em></span>.
</p>
-<p>
+
+ <p>
As stated previously, a zone is a point of delegation in
the <acronym class="acronym">DNS</acronym> tree. A zone consists of
those contiguous parts of the domain
parent zone, which should be matched by equivalent NS records at
the root of the delegated zone.
</p>
-<p>
+
+ <p>
For instance, consider the <code class="literal">example.com</code>
domain which includes names
such as <code class="literal">host.aaa.example.com</code> and
gain a complete understanding of this difficult and subtle
topic.
</p>
-<p>
+
+ <p>
Though <acronym class="acronym">BIND</acronym> is called a "domain name
server",
it deals primarily in terms of zones. The master and slave
be a slave server for your <span class="emphasis"><em>domain</em></span>, you are
actually asking for slave service for some collection of zones.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2567348"></a>Authoritative Name Servers</h3></div></div></div>
-<p>
+<a name="id-1.2.7.7"></a>Authoritative Name Servers</h3></div></div></div>
+
+
+ <p>
Each zone is served by at least
one <span class="emphasis"><em>authoritative name server</em></span>,
which contains the complete data for the zone.
most zones have two or more authoritative servers, on
different networks.
</p>
-<p>
+
+ <p>
Responses from authoritative servers have the "authoritative
answer" (AA) bit set in the response packets. This makes them
easy to identify when debugging DNS configurations using tools like
- <span><strong class="command">dig</strong></span> (<a href="Bv9ARM.ch03.html#diagnostic_tools" title="Diagnostic Tools">the section called “Diagnostic Tools”</a>).
+ <span class="command"><strong>dig</strong></span> (<a class="xref" href="Bv9ARM.ch03.html#diagnostic_tools" title="Diagnostic Tools">the section called “Diagnostic Tools”</a>).
</p>
-<div class="sect3" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2567371"></a>The Primary Master</h4></div></div></div>
-<p>
+<a name="id-1.2.7.7.5"></a>The Primary Master</h4></div></div></div>
+
+
+ <p>
The authoritative server where the master copy of the zone
data is maintained is called the
<span class="emphasis"><em>primary master</em></span> server, or simply the
<span class="emphasis"><em>zone file</em></span> or
<span class="emphasis"><em>master file</em></span>.
</p>
-<p>
+
+ <p>
In some cases, however, the master file may not be edited
by humans at all, but may instead be the result of
<span class="emphasis"><em>dynamic update</em></span> operations.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2567401"></a>Slave Servers</h4></div></div></div>
-<p>
+<a name="id-1.2.7.7.6"></a>Slave Servers</h4></div></div></div>
+
+ <p>
The other authoritative servers, the <span class="emphasis"><em>slave</em></span>
servers (also known as <span class="emphasis"><em>secondary</em></span> servers)
load
to transfer it from another slave. In other words, a slave server
may itself act as a master to a subordinate slave server.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2567422"></a>Stealth Servers</h4></div></div></div>
-<p>
+<a name="id-1.2.7.7.7"></a>Stealth Servers</h4></div></div></div>
+
+
+ <p>
Usually all of the zone's authoritative servers are listed in
NS records in the parent zone. These NS records constitute
a <span class="emphasis"><em>delegation</em></span> of the zone from the parent.
list servers in the parent's delegation that are not present at
the zone's top level.
</p>
-<p>
+
+ <p>
A <span class="emphasis"><em>stealth server</em></span> is a server that is
authoritative for a zone but is not listed in that zone's NS
records. Stealth servers can be used for keeping a local copy of
are
inaccessible.
</p>
-<p>
+
+ <p>
A configuration where the primary master server itself is a
stealth server is often referred to as a "hidden primary"
configuration. One use for this configuration is when the primary
is behind a firewall and therefore unable to communicate directly
with the outside world.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2567589"></a>Caching Name Servers</h3></div></div></div>
-<p>
+<a name="id-1.2.7.8"></a>Caching Name Servers</h3></div></div></div>
+
+
+
+
+
+ <p>
The resolver libraries provided by most operating systems are
<span class="emphasis"><em>stub resolvers</em></span>, meaning that they are not
capable of
is called a <span class="emphasis"><em>recursive</em></span> name server; it performs
<span class="emphasis"><em>recursive lookups</em></span> for local clients.
</p>
-<p>
+
+ <p>
To improve performance, recursive servers cache the results of
the lookups they perform. Since the processes of recursion and
caching are intimately connected, the terms
<span class="emphasis"><em>recursive server</em></span> and
<span class="emphasis"><em>caching server</em></span> are often used synonymously.
</p>
-<p>
+
+ <p>
The length of time for which a record may be retained in
the cache of a caching name server is controlled by the
Time To Live (TTL) field associated with each resource record.
</p>
-<div class="sect3" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2567624"></a>Forwarding</h4></div></div></div>
-<p>
+<a name="id-1.2.7.8.6"></a>Forwarding</h4></div></div></div>
+
+
+ <p>
Even a caching name server does not necessarily perform
the complete recursive lookup itself. Instead, it can
<span class="emphasis"><em>forward</em></span> some or all of the queries
server,
commonly referred to as a <span class="emphasis"><em>forwarder</em></span>.
</p>
-<p>
+
+ <p>
There may be one or more forwarders,
and they are queried in turn until the list is exhausted or an
answer
that can do it, and that server would query the Internet <acronym class="acronym">DNS</acronym> servers
on the internal server's behalf.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2567651"></a>Name Servers in Multiple Roles</h3></div></div></div>
-<p>
+<a name="id-1.2.7.9"></a>Name Servers in Multiple Roles</h3></div></div></div>
+
+
+ <p>
The <acronym class="acronym">BIND</acronym> name server can
simultaneously act as
a master for some zones, a slave for other zones, and as a caching
(recursive) server for a set of local clients.
</p>
-<p>
+
+ <p>
However, since the functions of authoritative name service
and caching/recursive name service are logically separate, it is
often advantageous to run them on separate server machines.
does not need to be reachable from the Internet at large and can
be placed inside a firewall.
</p>
-</div>
-</div>
-</div>
+
+ </div>
+ </div>
+
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 2. BIND Resource Requirements</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch01.html" title="Chapter 1. Introduction">
<link rel="next" href="Bv9ARM.ch03.html" title="Chapter 3. Name Server Configuration">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch02"></a>Chapter 2. <acronym class="acronym">BIND</acronym> Resource Requirements</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch02"></a>Chapter 2. <acronym class="acronym">BIND</acronym> Resource Requirements</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567685">Hardware requirements</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567712">CPU Requirements</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567793">Memory Requirements</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567819">Name Server Intensive Environment Issues</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567830">Supported Operating Systems</a></span></dt>
+<dl class="toc">
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.3">Hardware requirements</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.4">CPU Requirements</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.5">Memory Requirements</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.6">Name Server Intensive Environment Issues</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.7">Supported Operating Systems</a></span></dt>
</dl>
</div>
-<div class="sect1" lang="en">
+
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2567685"></a>Hardware requirements</h2></div></div></div>
-<p>
+<a name="id-1.3.3"></a>Hardware requirements</h2></div></div></div>
+
+
+ <p>
<acronym class="acronym">DNS</acronym> hardware requirements have
traditionally been quite modest.
For many installations, servers that have been pensioned off from
active duty have performed admirably as <acronym class="acronym">DNS</acronym> servers.
</p>
-<p>
The DNSSEC features of <acronym class="acronym">BIND</acronym> 9
may prove to be quite
CPU intensive however, so organizations that make heavy use of these
full utilization of
multiprocessor systems for installations that need it.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2567712"></a>CPU Requirements</h2></div></div></div>
-<p>
+<a name="id-1.3.4"></a>CPU Requirements</h2></div></div></div>
+
+ <p>
CPU requirements for <acronym class="acronym">BIND</acronym> 9 range from
i486-class machines
for serving of static zones without caching, to enterprise-class
machines if you intend to process many dynamic updates and DNSSEC
signed zones, serving many thousands of queries per second.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2567793"></a>Memory Requirements</h2></div></div></div>
-<p>
+<a name="id-1.3.5"></a>Memory Requirements</h2></div></div></div>
+
+ <p>
The memory of the server has to be large enough to fit the
- cache and zones loaded off disk. The <span><strong class="command">max-cache-size</strong></span>
+ cache and zones loaded off disk. The <span class="command"><strong>max-cache-size</strong></span>
option can be used to limit the amount of memory used by the cache,
at the expense of reducing cache hit rates and causing more <acronym class="acronym">DNS</acronym>
traffic.
Additionally, if additional section caching
- (<a href="Bv9ARM.ch06.html#acache" title="Additional Section Caching">the section called “Additional Section Caching”</a>) is enabled,
- the <span><strong class="command">max-acache-size</strong></span> option can be used to
+ (<a class="xref" href="Bv9ARM.ch06.html#acache" title="Additional Section Caching">the section called “Additional Section Caching”</a>) is enabled,
+ the <span class="command"><strong>max-acache-size</strong></span> option can be used to
limit the amount
of memory used by the mechanism.
It is still good practice to have enough memory to load
a relatively stable size where entries are expiring from the cache as
fast as they are being inserted.
</p>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2567819"></a>Name Server Intensive Environment Issues</h2></div></div></div>
-<p>
+<a name="id-1.3.6"></a>Name Server Intensive Environment Issues</h2></div></div></div>
+
+ <p>
For name server intensive environments, there are two alternative
configurations that may be used. The first is where clients and
any second-level internal name servers query a main name server, which
this has the disadvantage of making many more external queries,
as none of the name servers share their cached data.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2567830"></a>Supported Operating Systems</h2></div></div></div>
-<p>
+<a name="id-1.3.7"></a>Supported Operating Systems</h2></div></div></div>
+
+ <p>
ISC <acronym class="acronym">BIND</acronym> 9 compiles and runs on a large
number
of Unix-like operating systems and on
directory
of the BIND 9 source distribution.
</p>
-</div>
-</div>
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 3. Name Server Configuration</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch02.html" title="Chapter 2. BIND Resource Requirements">
<link rel="next" href="Bv9ARM.ch04.html" title="Chapter 4. Advanced DNS Features">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch03"></a>Chapter 3. Name Server Configuration</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch03"></a>Chapter 3. Name Server Configuration</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt>
+<dl class="toc">
+<dt><span class="sect
ion"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2567998">A Caching-only Name Server</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568014">An Authoritative-only Name Server</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.4.3">A Caching-only Name Server</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.4.4">An Authoritative-only Name Server</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568037">Load Balancing</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568391">Name Server Operations</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5">Load Balancing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.6">Name Server Operations</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568396">Tools for Use With the Name Server Daemon</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2569465">Signals</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.6.3">Tools for Use With the Name Server Daemon</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.6.4">Signals</a></span></dt>
</dl></dd>
</dl>
</div>
-<p>
+
+ <p>
In this chapter we provide some suggested configurations along
with guidelines for their use. We suggest reasonable values for
certain option settings.
</p>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="sample_configuration"></a>Sample Configurations</h2></div></div></div>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2567998"></a>A Caching-only Name Server</h3></div></div></div>
-<p>
+<a name="id-1.4.4.3"></a>A Caching-only Name Server</h3></div></div></div>
+
+ <p>
The following sample configuration is appropriate for a caching-only
name server for use by clients internal to a corporation. All
queries
- from outside clients are refused using the <span><strong class="command">allow-query</strong></span>
+ from outside clients are refused using the <span class="command"><strong>allow-query</strong></span>
option. Alternatively, the same effect could be achieved using
suitable
firewall rules.
</p>
+
<pre class="programlisting">
// Two corporate subnets we wish to allow queries from.
acl corpnets { 192.168.4.0/24; 192.168.7.0/24; };
notify no;
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2568014"></a>An Authoritative-only Name Server</h3></div></div></div>
-<p>
+<a name="id-1.4.4.4"></a>An Authoritative-only Name Server</h3></div></div></div>
+
+ <p>
This sample configuration is for an authoritative-only server
that is the master server for "<code class="filename">example.com</code>"
and a slave for the subdomain "<code class="filename">eng.example.com</code>".
</p>
+
<pre class="programlisting">
options {
// Working directory
masters { 192.168.4.12; };
};
</pre>
-</div>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2568037"></a>Load Balancing</h2></div></div></div>
-<p>
+<a name="id-1.4.5"></a>Load Balancing</h2></div></div></div>
+
+
+
+ <p>
A primitive form of load balancing can be achieved in
the <acronym class="acronym">DNS</acronym> by using multiple records
(such as multiple A records) for one name.
</p>
-<p>
+
+ <p>
For example, if you have three WWW servers with network addresses
of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the
following means that clients will connect to each machine one third
of the time:
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
-<col>
-<col>
-<col>
+<col width="0.875in" class="1">
+<col width="0.500in" class="2">
+<col width="0.750in" class="3">
+<col width="0.750in" class="4">
+<col width="2.028in" class="5">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
When a resolver queries for these records, <acronym class="acronym">BIND</acronym> will rotate
them and respond to the query with the records in a different
order. In the example above, clients will randomly receive
records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients
will use the first record returned and discard the rest.
</p>
-<p>
For more detail on ordering responses, check 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>.
+ <span class="command"><strong>rrset-order</strong></span> sub-statement in the
+ <span class="command"><strong>options</strong></span> statement, see
+ <a class="xref" href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">RRset Ordering</a>.
</p>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2568391"></a>Name Server Operations</h2></div></div></div>
-<div class="sect2" lang="en">
+<a name="id-1.4.6"></a>Name Server Operations</h2></div></div></div>
+
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2568396"></a>Tools for Use With the Name Server Daemon</h3></div></div></div>
-<p>
+<a name="id-1.4.6.3"></a>Tools for Use With the Name Server Daemon</h3></div></div></div>
+
+ <p>
This section describes several indispensable diagnostic,
administrative and monitoring tools available to the system
administrator for controlling and debugging the name server
daemon.
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="diagnostic_tools"></a>Diagnostic Tools</h4></div></div></div>
-<p>
- The <span><strong class="command">dig</strong></span>, <span><strong class="command">host</strong></span>, and
- <span><strong class="command">nslookup</strong></span> programs are all command
+
+ <p>
+ The <span class="command"><strong>dig</strong></span>, <span class="command"><strong>host</strong></span>, and
+ <span class="command"><strong>nslookup</strong></span> programs are all command
line tools
for manually querying name servers. They differ in style and
output format.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><a name="dig"></a><span><strong class="command">dig</strong></span></span></dt>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><a name="dig"></a><span class="command"><strong>dig</strong></span></span></dt>
<dd>
-<p>
- The domain information groper (<span><strong class="command">dig</strong></span>)
+ The domain information groper (<span class="command"><strong>dig</strong></span>)
is the most versatile and complete of these lookup tools.
It has two modes: simple interactive
mode for a single query, and batch mode which executes a
accessible
from the command line.
</p>
-<div class="cmdsynopsis"><p><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] <em class="replaceable"><code>domain</code></em> [<em class="replaceable"><code>query-type</code></em>] [<em class="replaceable"><code>query-class</code></em>] [+<em class="replaceable"><code>query-option</code></em>] [-<em class="replaceable"><code>dig-option</code></em>] [%<em class="replaceable"><code>comment</code></em>]</p></div>
-<p>
- The usual simple use of <span><strong class="command">dig</strong></span> will take the form
+ <div class="cmdsynopsis"><p>
+ <code class="command">dig</code>
+ [@<em class="replaceable"><code>server</code></em>]
+ <em class="replaceable"><code>domain</code></em>
+ [<em class="replaceable"><code>query-type</code></em>]
+ [<em class="replaceable"><code>query-class</code></em>]
+ [+<em class="replaceable"><code>query-option</code></em>]
+ [-<em class="replaceable"><code>dig-option</code></em>]
+ [%<em class="replaceable"><code>comment</code></em>]
+ </p></div>
+ <p>
+ The usual simple use of <span class="command"><strong>dig</strong></span> will take the form
</p>
-<p>
- <span><strong class="command">dig @server domain query-type query-class</strong></span>
+ <p class="simpara">
+ <span class="command"><strong>dig @server domain query-type query-class</strong></span>
</p>
-<p>
For more information and a list of available commands and
- options, see the <span><strong class="command">dig</strong></span> man
+ options, see the <span class="command"><strong>dig</strong></span> man
page.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">host</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>host</strong></span></span></dt>
<dd>
-<p>
- The <span><strong class="command">host</strong></span> utility emphasizes
+ The <span class="command"><strong>host</strong></span> utility emphasizes
simplicity
and ease of use. By default, it converts
between host names and Internet addresses, but its
functionality
can be extended with the use of options.
</p>
-<div class="cmdsynopsis"><p><code class="command">host</code> [-aCdlnrsTwv] [-c <em class="replaceable"><code>class</code></em>] [-N <em class="replaceable"><code>ndots</code></em>] [-t <em class="replaceable"><code>type</code></em>] [-W <em class="replaceable"><code>timeout</code></em>] [-R <em class="replaceable"><code>retries</code></em>] [-m <em class="replaceable"><code>flag</code></em>] [-4] [-6] <em class="replaceable"><code>hostname</code></em> [<em class="replaceable"><code>server</code></em>]</p></div>
-<p>
+ <div class="cmdsynopsis"><p>
+ <code class="command">host</code>
+ [-aCdlnrsTwv]
+ [-c <em class="replaceable"><code>class</code></em>]
+ [-N <em class="replaceable"><code>ndots</code></em>]
+ [-t <em class="replaceable"><code>type</code></em>]
+ [-W <em class="replaceable"><code>timeout</code></em>]
+ [-R <em class="replaceable"><code>retries</code></em>]
+ [-m <em class="replaceable"><code>flag</code></em>]
+ [-4]
+ [-6]
+ <em class="replaceable"><code>hostname</code></em>
+ [<em class="replaceable"><code>server</code></em>]
+ </p></div>
+ <p>
For more information and a list of available commands and
- options, see the <span><strong class="command">host</strong></span> man
+ options, see the <span class="command"><strong>host</strong></span> man
page.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">nslookup</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>nslookup</strong></span></span></dt>
<dd>
-<p><span><strong class="command">nslookup</strong></span>
+ <p><span class="command"><strong>nslookup</strong></span>
has two modes: interactive and
non-interactive. Interactive mode allows the user to
query name servers for information about various
the name and requested information for a host or
domain.
</p>
-<div class="cmdsynopsis"><p><code class="command">nslookup</code> [-option...] [[<em class="replaceable"><code>host-to-find</code></em>] | [- [server]]]</p></div>
-<p>
+ <div class="cmdsynopsis"><p>
+ <code class="command">nslookup</code>
+ [-option...]
+ [
+ [<em class="replaceable"><code>host-to-find</code></em>]
+ | [- [server]]
+ ]
+ </p></div>
+ <p>
Interactive mode is entered when no arguments are given (the
default name server will be used) or when the first argument
is a
Internet address
of a name server.
</p>
-<p>
Non-interactive mode is used when the name or Internet
address
of the host to be looked up is given as the first argument.
optional second argument specifies the host name or address
of a name server.
</p>
-<p>
Due to its arcane user interface and frequently inconsistent
- behavior, we do not recommend the use of <span><strong class="command">nslookup</strong></span>.
- Use <span><strong class="command">dig</strong></span> instead.
+ behavior, we do not recommend the use of <span class="command"><strong>nslookup</strong></span>.
+ Use <span class="command"><strong>dig</strong></span> instead.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="admin_tools"></a>Administrative Tools</h4></div></div></div>
-<p>
+
+ <p>
Administrative tools play an integral part in the management
of a server.
</p>
-<div class="variablelist"><dl>
+ <div class="variablelist"><dl class="variablelist">
<dt>
-<a name="named-checkconf"></a><span class="term"><span><strong class="command">named-checkconf</strong></span></span>
+<a name="named-checkconf"></a><span class="term"><span class="command"><strong>named-checkconf</strong></span></span>
</dt>
<dd>
-<p>
- The <span><strong class="command">named-checkconf</strong></span> program
+ The <span class="command"><strong>named-checkconf</strong></span> program
checks the syntax of a <code class="filename">named.conf</code> file.
</p>
-<div class="cmdsynopsis"><p><code class="command">named-checkconf</code> [-jvz] [-t <em class="replaceable"><code>directory</code></em>] [<em class="replaceable"><code>filename</code></em>]</p></div>
-</dd>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named-checkconf</code>
+ [-jvz]
+ [-t <em class="replaceable"><code>directory</code></em>]
+ [<em class="replaceable"><code>filename</code></em>]
+ </p></div>
+ </dd>
<dt>
-<a name="named-checkzone"></a><span class="term"><span><strong class="command">named-checkzone</strong></span></span>
+<a name="named-checkzone"></a><span class="term"><span class="command"><strong>named-checkzone</strong></span></span>
</dt>
<dd>
-<p>
- The <span><strong class="command">named-checkzone</strong></span> program
+ The <span class="command"><strong>named-checkzone</strong></span> program
checks a master file for
syntax and consistency.
</p>
-<div class="cmdsynopsis"><p><code class="command">named-checkzone</code> [-djqvD] [-c <em class="replaceable"><code>class</code></em>] [-o <em class="replaceable"><code>output</code></em>] [-t <em class="replaceable"><code>directory</code></em>] [-w <em class="replaceable"><code>directory</code></em>] [-k <em class="replaceable"><code>(ignore|warn|fail)</code></em>] [-n <em class="replaceable"><code>(ignore|warn|fail)</code></em>] [-W <em class="replaceable"><code>(ignore|warn)</code></em>] <em class="replaceable"><code>zone</code></em> [<em class="replaceable"><code>filename</code></em>]</p></div>
-</dd>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named-checkzone</code>
+ [-djqvD]
+ [-c <em class="replaceable"><code>class</code></em>]
+ [-o <em class="replaceable"><code>output</code></em>]
+ [-t <em class="replaceable"><code>directory</code></em>]
+ [-w <em class="replaceable"><code>directory</code></em>]
+ [-k <em class="replaceable"><code>(ignore|warn|fail)</code></em>]
+ [-n <em class="replaceable"><code>(ignore|warn|fail)</code></em>]
+ [-W <em class="replaceable"><code>(ignore|warn)</code></em>]
+ <em class="replaceable"><code>zone</code></em>
+ [<em class="replaceable"><code>filename</code></em>]
+ </p></div>
+ </dd>
<dt>
-<a name="named-compilezone"></a><span class="term"><span><strong class="command">named-compilezone</strong></span></span>
+<a name="named-compilezone"></a><span class="term"><span class="command"><strong>named-compilezone</strong></span></span>
</dt>
-<dd><p>
- Similar to <span><strong class="command">named-checkzone,</strong></span> but
+<dd>
+ <p>
+ Similar to <span class="command"><strong>named-checkzone,</strong></span> but
it always dumps the zone content to a specified file
(typically in a different format).
- </p></dd>
+ </p>
+ </dd>
<dt>
-<a name="rndc"></a><span class="term"><span><strong class="command">rndc</strong></span></span>
+<a name="rndc"></a><span class="term"><span class="command"><strong>rndc</strong></span></span>
</dt>
<dd>
-<p>
The remote name daemon control
- (<span><strong class="command">rndc</strong></span>) program allows the
+ (<span class="command"><strong>rndc</strong></span>) program allows the
system
administrator to control the operation of a name server.
- Since <acronym class="acronym">BIND</acronym> 9.2, <span><strong class="command">rndc</strong></span>
- supports all the commands of the BIND 8 <span><strong class="command">ndc</strong></span>
- utility except <span><strong class="command">ndc start</strong></span> and
- <span><strong class="command">ndc restart</strong></span>, which were also
- not supported in <span><strong class="command">ndc</strong></span>'s
+ Since <acronym class="acronym">BIND</acronym> 9.2, <span class="command"><strong>rndc</strong></span>
+ supports all the commands of the BIND 8 <span class="command"><strong>ndc</strong></span>
+ utility except <span class="command"><strong>ndc start</strong></span> and
+ <span class="command"><strong>ndc restart</strong></span>, which were also
+ not supported in <span class="command"><strong>ndc</strong></span>'s
channel mode.
- If you run <span><strong class="command">rndc</strong></span> without any
+ If you run <span class="command"><strong>rndc</strong></span> without any
options
it will display a usage message as follows:
</p>
-<div class="cmdsynopsis"><p><code class="command">rndc</code> [-c <em class="replaceable"><code>config</code></em>] [-s <em class="replaceable"><code>server</code></em>] [-p <em class="replaceable"><code>port</code></em>] [-y <em class="replaceable"><code>key</code></em>] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command</code></em>...]</p></div>
-<p>See <a href="man.rndc.html" title="rndc"><span class="refentrytitle"><span class="application">rndc</span></span>(8)</a> for details of
- the available <span><strong class="command">rndc</strong></span> commands.
+ <div class="cmdsynopsis"><p>
+ <code class="command">rndc</code>
+ [-c <em class="replaceable"><code>config</code></em>]
+ [-s <em class="replaceable"><code>server</code></em>]
+ [-p <em class="replaceable"><code>port</code></em>]
+ [-y <em class="replaceable"><code>key</code></em>]
+ <em class="replaceable"><code>command</code></em>
+ [<em class="replaceable"><code>command</code></em>...]
+ </p></div>
+
+ <p>See <a class="xref" href="man.rndc.html" title="rndc"><span class="refentrytitle"><span class="application">rndc</span></span>(8)</a> for details of
+ the available <span class="command"><strong>rndc</strong></span> commands.
</p>
-<p>
- <span><strong class="command">rndc</strong></span> requires a configuration file,
+
+ <p>
+ <span class="command"><strong>rndc</strong></span> requires a configuration file,
since all
communication with the server is authenticated with
digital signatures that rely on a shared secret, and
there is no way to provide that secret other than with a
configuration file. The default location for the
- <span><strong class="command">rndc</strong></span> configuration file is
+ <span class="command"><strong>rndc</strong></span> configuration file is
<code class="filename">/etc/rndc.conf</code>, but an
alternate
location can be specified with the <code class="option">-c</code>
option. If the configuration file is not found,
- <span><strong class="command">rndc</strong></span> will also look in
+ <span class="command"><strong>rndc</strong></span> will also look in
<code class="filename">/etc/rndc.key</code> (or whatever
<code class="varname">sysconfdir</code> was defined when
the <acronym class="acronym">BIND</acronym> build was
configured).
The <code class="filename">rndc.key</code> file is
generated by
- running <span><strong class="command">rndc-confgen -a</strong></span> as
+ running <span class="command"><strong>rndc-confgen -a</strong></span> as
described in
- <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
- Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and
+ <a class="xref" href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called “<span class="command"><strong>controls</strong></span> Statement Definition and
Usage”</a>.
</p>
-<p>
+
+ <p>
The format of the configuration file is similar to
that of <code class="filename">named.conf</code>, but
limited to
- only four statements, the <span><strong class="command">options</strong></span>,
- <span><strong class="command">key</strong></span>, <span><strong class="command">server</strong></span> and
- <span><strong class="command">include</strong></span>
+ only four statements, the <span class="command"><strong>options</strong></span>,
+ <span class="command"><strong>key</strong></span>, <span class="command"><strong>server</strong></span> and
+ <span class="command"><strong>include</strong></span>
statements. These statements are what associate the
secret keys to the servers with which they are meant to
be shared. The order of statements is not
significant.
</p>
-<p>
- The <span><strong class="command">options</strong></span> statement has
+
+ <p>
+ The <span class="command"><strong>options</strong></span> statement has
three clauses:
- <span><strong class="command">default-server</strong></span>, <span><strong class="command">default-key</strong></span>,
- and <span><strong class="command">default-port</strong></span>.
- <span><strong class="command">default-server</strong></span> takes a
+ <span class="command"><strong>default-server</strong></span>, <span class="command"><strong>default-key</strong></span>,
+ and <span class="command"><strong>default-port</strong></span>.
+ <span class="command"><strong>default-server</strong></span> takes a
host name or address argument and represents the server
that will
be contacted if no <code class="option">-s</code>
option is provided on the command line.
- <span><strong class="command">default-key</strong></span> takes
- the name of a key as its argument, as defined by a <span><strong class="command">key</strong></span> statement.
- <span><strong class="command">default-port</strong></span> specifies the
+ <span class="command"><strong>default-key</strong></span> takes
+ the name of a key as its argument, as defined by a <span class="command"><strong>key</strong></span> statement.
+ <span class="command"><strong>default-port</strong></span> specifies the
port to which
- <span><strong class="command">rndc</strong></span> should connect if no
+ <span class="command"><strong>rndc</strong></span> should connect if no
port is given on the command line or in a
- <span><strong class="command">server</strong></span> statement.
+ <span class="command"><strong>server</strong></span> statement.
</p>
-<p>
- The <span><strong class="command">key</strong></span> statement defines a
+
+ <p>
+ The <span class="command"><strong>key</strong></span> statement defines a
key to be used
- by <span><strong class="command">rndc</strong></span> when authenticating
+ by <span class="command"><strong>rndc</strong></span> when authenticating
with
- <span><strong class="command">named</strong></span>. Its syntax is
+ <span class="command"><strong>named</strong></span>. Its syntax is
identical to the
- <span><strong class="command">key</strong></span> statement in <code class="filename">named.conf</code>.
+ <span class="command"><strong>key</strong></span> statement in <code class="filename">named.conf</code>.
The keyword <strong class="userinput"><code>key</code></strong> is
followed by a key name, which must be a valid
domain name, though it need not actually be hierarchical;
thus,
a string like "<strong class="userinput"><code>rndc_key</code></strong>" is a valid
name.
- The <span><strong class="command">key</strong></span> statement has two
+ The <span class="command"><strong>key</strong></span> statement has two
clauses:
- <span><strong class="command">algorithm</strong></span> and <span><strong class="command">secret</strong></span>.
+ <span class="command"><strong>algorithm</strong></span> and <span class="command"><strong>secret</strong></span>.
While the configuration parser will accept any string as the
argument
to algorithm, currently only the strings
have any meaning. The secret is a base-64 encoded string
as specified in RFC 3548.
</p>
-<p>
- The <span><strong class="command">server</strong></span> statement
+
+ <p>
+ The <span class="command"><strong>server</strong></span> statement
associates a key
- defined using the <span><strong class="command">key</strong></span>
+ defined using the <span class="command"><strong>key</strong></span>
statement with a server.
The keyword <strong class="userinput"><code>server</code></strong> is followed by a
- host name or address. The <span><strong class="command">server</strong></span> statement
- has two clauses: <span><strong class="command">key</strong></span> and <span><strong class="command">port</strong></span>.
- The <span><strong class="command">key</strong></span> clause specifies the
+ host name or address. The <span class="command"><strong>server</strong></span> statement
+ has two clauses: <span class="command"><strong>key</strong></span> and <span class="command"><strong>port</strong></span>.
+ The <span class="command"><strong>key</strong></span> clause specifies the
name of the key
to be used when communicating with this server, and the
- <span><strong class="command">port</strong></span> clause can be used to
- specify the port <span><strong class="command">rndc</strong></span> should
+ <span class="command"><strong>port</strong></span> clause can be used to
+ specify the port <span class="command"><strong>rndc</strong></span> should
connect
to on the server.
</p>
-<p>
+
+ <p>
A sample minimal configuration file is as follows:
</p>
+
<pre class="programlisting">
key rndc_key {
algorithm "hmac-sha256";
default-key rndc_key;
};
</pre>
-<p>
+
+ <p>
This file, if installed as <code class="filename">/etc/rndc.conf</code>,
would allow the command:
</p>
-<p>
+
+ <p>
<code class="prompt">$ </code><strong class="userinput"><code>rndc reload</code></strong>
</p>
-<p>
+
+ <p>
to connect to 127.0.0.1 port 953 and cause the name server
to reload, if a name server on the local machine were
running with
following controls statements:
</p>
+
<pre class="programlisting">
controls {
inet 127.0.0.1
allow { localhost; } keys { rndc_key; };
};
</pre>
-<p>
+
+ <p>
and it had an identical key statement for
<code class="literal">rndc_key</code>.
</p>
-<p>
- Running the <span><strong class="command">rndc-confgen</strong></span>
+
+ <p>
+ Running the <span class="command"><strong>rndc-confgen</strong></span>
program will
conveniently create a <code class="filename">rndc.conf</code>
file for you, and also display the
- corresponding <span><strong class="command">controls</strong></span>
+ corresponding <span class="command"><strong>controls</strong></span>
statement that you need to
add to <code class="filename">named.conf</code>.
Alternatively,
- you can run <span><strong class="command">rndc-confgen -a</strong></span>
+ you can run <span class="command"><strong>rndc-confgen -a</strong></span>
to set up
a <code class="filename">rndc.key</code> file and not
modify
<code class="filename">named.conf</code> at all.
</p>
-</dd>
+
+ </dd>
</dl></div>
-</div>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2569465"></a>Signals</h3></div></div></div>
-<p>
+<a name="id-1.4.6.4"></a>Signals</h3></div></div></div>
+
+
+ <p>
Certain UNIX signals cause the name server to take specific
actions, as described in the following table. These signals can
- be sent using the <span><strong class="command">kill</strong></span> command.
+ be sent using the <span class="command"><strong>kill</strong></span> command.
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.125in" class="1">
+<col width="4.000in" class="2">
</colgroup>
<tbody>
<tr>
<td>
- <p><span><strong class="command">SIGHUP</strong></span></p>
+ <p><span class="command"><strong>SIGHUP</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">SIGTERM</strong></span></p>
+ <p><span class="command"><strong>SIGTERM</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">SIGINT</strong></span></p>
+ <p><span class="command"><strong>SIGINT</strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
-</div>
-</div>
-</div>
+</table>
+ </div>
+ </div>
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 4. Advanced DNS Features</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch03.html" title="Chapter 3. Name Server Configuration">
<link rel="next" href="Bv9ARM.ch05.html" title="Chapter 5. The BIND 9 Lightweight Resolver">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch04"></a>Chapter 4. Advanced DNS Features</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch04"></a>Chapter 4. Advanced DNS Features</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#notify">Notify</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
-<dd><dl><dt><span class="sect
2"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2569988">Split DNS</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570006">Example split DNS setup</a></span></dt></dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
+<dl class="toc">
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#notify">Notify</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
+<dd><dl><dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6">Split DNS</a></span></dt>
+<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.6">Example split DNS setup</a></span></dt></dl></dd>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570439">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570581">Copying the Shared Secret to Both Machines</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570592">Informing the Servers of the Key's Existence</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570628">Instructing the Server to Use the Key</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570685">TSIG Key Based Access Control</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570734">Errors</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.6">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.7">Copying the Shared Secret to Both Machines</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.8">Informing the Servers of the Key's Existence</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.9">Instructing the Server to Use the Key</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.10">TSIG Key Based Access Control</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.11">Errors</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570748">TKEY</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570866">SIG(0)</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.8">TKEY</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9">SIG(0)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571002">Generating Keys</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571218">Signing the Zone</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571299">Configuring Servers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.7">Generating Keys</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.8">Signing the Zone</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.9">Configuring Servers</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613607">Converting from insecure to secure</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613644">Dynamic DNS update method</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563573">Fully automatic zone signing</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563820">Private-type records</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573415">DNSKEY rollovers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573428">Dynamic DNS update method</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573461">Automatic key rollovers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573488">NSEC3PARAM rollovers via UPDATE</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573497">Converting from NSEC to NSEC3</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573507">Converting from NSEC3 to NSEC</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573520">Converting from secure to insecure</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573557">Periodic re-signing</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573571">NSEC3 and OPTOUT</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.4">Converting from insecure to secure</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.9">Dynamic DNS update method</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.17">Fully automatic zone signing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.26">Private-type records</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.33">DNSKEY rollovers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.35">Dynamic DNS update method</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.40">Automatic key rollovers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.42">NSEC3PARAM rollovers via UPDATE</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.44">Converting from NSEC to NSEC3</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.46">Converting from NSEC3 to NSEC</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.48">Converting from secure to insecure</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.52">Periodic re-signing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.54">NSEC3 and OPTOUT</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#rfc5011.support">Dynamic Trust Anchor Management</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#rfc5011.support">Dynamic Trust Anchor Management</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573594">Validating Resolver</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573617">Authoritative Server</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.4">Validating Resolver</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.5">Authoritative Server</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#pkcs11">PKCS#11 (Cryptoki) support</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#pkcs11">PKCS#11 (Cryptoki) support</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613795">Prerequisites</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613804">Native PKCS#11</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613950">OpenSSL-based PKCS#11</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641062">PKCS#11 Tools</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641098">Using the HSM</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641452">Specifying the engine on the command line</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641500">Running named with automatic zone re-signing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.7">Prerequisites</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.8">Native PKCS#11</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.9">OpenSSL-based PKCS#11</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.10">PKCS#11 Tools</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.11">Using the HSM</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.12">Specifying the engine on the command line</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.13">Running named with automatic zone re-signing</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dlz-info">DLZ (Dynamically Loadable Zones)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dlz-info">DLZ (Dynamically Loadable Zones)</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613331">Configuring DLZ</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613473">Sample DLZ Driver</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.14.7">Configuring DLZ</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.14.8">Sample DLZ Driver</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dyndb-info">DynDB (Dynamic Database)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dyndb-info">DynDB (Dynamic Database)</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2668419">Configuring DynDB</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2614349">Sample DynDB Module</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.15.6">Configuring DynDB</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.15.7">Sample DynDB Module</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#id2571527">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#id-1.5.16">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571794">Address Lookups Using AAAA Records</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571815">Address to Name Lookups Using Nibble Format</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.16.7">Address Lookups Using AAAA Records</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.16.8">Address to Name Lookups Using Nibble Format</a></span></dt>
</dl></dd>
</dl>
</div>
-<div class="sect1" lang="en">
+
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="notify"></a>Notify</h2></div></div></div>
-<p>
+
+
+ <p>
<acronym class="acronym">DNS</acronym> NOTIFY is a mechanism that allows master
servers to notify their slave servers of changes to a zone's data. In
- response to a <span><strong class="command">NOTIFY</strong></span> from a master server, the
+ response to a <span class="command"><strong>NOTIFY</strong></span> from a master server, the
slave will check to see that its version of the zone is the
current version and, if not, initiate a zone transfer.
</p>
-<p>
+
+ <p>
For more information about <acronym class="acronym">DNS</acronym>
- <span><strong class="command">NOTIFY</strong></span>, see the description of the
- <span><strong class="command">notify</strong></span> option in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a> and
- the description of the zone option <span><strong class="command">also-notify</strong></span> in
- <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. The <span><strong class="command">NOTIFY</strong></span>
+ <span class="command"><strong>NOTIFY</strong></span>, see the description of the
+ <span class="command"><strong>notify</strong></span> option in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a> and
+ the description of the zone option <span class="command"><strong>also-notify</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. The <span class="command"><strong>NOTIFY</strong></span>
protocol is specified in RFC 1996.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
- As a slave zone can also be a master to other slaves, <span><strong class="command">named</strong></span>,
- by default, sends <span><strong class="command">NOTIFY</strong></span> messages for every zone
- it loads. Specifying <span><strong class="command">notify master-only;</strong></span> will
- cause <span><strong class="command">named</strong></span> to only send <span><strong class="command">NOTIFY</strong></span> for master
+ As a slave zone can also be a master to other slaves, <span class="command"><strong>named</strong></span>,
+ by default, sends <span class="command"><strong>NOTIFY</strong></span> messages for every zone
+ it loads. Specifying <span class="command"><strong>notify master-only;</strong></span> will
+ cause <span class="command"><strong>named</strong></span> to only send <span class="command"><strong>NOTIFY</strong></span> for master
zones that it loads.
</div>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="dynamic_update"></a>Dynamic Update</h2></div></div></div>
-<p>
+
+
+ <p>
Dynamic Update is a method for adding, replacing or deleting
records in a master server by sending it a special form of DNS
messages. The format and meaning of these messages is specified
in RFC 2136.
</p>
-<p>
+
+ <p>
Dynamic update is enabled by including an
- <span><strong class="command">allow-update</strong></span> or an <span><strong class="command">update-policy</strong></span>
- clause in the <span><strong class="command">zone</strong></span> statement.
+ <span class="command"><strong>allow-update</strong></span> or an <span class="command"><strong>update-policy</strong></span>
+ clause in the <span class="command"><strong>zone</strong></span> statement.
</p>
-<p>
- If the zone's <span><strong class="command">update-policy</strong></span> is set to
+
+ <p>
+ If the zone's <span class="command"><strong>update-policy</strong></span> is set to
<strong class="userinput"><code>local</code></strong>, updates to the zone
will be permitted for the key <code class="varname">local-ddns</code>,
- which will be generated by <span><strong class="command">named</strong></span> at startup.
- See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for more details.
+ which will be generated by <span class="command"><strong>named</strong></span> at startup.
+ See <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for more details.
</p>
-<p>
+
+ <p>
Dynamic updates using Kerberos signed requests can be made
using the TKEY/GSS protocol by setting either the
- <span><strong class="command">tkey-gssapi-keytab</strong></span> option, or alternatively
- by setting both the <span><strong class="command">tkey-gssapi-credential</strong></span>
- and <span><strong class="command">tkey-domain</strong></span> options. Once enabled,
+ <span class="command"><strong>tkey-gssapi-keytab</strong></span> option, or alternatively
+ by setting both the <span class="command"><strong>tkey-gssapi-credential</strong></span>
+ and <span class="command"><strong>tkey-domain</strong></span> options. Once enabled,
Kerberos signed requests will be matched against the update
policies for the zone, using the Kerberos principal as the
signer for the request.
</p>
-<p>
+
+ <p>
Updating of secure zones (zones using DNSSEC) follows RFC
3007: RRSIG, NSEC and NSEC3 records affected by updates are
automatically regenerated by the server using an online
zone key. Update authorization is based on transaction
signatures and an explicit server policy.
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="journal"></a>The journal file</h3></div></div></div>
-<p>
+
+
+ <p>
All changes made to a zone using dynamic update are stored
in the zone's journal file. This file is automatically created
by the server when the first dynamic update takes place.
file unless specifically overridden. The journal file is in a
binary format and should not be edited manually.
</p>
-<p>
+
+ <p>
The server will also occasionally write ("dump")
the complete contents of the updated zone to its zone file.
This is not done immediately after
will be removed when the dump is complete, and can be safely
ignored.
</p>
-<p>
+
+ <p>
When a server is restarted after a shutdown or crash, it will replay
the journal file to incorporate into the zone any updates that
took
place after the last zone dump.
</p>
-<p>
+
+ <p>
Changes that result from incoming incremental zone transfers are
also
journalled in a similar way.
</p>
-<p>
+
+ <p>
The zone files of dynamic zones cannot normally be edited by
hand because they are not guaranteed to contain the most recent
dynamic changes — those are only in the journal file.
The only way to ensure that the zone file of a dynamic zone
- is up to date is to run <span><strong class="command">rndc stop</strong></span>.
+ is up to date is to run <span class="command"><strong>rndc stop</strong></span>.
</p>
-<p>
+
+ <p>
If you have to make changes to a dynamic zone
manually, the following procedure will work:
Disable dynamic updates to the zone using
- <span><strong class="command">rndc freeze <em class="replaceable"><code>zone</code></em></strong></span>.
+ <span class="command"><strong>rndc freeze <em class="replaceable"><code>zone</code></em></strong></span>.
This will update the zone's master file with the changes
stored in its <code class="filename">.jnl</code> file.
Edit the zone file. Run
- <span><strong class="command">rndc thaw <em class="replaceable"><code>zone</code></em></strong></span>
+ <span class="command"><strong>rndc thaw <em class="replaceable"><code>zone</code></em></strong></span>
to reload the changed zone and re-enable dynamic updates.
</p>
-<p>
- <span><strong class="command">rndc sync <em class="replaceable"><code>zone</code></em></strong></span>
+
+ <p>
+ <span class="command"><strong>rndc sync <em class="replaceable"><code>zone</code></em></strong></span>
will update the zone file with changes from the journal file
without stopping dynamic updates; this may be useful for viewing
the current zone state. To remove the <code class="filename">.jnl</code>
file after updating the zone file, use
- <span><strong class="command">rndc sync -clean</strong></span>.
+ <span class="command"><strong>rndc sync -clean</strong></span>.
</p>
-</div>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="incremental_zone_transfers"></a>Incremental Zone Transfers (IXFR)</h2></div></div></div>
-<p>
+
+
+ <p>
The incremental zone transfer (IXFR) protocol is a way for
slave servers to transfer only changed data, instead of having to
transfer the entire zone. The IXFR protocol is specified in RFC
- 1995. See <a href="Bv9ARM.ch11.html#proposed_standards">Proposed Standards</a>.
+ 1995. See <a class="xref" href="Bv9ARM.ch11.html#proposed_standards" title="Proposed Standards">Proposed Standards</a>.
</p>
-<p>
+
+ <p>
When acting as a master, <acronym class="acronym">BIND</acronym> 9
supports IXFR for those zones
where the necessary change history information is available. These
whose data was obtained by IXFR. For manually maintained master
zones, and for slave zones obtained by performing a full zone
transfer (AXFR), IXFR is supported only if the option
- <span><strong class="command">ixfr-from-differences</strong></span> is set
+ <span class="command"><strong>ixfr-from-differences</strong></span> is set
to <strong class="userinput"><code>yes</code></strong>.
</p>
-<p>
+
+ <p>
When acting as a slave, <acronym class="acronym">BIND</acronym> 9 will
attempt to use IXFR unless
it is explicitly disabled. For more information about disabling
- IXFR, see the description of the <span><strong class="command">request-ixfr</strong></span> clause
- of the <span><strong class="command">server</strong></span> statement.
+ IXFR, see the description of the <span class="command"><strong>request-ixfr</strong></span> clause
+ of the <span class="command"><strong>server</strong></span> statement.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2569988"></a>Split DNS</h2></div></div></div>
-<p>
+<a name="id-1.5.6"></a>Split DNS</h2></div></div></div>
+
+ <p>
Setting up different views, or visibility, of the DNS space to
internal and external resolvers is usually referred to as a
<span class="emphasis"><em>Split DNS</em></span> setup. There are several
reasons an organization would want to set up its DNS this way.
</p>
-<p>
One common reason for setting up a DNS system this way is
to hide "internal" DNS information from "external" clients on the
Internet. There is some debate as to whether or not this is actually
choose to use a Split DNS to present a consistent view of itself
to the outside world.
</p>
-<p>
Another common reason for setting up a Split DNS system is
to allow internal networks that are behind filters or in RFC 1918
space (reserved IP space, as documented in RFC 1918) to resolve DNS
on the Internet. Split DNS can also be used to allow mail from outside
back in to the internal network.
</p>
-<div class="sect2" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2570006"></a>Example split DNS setup</h3></div></div></div>
-<p>
+<a name="id-1.5.6.6"></a>Example split DNS setup</h3></div></div></div>
+
+ <p>
Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span>
(<code class="literal">example.com</code>)
has several corporate sites that have an internal network with
Internet Protocol (IP) space and an external demilitarized zone (DMZ),
or "outside" section of a network, that is available to the public.
</p>
-<p>
<span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients
to be able to resolve external hostnames and to exchange mail with
people on the outside. The company also wants its internal resolvers
to have access to certain internal-only zones that are not available
at all outside of the internal network.
</p>
-<p>
In order to accomplish this, the company will set up two sets
of name servers. One set will be on the inside network (in the
reserved
"proxy"
hosts that can talk to both sides of its network, in the DMZ.
</p>
-<p>
The internal servers will be configured to forward all queries,
except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>,
and <code class="filename">site2.example.com</code>, to the servers
for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>, <code class="filename">site1.internal</code>,
and <code class="filename">site2.internal</code>.
</p>
-<p>
To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains,
the internal name servers must be configured to disallow all queries
to these domains from any external hosts, including the bastion
hosts.
</p>
-<p>
The external servers, which are on the bastion hosts, will
be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones.
This could include things such as the host records for public servers
(<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>),
and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>).
</p>
-<p>
In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones
should have special MX records that contain wildcard (`*') records
pointing to the bastion hosts. This is needed because external mail
be delivered to the bastion host, which can then forward it on to
internal hosts.
</p>
-<p>
Here's an example of a wildcard MX record:
</p>
-<pre class="programlisting">* IN MX 10 external1.example.com.</pre>
-<p>
+
<pre class="programlisting">* IN MX 10 external1.example.com.</pre>
Now that they accept mail on behalf of anything in the internal
network, the bastion hosts will need to know how to deliver mail
to internal hosts. In order for this to work properly, the resolvers
the bastion hosts will need to be configured to point to the internal
name servers for DNS resolution.
</p>
-<p>
Queries for internal hostnames will be answered by the internal
servers, and queries for external hostnames will be forwarded back
out to the DNS servers on the bastion hosts.
</p>
-<p>
In order for all this to work properly, internal clients will
need to be configured to query <span class="emphasis"><em>only</em></span> the internal
name servers for DNS queries. This could also be enforced via
selective
filtering on the network.
</p>
-<p>
If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s
internal clients will now be able to:
</p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+
Look up any hostnames in the <code class="literal">site1</code>
and
<code class="literal">site2.example.com</code> zones.
- </li>
-<li>
+
+ </li>
+<li class="listitem">
+
Look up any hostnames in the <code class="literal">site1.internal</code> and
<code class="literal">site2.internal</code> domains.
- </li>
-<li>Look up any hostnames on the Internet.</li>
-<li>Exchange mail with both internal and external people.</li>
+
+ </li>
+<li class="listitem">
+ Look up any hostnames on the Internet.
+ </li>
+<li class="listitem">
+ Exchange mail with both internal and external people.
+ </li>
</ul></div>
-<p>
Hosts on the Internet will be able to:
</p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+
Look up any hostnames in the <code class="literal">site1</code>
and
<code class="literal">site2.example.com</code> zones.
- </li>
-<li>
+
+ </li>
+<li class="listitem">
+
Exchange mail with anyone in the <code class="literal">site1</code> and
<code class="literal">site2.example.com</code> zones.
- </li>
+
+ </li>
</ul></div>
-<p>
+
+ <p>
Here is an example configuration for the setup we just
described above. Note that this is only configuration information;
- for information on how to configure your zone files, see <a href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>.
+ for information on how to configure your zone files, see <a class="xref" href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>.
</p>
-<p>
+
+ <p>
Internal DNS server config:
</p>
+
<pre class="programlisting">
acl internals { 172.16.72.0/24; 192.168.1.0/24; };
allow-transfer { internals; }
};
</pre>
-<p>
+
+ <p>
External (bastion host) DNS server config:
</p>
+
<pre class="programlisting">
acl internals { 172.16.72.0/24; 192.168.1.0/24; };
allow-transfer { internals; externals; }
};
</pre>
-<p>
+
+ <p>
In the <code class="filename">resolv.conf</code> (or equivalent) on
the bastion host(s):
</p>
+
<pre class="programlisting">
search ...
nameserver 172.16.72.2
nameserver 172.16.72.3
nameserver 172.16.72.4
</pre>
-</div>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="tsig"></a>TSIG</h2></div></div></div>
-<p>
+
+ <p>
This is a short guide to setting up Transaction SIGnatures
(TSIG) based transaction security in <acronym class="acronym">BIND</acronym>. It describes changes
to the configuration file as well as what changes are required for
different features, including the process of creating transaction
keys and using transaction signatures with <acronym class="acronym">BIND</acronym>.
</p>
-<p>
<acronym class="acronym">BIND</acronym> primarily supports TSIG for server
to server communication.
This includes zone transfer, notify, and recursive query messages.
Resolvers based on newer versions of <acronym class="acronym">BIND</acronym> 8 have limited support
for TSIG.
</p>
-<p>
+
+ <p>
TSIG can also be useful for dynamic update. A primary
server for a dynamic zone should control access to the dynamic
update service, but IP-based access control is insufficient.
The cryptographic access control provided by TSIG
- is far superior. The <span><strong class="command">nsupdate</strong></span>
+ is far superior. The <span class="command"><strong>nsupdate</strong></span>
program supports TSIG via the <code class="option">-k</code> and
<code class="option">-y</code> command line options or inline by use
- of the <span><strong class="command">key</strong></span>.
+ of the <span class="command"><strong>key</strong></span>.
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2570439"></a>Generate Shared Keys for Each Pair of Hosts</h3></div></div></div>
-<p>
+<a name="id-1.5.7.6"></a>Generate Shared Keys for Each Pair of Hosts</h3></div></div></div>
+
+ <p>
A shared secret is generated to be shared between <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host2</em></span>.
An arbitrary key name is chosen: "host1-host2.". The key name must
be the same on both hosts.
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2570524"></a>Automatic Generation</h4></div></div></div>
-<p>
+<a name="id-1.5.7.6.4"></a>Automatic Generation</h4></div></div></div>
+
+ <p>
The following command will generate a 128-bit (16 byte) HMAC-SHA256
key as described above. Longer keys are better, but shorter keys
are easier to read. Note that the maximum key length is the digest
length, here 256 bits.
</p>
-<p>
<strong class="userinput"><code>dnssec-keygen -a hmac-sha256 -b 128 -n HOST host1-host2.</code></strong>
</p>
-<p>
The key is in the file <code class="filename">Khost1-host2.+163+00000.private</code>.
Nothing directly uses this file, but the base-64 encoded string
following "<code class="literal">Key:</code>"
can be extracted from the file and used as a shared secret:
</p>
-<pre class="programlisting">Key: La/E5CjG9O+os1jq0a2jdA==</pre>
-<p>
+
<pre class="programlisting">Key: La/E5CjG9O+os1jq0a2jdA==</pre>
The string "<code class="literal">La/E5CjG9O+os1jq0a2jdA==</code>" can
be used as the shared secret.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2570563"></a>Manual Generation</h4></div></div></div>
-<p>
+<a name="id-1.5.7.6.5"></a>Manual Generation</h4></div></div></div>
+
+ <p>
The shared secret is simply a random sequence of bits, encoded
in base-64. Most ASCII strings are valid base-64 strings (assuming
the length is a multiple of 4 and only valid characters are used),
so the shared secret can be manually generated.
</p>
-<p>
- Also, a known string can be run through <span><strong class="command">mmencode</strong></span> or
+ Also, a known string can be run through <span class="command"><strong>mmencode</strong></span> or
a similar program to generate base-64 encoded data.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2570581"></a>Copying the Shared Secret to Both Machines</h3></div></div></div>
-<p>
+<a name="id-1.5.7.7"></a>Copying the Shared Secret to Both Machines</h3></div></div></div>
+
+ <p>
This is beyond the scope of DNS. A secure transport mechanism
should be used. This could be secure FTP, ssh, telephone, etc.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2570592"></a>Informing the Servers of the Key's Existence</h3></div></div></div>
-<p>
+<a name="id-1.5.7.8"></a>Informing the Servers of the Key's Existence</h3></div></div></div>
+
+ <p>
Imagine <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host 2</em></span>
are
both servers. The following is added to each server's <code class="filename">named.conf</code> file:
</p>
+
<pre class="programlisting">
key host1-host2. {
algorithm hmac-sha256;
secret "La/E5CjG9O+os1jq0a2jdA==";
};
</pre>
-<p>
+
+ <p>
The secret is the one generated above. Since this is a secret, it
is recommended that either <code class="filename">named.conf</code> be
non-world readable, or the key directive be added to a non-world
readable file that is included by <code class="filename">named.conf</code>.
</p>
-<p>
At this point, the key is recognized. This means that if the
server receives a message signed by this key, it can verify the
signature. If the signature is successfully verified, the
response is signed by the same key.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2570628"></a>Instructing the Server to Use the Key</h3></div></div></div>
-<p>
+<a name="id-1.5.7.9"></a>Instructing the Server to Use the Key</h3></div></div></div>
+
+ <p>
Since keys are shared between two hosts only, the server must
be told when keys are to be used. The following is added to the <code class="filename">named.conf</code> file
for <span class="emphasis"><em>host1</em></span>, if the IP address of <span class="emphasis"><em>host2</em></span> is
10.1.2.3:
</p>
+
<pre class="programlisting">
server 10.1.2.3 {
keys { host1-host2. ;};
};
</pre>
-<p>
+
+ <p>
Multiple keys may be present, but only the first is used.
This directive does not contain any secrets, so it may be in a
world-readable
file.
</p>
-<p>
If <span class="emphasis"><em>host1</em></span> sends a message that is a request
to that address, the message will be signed with the specified key. <span class="emphasis"><em>host1</em></span> will
expect any responses to signed messages to be signed with the same
key.
</p>
-<p>
A similar statement must be present in <span class="emphasis"><em>host2</em></span>'s
configuration file (with <span class="emphasis"><em>host1</em></span>'s address) for <span class="emphasis"><em>host2</em></span> to
sign request messages to <span class="emphasis"><em>host1</em></span>.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2570685"></a>TSIG Key Based Access Control</h3></div></div></div>
-<p>
+<a name="id-1.5.7.10"></a>TSIG Key Based Access Control</h3></div></div></div>
+
+ <p>
<acronym class="acronym">BIND</acronym> allows IP addresses and ranges
to be specified in ACL
definitions and
- <span><strong class="command">allow-{ query | transfer | update }</strong></span>
+ <span class="command"><strong>allow-{ query | transfer | update }</strong></span>
directives.
This has been extended to allow TSIG keys also. The above key would
- be denoted <span><strong class="command">key host1-host2.</strong></span>
+ be denoted <span class="command"><strong>key host1-host2.</strong></span>
</p>
-<p>
- An example of an <span><strong class="command">allow-update</strong></span> directive would be:
+ An example of an <span class="command"><strong>allow-update</strong></span> directive would be:
</p>
+
<pre class="programlisting">
allow-update { key host1-host2. ;};
</pre>
-<p>
+
+ <p>
This allows dynamic updates to succeed only if the request
- was signed by a key named "<span><strong class="command">host1-host2.</strong></span>".
+ was signed by a key named "<span class="command"><strong>host1-host2.</strong></span>".
</p>
-<p>
- See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for a discussion of
- the more flexible <span><strong class="command">update-policy</strong></span> statement.
+
+ <p>
+ See <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for a discussion of
+ the more flexible <span class="command"><strong>update-policy</strong></span> statement.
</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2570734"></a>Errors</h3></div></div></div>
-<p>
+<a name="id-1.5.7.11"></a>Errors</h3></div></div></div>
+
+
+ <p>
The processing of TSIG signed messages can result in
several errors. If a signed message is sent to a non-TSIG aware
server, a FORMERR (format error) will be returned, since the server will not
since the server must be explicitly configured to send a TSIG
signed message to a specific server.
</p>
-<p>
+
+ <p>
If a TSIG aware server receives a message signed by an
unknown key, the response will be unsigned with the TSIG
extended error code set to BADKEY. If a TSIG aware server
verified. In any of these cases, the message's rcode (response code) is set to
NOTAUTH (not authenticated).
</p>
-</div>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2570748"></a>TKEY</h2></div></div></div>
-<p><span><strong class="command">TKEY</strong></span>
+<a name="id-1.5.8"></a>TKEY</h2></div></div></div>
+
+
+ <p><span class="command"><strong>TKEY</strong></span>
is a mechanism for automatically generating a shared secret
between two hosts. There are several "modes" of
- <span><strong class="command">TKEY</strong></span> that specify how the key is generated
+ <span class="command"><strong>TKEY</strong></span> that specify how the key is generated
or assigned. <acronym class="acronym">BIND</acronym> 9 implements only one of
these modes, the Diffie-Hellman key exchange. Both hosts are
required to have a Diffie-Hellman KEY record (although this
record is not required to be present in a zone). The
- <span><strong class="command">TKEY</strong></span> process must use signed messages,
+ <span class="command"><strong>TKEY</strong></span> process must use signed messages,
signed either by TSIG or SIG(0). The result of
- <span><strong class="command">TKEY</strong></span> is a shared secret that can be used to
- sign messages with TSIG. <span><strong class="command">TKEY</strong></span> can also be
+ <span class="command"><strong>TKEY</strong></span> is a shared secret that can be used to
+ sign messages with TSIG. <span class="command"><strong>TKEY</strong></span> can also be
used to delete shared secrets that it had previously
generated.
</p>
-<p>
- The <span><strong class="command">TKEY</strong></span> process is initiated by a
+
+ <p>
+ The <span class="command"><strong>TKEY</strong></span> process is initiated by a
client
- or server by sending a signed <span><strong class="command">TKEY</strong></span>
+ or server by sending a signed <span class="command"><strong>TKEY</strong></span>
query
(including any appropriate KEYs) to a TKEY-aware server. The
server response, if it indicates success, will contain a
- <span><strong class="command">TKEY</strong></span> record and any appropriate keys.
+ <span class="command"><strong>TKEY</strong></span> record and any appropriate keys.
After
this exchange, both participants have enough information to
determine the shared secret; the exact process depends on the
- <span><strong class="command">TKEY</strong></span> mode. When using the
+ <span class="command"><strong>TKEY</strong></span> mode. When using the
Diffie-Hellman
- <span><strong class="command">TKEY</strong></span> mode, Diffie-Hellman keys are
+ <span class="command"><strong>TKEY</strong></span> mode, Diffie-Hellman keys are
exchanged,
and the shared secret is derived by both participants.
</p>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2570866"></a>SIG(0)</h2></div></div></div>
-<p>
+<a name="id-1.5.9"></a>SIG(0)</h2></div></div></div>
+
+
+ <p>
<acronym class="acronym">BIND</acronym> 9 partially supports DNSSEC SIG(0)
transaction signatures as specified in RFC 2535 and RFC 2931.
SIG(0)
is performed in the same manner as TSIG keys; privileges can be
granted or denied based on the key name.
</p>
-<p>
+
+ <p>
When a SIG(0) signed message is received, it will only be
verified if the key is known and trusted by the server; the server
will not attempt to locate and/or validate the key.
</p>
-<p>
+
+ <p>
SIG(0) signing of multiple-message TCP streams is not
supported.
</p>
-<p>
+
+ <p>
The only tool shipped with <acronym class="acronym">BIND</acronym> 9 that
- generates SIG(0) signed messages is <span><strong class="command">nsupdate</strong></span>.
+ generates SIG(0) signed messages is <span class="command"><strong>nsupdate</strong></span>.
</p>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="DNSSEC"></a>DNSSEC</h2></div></div></div>
-<p>
+
+
+ <p>
Cryptographic authentication of DNS information is possible
through the DNS Security (<span class="emphasis"><em>DNSSEC-bis</em></span>) extensions,
defined in RFC 4033, RFC 4034, and RFC 4035.
This section describes the creation and use of DNSSEC signed zones.
</p>
-<p>
+
+ <p>
In order to set up a DNSSEC secure zone, there are a series
of steps which must be followed. <acronym class="acronym">BIND</acronym>
9 ships
that the tools shipped with BIND 9.2.x and earlier are not compatible
with the current ones.
</p>
-<p>
+
+ <p>
There must also be communication with the administrators of
the parent and/or child zone to transmit keys. A zone's security
status must be indicated by the parent zone for a DNSSEC capable
delegation
point.
</p>
-<p>
+
+ <p>
For other servers to trust data in this zone, they must
either be statically configured with this zone's zone key or the
zone key of another zone above this one in the DNS tree.
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2571002"></a>Generating Keys</h3></div></div></div>
-<p>
- The <span><strong class="command">dnssec-keygen</strong></span> program is used to
+<a name="id-1.5.10.7"></a>Generating Keys</h3></div></div></div>
+
+
+ <p>
+ The <span class="command"><strong>dnssec-keygen</strong></span> program is used to
generate keys.
</p>
-<p>
+
+ <p>
A secure zone must contain one or more zone keys. The
zone keys will sign all other records in the zone, as well as
the zone keys of any secure delegated zones. Zone keys must
have the same name as the zone, a name type of
- <span><strong class="command">ZONE</strong></span>, and must be usable for
+ <span class="command"><strong>ZONE</strong></span>, and must be usable for
authentication.
It is recommended that zone keys use a cryptographic algorithm
designated as "mandatory to implement" by the IETF; currently
the only one is RSASHA1.
</p>
-<p>
+
+ <p>
The following command will generate a 768-bit RSASHA1 key for
the <code class="filename">child.example</code> zone:
</p>
-<p>
+
+ <p>
<strong class="userinput"><code>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</code></strong>
</p>
-<p>
+
+ <p>
Two output files will be produced:
<code class="filename">Kchild.example.+005+12345.key</code> and
<code class="filename">Kchild.example.+005+12345.private</code>
<code class="filename">.key</code> file) is used for signature
verification.
</p>
-<p>
+
+ <p>
To generate another key with the same properties (but with
a different key tag), repeat the above command.
</p>
-<p>
- The <span><strong class="command">dnssec-keyfromlabel</strong></span> program is used
+
+ <p>
+ The <span class="command"><strong>dnssec-keyfromlabel</strong></span> program is used
to get a key pair from a crypto hardware and build the key
- files. Its usage is similar to <span><strong class="command">dnssec-keygen</strong></span>.
+ files. Its usage is similar to <span class="command"><strong>dnssec-keygen</strong></span>.
</p>
-<p>
+
+ <p>
The public keys should be inserted into the zone file by
including the <code class="filename">.key</code> files using
- <span><strong class="command">$INCLUDE</strong></span> statements.
+ <span class="command"><strong>$INCLUDE</strong></span> statements.
</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2571218"></a>Signing the Zone</h3></div></div></div>
-<p>
- The <span><strong class="command">dnssec-signzone</strong></span> program is used
+<a name="id-1.5.10.8"></a>Signing the Zone</h3></div></div></div>
+
+
+ <p>
+ The <span class="command"><strong>dnssec-signzone</strong></span> program is used
to sign a zone.
</p>
-<p>
+
+ <p>
Any <code class="filename">keyset</code> files corresponding to
secure subzones should be present. The zone signer will
generate <code class="literal">NSEC</code>, <code class="literal">NSEC3</code>
is not specified, then DS RRsets for the secure child
zones need to be added manually.
</p>
-<p>
+
+ <p>
The following command signs the zone, assuming it is in a
file called <code class="filename">zone.child.example</code>. By
default, all zone keys which have an available private key are
used to generate signatures.
</p>
-<p>
+
+ <p>
<strong class="userinput"><code>dnssec-signzone -o child.example zone.child.example</code></strong>
</p>
-<p>
+
+ <p>
One output file is produced:
<code class="filename">zone.child.example.signed</code>. This
file
as the
input file for the zone.
</p>
-<p><span><strong class="command">dnssec-signzone</strong></span>
+
+ <p><span class="command"><strong>dnssec-signzone</strong></span>
will also produce a keyset and dsset files and optionally a
dlvset file. These are used to provide the parent zone
administrators with the <code class="literal">DNSKEYs</code> (or their
corresponding <code class="literal">DS</code> records) that are the
secure entry point to the zone.
</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2571299"></a>Configuring Servers</h3></div></div></div>
-<p>
- To enable <span><strong class="command">named</strong></span> to respond appropriately
+<a name="id-1.5.10.9"></a>Configuring Servers</h3></div></div></div>
+
+
+ <p>
+ To enable <span class="command"><strong>named</strong></span> to respond appropriately
to DNS requests from DNSSEC aware clients,
- <span><strong class="command">dnssec-enable</strong></span> must be set to yes.
+ <span class="command"><strong>dnssec-enable</strong></span> must be set to yes.
(This is the default setting.)
</p>
-<p>
- To enable <span><strong class="command">named</strong></span> to validate answers from
- other servers, the <span><strong class="command">dnssec-enable</strong></span> option
+
+ <p>
+ To enable <span class="command"><strong>named</strong></span> to validate answers from
+ other servers, the <span class="command"><strong>dnssec-enable</strong></span> option
must be set to <strong class="userinput"><code>yes</code></strong>, and the
- <span><strong class="command">dnssec-validation</strong></span> options must be set to
+ <span class="command"><strong>dnssec-validation</strong></span> options must be set to
<strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>auto</code></strong>.
</p>
-<p>
- If <span><strong class="command">dnssec-validation</strong></span> is set to
+
+ <p>
+ If <span class="command"><strong>dnssec-validation</strong></span> is set to
<strong class="userinput"><code>auto</code></strong>, then a default
trust anchor for the DNS root zone will be used.
If it is set to <strong class="userinput"><code>yes</code></strong>, however,
then at least one trust anchor must be configured
- with a <span><strong class="command">trusted-keys</strong></span> or
- <span><strong class="command">managed-keys</strong></span> statement in
+ with a <span class="command"><strong>trusted-keys</strong></span> or
+ <span class="command"><strong>managed-keys</strong></span> statement in
<code class="filename">named.conf</code>, or DNSSEC validation
will not occur. The default setting is
<strong class="userinput"><code>yes</code></strong>.
</p>
-<p>
- <span><strong class="command">trusted-keys</strong></span> are copies of DNSKEY RRs
+
+ <p>
+ <span class="command"><strong>trusted-keys</strong></span> are copies of DNSKEY RRs
for zones that are used to form the first link in the
cryptographic chain of trust. All keys listed in
- <span><strong class="command">trusted-keys</strong></span> (and corresponding zones)
+ <span class="command"><strong>trusted-keys</strong></span> (and corresponding zones)
are deemed to exist and only the listed keys will be used
to validated the DNSKEY RRset that they are from.
</p>
-<p>
- <span><strong class="command">managed-keys</strong></span> are trusted keys which are
+
+ <p>
+ <span class="command"><strong>managed-keys</strong></span> are trusted keys which are
automatically kept up to date via RFC 5011 trust anchor
maintenance.
</p>
-<p>
- <span><strong class="command">trusted-keys</strong></span> and
- <span><strong class="command">managed-keys</strong></span> are described in more detail
+
+ <p>
+ <span class="command"><strong>trusted-keys</strong></span> and
+ <span class="command"><strong>managed-keys</strong></span> are described in more detail
later in this document.
</p>
-<p>
+
+ <p>
Unlike <acronym class="acronym">BIND</acronym> 8, <acronym class="acronym">BIND</acronym>
9 does not verify signatures on load, so zone keys for
authoritative zones do not need to be specified in the
configuration file.
</p>
-<p>
+
+ <p>
After DNSSEC gets established, a typical DNSSEC configuration
will look something like the following. It has one or
more public keys for the root. This allows answers from
outside the organization to be validated. It will also
have several keys for parts of the namespace the organization
- controls. These are here to ensure that <span><strong class="command">named</strong></span>
+ controls. These are here to ensure that <span class="command"><strong>named</strong></span>
is immune to compromises in the DNSSEC components of the security
of parent zones.
</p>
+
<pre class="programlisting">
managed-keys {
/* Root Key */
dnssec-validation yes;
};
</pre>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
None of the keys listed in this example are valid. In particular,
the root key is not valid.
</div>
-<p>
+
+ <p>
When DNSSEC validation is enabled and properly configured,
the resolver will reject any answers from signed, secure zones
which fail to validate, and will return SERVFAIL to the client.
</p>
-<p>
+
+ <p>
Responses may fail to validate for any of several reasons,
including missing, expired, or invalid signatures, a key which
does not match the DS RRset in the parent zone, or an insecure
response from a zone which, according to its parent, should have
been secure.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
When the validator receives a response from an unsigned zone
that has a signed parent, it must confirm with the parent
that the zone was intentionally left unsigned. It does
this by verifying, via signed and validated NSEC/NSEC3 records,
that the parent zone contains no DS records for the child.
</p>
-<p>
If the validator <span class="emphasis"><em>can</em></span> prove that the zone
is insecure, then the response is accepted. However, if it
cannot, then it must assume an insecure response to be a
forgery; it rejects the response and logs an error.
</p>
-<p>
The logged error reads "insecurity proof failed" and
"got insecure response; parent indicates it should be secure".
(Prior to BIND 9.7, the logged error was "not insecure".
This referred to the zone, not the response.)
</p>
-</div>
-</div>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="dnssec.dynamic.zones"></a>DNSSEC, Dynamic Zones, and Automatic Signing</h2></div></div></div>
-<p>As of BIND 9.7.0 it is possible to change a dynamic zone
+
+ <p>As of BIND 9.7.0 it is possible to change a dynamic zone
from insecure to signed and back again. A secure zone can use
either NSEC or NSEC3 chains.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2613607"></a>Converting from insecure to secure</h3></div></div></div></div>
-<p>Changing a zone from insecure to secure can be done in two
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.4"></a>Converting from insecure to secure</h3></div></div></div>
+
+ </div>
+ <p>Changing a zone from insecure to secure can be done in two
ways: using a dynamic DNS update, or the
- <span><strong class="command">auto-dnssec</strong></span> zone option.</p>
-<p>For either method, you need to configure
- <span><strong class="command">named</strong></span> so that it can see the
+ <span class="command"><strong>auto-dnssec</strong></span> zone option.</p>
+
<p>For either method, you need to configure
+ <span class="command"><strong>named</strong></span> so that it can see the
<code class="filename">K*</code> files which contain the public and private
parts of the keys that will be used to sign the zone. These files
will have been generated by
- <span><strong class="command">dnssec-keygen</strong></span>. You can do this by placing them
+ <span class="command"><strong>dnssec-keygen</strong></span>. You can do this by placing them
in the key-directory, as specified in
<code class="filename">named.conf</code>:</p>
-<pre class="programlisting">
- zone example.net {
- type master;
- update-policy local;
- file "dynamic/example.net/example.net";
- key-directory "dynamic/example.net";
- };
+
<pre class="programlisting">
+ zone example.net {
+ type master;
+ update-policy local;
+ file "dynamic/example.net/example.net";
+ key-directory "dynamic/example.net";
+ };
</pre>
-<p>If one KSK and one ZSK DNSKEY key have been generated, this
+
<p>If one KSK and one ZSK DNSKEY key have been generated, this
configuration will cause all records in the zone to be signed
with the ZSK, and the DNSKEY RRset to be signed with the KSK as
well. An NSEC chain will be generated as part of the initial
signing process.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2613644"></a>Dynamic DNS update method</h3></div></div></div></div>
-<p>To insert the keys via dynamic update:</p>
-<pre class="screen">
- % nsupdate
- > ttl 3600
- > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
- > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
- > send
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.9"></a>Dynamic DNS update method</h3></div></div></div>
+
+ </div>
+ <p>To insert the keys via dynamic update:</p>
+ <pre class="screen">
+ % nsupdate
+ > ttl 3600
+ > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+ > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+ > send
</pre>
-<p>While the update request will complete almost immediately,
+
<p>While the update request will complete almost immediately,
the zone will not be completely signed until
- <span><strong class="command">named</strong></span> has had time to walk the zone and
+ <span class="command"><strong>named</strong></span> has had time to walk the zone and
generate the NSEC and RRSIG records. The NSEC record at the apex
will be added last, to signal that there is a complete NSEC
chain.</p>
-<p>If you wish to sign using NSEC3 instead of NSEC, you should
+
<p>If you wish to sign using NSEC3 instead of NSEC, you should
add an NSEC3PARAM record to the initial update request. If you
wish the NSEC3 chain to have the OPTOUT bit set, set it in the
flags field of the NSEC3PARAM record.</p>
-<pre class="screen">
- % nsupdate
- > ttl 3600
- > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
- > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
- > update add example.net NSEC3PARAM 1 1 100 1234567890
- > send
+ % nsupdate
+ > ttl 3600
+ > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+ > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+ > update add example.net NSEC3PARAM 1 1 100 1234567890
+ > send
</pre>
-<p>Again, this update request will complete almost
+
<p>Again, this update request will complete almost
immediately; however, the record won't show up until
- <span><strong class="command">named</strong></span> has had a chance to build/remove the
+ <span class="command"><strong>named</strong></span> has had a chance to build/remove the
relevant chain. A private type record will be created to record
the state of the operation (see below for more details), and will
be removed once the operation completes.</p>
-<p>While the initial signing and NSEC/NSEC3 chain generation
+
<p>While the initial signing and NSEC/NSEC3 chain generation
is happening, other updates are possible as well.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2563573"></a>Fully automatic zone signing</h3></div></div></div></div>
-<p>To enable automatic signing, add the
- <span><strong class="command">auto-dnssec</strong></span> option to the zone statement in
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.17"></a>Fully automatic zone signing</h3></div></div></div>
+
+ </div>
+ <p>To enable automatic signing, add the
+ <span class="command"><strong>auto-dnssec</strong></span> option to the zone statement in
<code class="filename">named.conf</code>.
- <span><strong class="command">auto-dnssec</strong></span> has two possible arguments:
+ <span class="command"><strong>auto-dnssec</strong></span> has two possible arguments:
<code class="constant">allow</code> or
<code class="constant">maintain</code>.</p>
-<p>With
- <span><strong class="command">auto-dnssec allow</strong></span>,
- <span><strong class="command">named</strong></span> can search the key directory for keys
+ <span class="command"><strong>auto-dnssec allow</strong></span>,
+ <span class="command"><strong>named</strong></span> can search the key directory for keys
matching the zone, insert them into the zone, and use them to
sign the zone. It will do so only when it receives an
- <span><strong class="command">rndc sign <zonename></strong></span>.</p>
-<p>
+ <span class="command"><strong>rndc sign <zonename></strong></span>.</p>
- <span><strong class="command">auto-dnssec maintain</strong></span> includes the above
+ <span class="command"><strong>auto-dnssec maintain</strong></span> includes the above
functionality, but will also automatically adjust the zone's
DNSKEY records on schedule according to the keys' timing metadata.
- (See <a href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
- <a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a> for more information.)
+ (See <a class="xref" href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
+ <a class="xref" href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a> for more information.)
</p>
-<p>
- <span><strong class="command">named</strong></span> will periodically search the key directory
+ <span class="command"><strong>named</strong></span> will periodically search the key directory
for keys matching the zone, and if the keys' metadata indicates
that any change should be made the zone, such as adding, removing,
or revoking a key, then that action will be carried out. By default,
the key directory is checked for changes every 60 minutes; this period
can be adjusted with the <code class="option">dnssec-loadkeys-interval</code>, up
- to a maximum of 24 hours. The <span><strong class="command">rndc loadkeys</strong></span> forces
- <span><strong class="command">named</strong></span> to check for key updates immediately.
+ to a maximum of 24 hours. The <span class="command"><strong>rndc loadkeys</strong></span> forces
+ <span class="command"><strong>named</strong></span> to check for key updates immediately.
</p>
-<p>
If keys are present in the key directory the first time the zone
is loaded, the zone will be signed immediately, without waiting for an
- <span><strong class="command">rndc sign</strong></span> or <span><strong class="command">rndc loadkeys</strong></span>
+ <span class="command"><strong>rndc sign</strong></span> or <span class="command"><strong>rndc loadkeys</strong></span>
command. (Those commands can still be used when there are unscheduled
key changes, however.)
</p>
-<p>
When new keys are added to a zone, the TTL is set to match that
of any existing DNSKEY RRset. If there is no existing DNSKEY RRset,
then the TTL will be set to the TTL specified when the key was
- created (using the <span><strong class="command">dnssec-keygen -L</strong></span> option), if
+ created (using the <span class="command"><strong>dnssec-keygen -L</strong></span> option), if
any, or to the SOA TTL.
</p>
-<p>
If you wish the zone to be signed using NSEC3 instead of NSEC,
submit an NSEC3PARAM record via dynamic update prior to the
scheduled publication and activation of the keys. If you wish the
the zone is signed and the NSEC3 chain is completed, the NSEC3PARAM
record will appear in the zone.
</p>
-<p>Using the
- <span><strong class="command">auto-dnssec</strong></span> option requires the zone to be
+ <span class="command"><strong>auto-dnssec</strong></span> option requires the zone to be
configured to allow dynamic updates, by adding an
- <span><strong class="command">allow-update</strong></span> or
- <span><strong class="command">update-policy</strong></span> statement to the zone
+ <span class="command"><strong>allow-update</strong></span> or
+ <span class="command"><strong>update-policy</strong></span> statement to the zone
configuration. If this has not been done, the configuration will
fail.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2563820"></a>Private-type records</h3></div></div></div></div>
-<p>The state of the signing process is signaled by
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.26"></a>Private-type records</h3></div></div></div>
+
+ </div>
+ <p>The state of the signing process is signaled by
private-type records (with a default type value of 65534). When
signing is complete, these records will have a nonzero value for
the final octet (for those records which have a nonzero initial
octet).</p>
-<p>The private type record format: If the first octet is
+
<p>The private type record format: If the first octet is
non-zero then the record indicates that the zone needs to be
signed with the key matching the record, or that all signatures
that match the record should be removed.</p>
-<p>
</p>
<div class="literallayout"><p><br>
<br>
</p></div>
<p>
</p>
-<p>Only records flagged as "complete" can be removed via
+
<p>Only records flagged as "complete" can be removed via
dynamic update. Attempts to remove other private type records
will be silently ignored.</p>
-<p>If the first octet is zero (this is a reserved algorithm
+
<p>If the first octet is zero (this is a reserved algorithm
number that should never appear in a DNSKEY record) then the
record indicates changes to the NSEC3 chains are in progress. The
rest of the record contains an NSEC3PARAM record. The flag field
tells what operation to perform based on the flag bits.</p>
-<p>
</p>
<div class="literallayout"><p><br>
<br>
</p></div>
<p>
</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573415"></a>DNSKEY rollovers</h3></div></div></div></div>
-<p>As with insecure-to-secure conversions, rolling DNSSEC
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.33"></a>DNSKEY rollovers</h3></div></div></div>
+
+ </div>
+ <p>As with insecure-to-secure conversions, rolling DNSSEC
keys can be done in two ways: using a dynamic DNS update, or the
- <span><strong class="command">auto-dnssec</strong></span> zone option.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573428"></a>Dynamic DNS update method</h3></div></div></div></div>
-<p> To perform key rollovers via dynamic update, you need to add
+ <span class="command"><strong>auto-dnssec</strong></span> zone option.</p>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.35"></a>Dynamic DNS update method</h3></div></div></div>
+
+ </div>
+ <p> To perform key rollovers via dynamic update, you need to add
the <code class="filename">K*</code> files for the new keys so that
- <span><strong class="command">named</strong></span> can find them. You can then add the new
+ <span class="command"><strong>named</strong></span> can find them. You can then add the new
DNSKEY RRs via dynamic update.
- <span><strong class="command">named</strong></span> will then cause the zone to be signed
+ <span class="command"><strong>named</strong></span> will then cause the zone to be signed
with the new keys. When the signing is complete the private type
records will be updated so that the last octet is non
zero.</p>
-<p>If this is for a KSK you need to inform the parent and any
+
<p>If this is for a KSK you need to inform the parent and any
trust anchor repositories of the new KSK.</p>
-<p>You should then wait for the maximum TTL in the zone before
+
<p>You should then wait for the maximum TTL in the zone before
removing the old DNSKEY. If it is a KSK that is being updated,
you also need to wait for the DS RRset in the parent to be
updated and its TTL to expire. This ensures that all clients will
be able to verify at least one signature when you remove the old
DNSKEY.</p>
-<p>The old DNSKEY can be removed via UPDATE. Take care to
+
<p>The old DNSKEY can be removed via UPDATE. Take care to
specify the correct key.
- <span><strong class="command">named</strong></span> will clean out any signatures generated
+ <span class="command"><strong>named</strong></span> will clean out any signatures generated
by the old key after the update completes.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573461"></a>Automatic key rollovers</h3></div></div></div></div>
-<p>When a new key reaches its activation date (as set by
- <span><strong class="command">dnssec-keygen</strong></span> or <span><strong class="command">dnssec-settime</strong></span>),
- if the <span><strong class="command">auto-dnssec</strong></span> zone option is set to
- <code class="constant">maintain</code>, <span><strong class="command">named</strong></span> will
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.40"></a>Automatic key rollovers</h3></div></div></div>
+
+ </div>
+ <p>When a new key reaches its activation date (as set by
+ <span class="command"><strong>dnssec-keygen</strong></span> or <span class="command"><strong>dnssec-settime</strong></span>),
+ if the <span class="command"><strong>auto-dnssec</strong></span> zone option is set to
+ <code class="constant">maintain</code>, <span class="command"><strong>named</strong></span> will
automatically carry out the key rollover. If the key's algorithm
has not previously been used to sign the zone, then the zone will
be fully signed as quickly as possible. However, if the new key
signature validity periods expire. By default, this rollover
completes in 30 days, after which it will be safe to remove the
old key from the DNSKEY RRset.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573488"></a>NSEC3PARAM rollovers via UPDATE</h3></div></div></div></div>
-<p>Add the new NSEC3PARAM record via dynamic update. When the
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.42"></a>NSEC3PARAM rollovers via UPDATE</h3></div></div></div>
+
+ </div>
+ <p>Add the new NSEC3PARAM record via dynamic update. When the
new NSEC3 chain has been generated, the NSEC3PARAM flag field
will be zero. At this point you can remove the old NSEC3PARAM
record. The old chain will be removed after the update request
completes.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573497"></a>Converting from NSEC to NSEC3</h3></div></div></div></div>
-<p>To do this, you just need to add an NSEC3PARAM record. When
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.44"></a>Converting from NSEC to NSEC3</h3></div></div></div>
+
+ </div>
+ <p>To do this, you just need to add an NSEC3PARAM record. When
the conversion is complete, the NSEC chain will have been removed
and the NSEC3PARAM record will have a zero flag field. The NSEC3
chain will be generated before the NSEC chain is
destroyed.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573507"></a>Converting from NSEC3 to NSEC</h3></div></div></div></div>
-<p>To do this, use <span><strong class="command">nsupdate</strong></span> to
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.46"></a>Converting from NSEC3 to NSEC</h3></div></div></div>
+
+ </div>
+ <p>To do this, use <span class="command"><strong>nsupdate</strong></span> to
remove all NSEC3PARAM records with a zero flag
field. The NSEC chain will be generated before the NSEC3 chain is
removed.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573520"></a>Converting from secure to insecure</h3></div></div></div></div>
-<p>To convert a signed zone to unsigned using dynamic DNS,
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.48"></a>Converting from secure to insecure</h3></div></div></div>
+
+ </div>
+ <p>To convert a signed zone to unsigned using dynamic DNS,
delete all the DNSKEY records from the zone apex using
- <span><strong class="command">nsupdate</strong></span>. All signatures, NSEC or NSEC3 chains,
+ <span class="command"><strong>nsupdate</strong></span>. All signatures, NSEC or NSEC3 chains,
and associated NSEC3PARAM records will be removed automatically.
This will take place after the update request completes.</p>
-<p> This requires the
- <span><strong class="command">dnssec-secure-to-insecure</strong></span> option to be set to
+ <span class="command"><strong>dnssec-secure-to-insecure</strong></span> option to be set to
<strong class="userinput"><code>yes</code></strong> in
<code class="filename">named.conf</code>.</p>
-<p>In addition, if the <span><strong class="command">auto-dnssec maintain</strong></span>
+ <p>In addition, if the <span class="command"><strong>auto-dnssec maintain</strong></span>
zone statement is used, it should be removed or changed to
- <span><strong class="command">allow</strong></span> instead (or it will re-sign).
+ <span class="command"><strong>allow</strong></span> instead (or it will re-sign).
</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573557"></a>Periodic re-signing</h3></div></div></div></div>
-<p>In any secure zone which supports dynamic updates, <span><strong class="command">named</strong></span>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.52"></a>Periodic re-signing</h3></div></div></div>
+
+ </div>
+ <p>In any secure zone which supports dynamic updates, <span class="command"><strong>named</strong></span>
will periodically re-sign RRsets which have not been re-signed as
a result of some update action. The signature lifetimes will be
adjusted so as to spread the re-sign load over time rather than
all at once.</p>
-<div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title">
-<a name="id2573571"></a>NSEC3 and OPTOUT</h3></div></div></div></div>
-<p>
- <span><strong class="command">named</strong></span> only supports creating new NSEC3 chains
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id-1.5.11.54"></a>NSEC3 and OPTOUT</h3></div></div></div>
+
+ </div>
+ <p>
+ <span class="command"><strong>named</strong></span> only supports creating new NSEC3 chains
where all the NSEC3 records in the zone have the same OPTOUT
state.
- <span><strong class="command">named</strong></span> supports UPDATES to zones where the NSEC3
+ <span class="command"><strong>named</strong></span> supports UPDATES to zones where the NSEC3
records in the chain have mixed OPTOUT state.
- <span><strong class="command">named</strong></span> does not support changing the OPTOUT
+ <span class="command"><strong>named</strong></span> does not support changing the OPTOUT
state of an individual NSEC3 record, the entire chain needs to be
changed if the OPTOUT state of an individual NSEC3 needs to be
changed.</p>
</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="rfc5011.support"></a>Dynamic Trust Anchor Management</h2></div></div></div>
-<p>BIND 9.7.0 introduces support for RFC 5011, dynamic trust
+
+ <p>BIND 9.7.0 introduces support for RFC 5011, dynamic trust
anchor management. Using this feature allows
- <span><strong class="command">named</strong></span> to keep track of changes to critical
+ <span class="command"><strong>named</strong></span> to keep track of changes to critical
DNSSEC keys without any need for the operator to make changes to
configuration files.</p>
-<div class="sect2" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2573594"></a>Validating Resolver</h3></div></div></div>
-<p>To configure a validating resolver to use RFC 5011 to
+<a name="id-1.5.12.4"></a>Validating Resolver</h3></div></div></div>
+
+
+ <p>To configure a validating resolver to use RFC 5011 to
maintain a trust anchor, configure the trust anchor using a
- <span><strong class="command">managed-keys</strong></span> statement. Information about
+ <span class="command"><strong>managed-keys</strong></span> statement. Information about
this can be found in
- <a href="Bv9ARM.ch06.html#managed-keys" title="managed-keys Statement Definition
- and Usage">the section called “<span><strong class="command">managed-keys</strong></span> Statement Definition
+ <a class="xref" href="Bv9ARM.ch06.html#managed-keys" title="managed-keys Statement Definition and Usage">the section called “<span class="command"><strong>managed-keys</strong></span> Statement Definition
and Usage”</a>.</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2573617"></a>Authoritative Server</h3></div></div></div>
-<p>To set up an authoritative zone for RFC 5011 trust anchor
+<a name="id-1.5.12.5"></a>Authoritative Server</h3></div></div></div>
+
+ <p>To set up an authoritative zone for RFC 5011 trust anchor
maintenance, generate two (or more) key signing keys (KSKs) for
the zone. Sign the zone with one of them; this is the "active"
KSK. All KSKs which do not sign the zone are "stand-by"
keys.</p>
-<p>Any validating resolver which is configured to use the
+
<p>Any validating resolver which is configured to use the
active KSK as an RFC 5011-managed trust anchor will take note
of the stand-by KSKs in the zone's DNSKEY RRset, and store them
for future reference. The resolver will recheck the zone
anchor for the zone. Any time after this 30-day acceptance
timer has completed, the active KSK can be revoked, and the
zone can be "rolled over" to the newly accepted key.</p>
-<p>The easiest way to place a stand-by key in a zone is to
+
<p>The easiest way to place a stand-by key in a zone is to
use the "smart signing" features of
- <span><strong class="command">dnssec-keygen</strong></span> and
- <span><strong class="command">dnssec-signzone</strong></span>. If a key with a publication
+ <span class="command"><strong>dnssec-keygen</strong></span> and
+ <span class="command"><strong>dnssec-signzone</strong></span>. If a key with a publication
date in the past, but an activation date which is unset or in
the future, "
- <span><strong class="command">dnssec-signzone -S</strong></span>" will include the DNSKEY
+ <span class="command"><strong>dnssec-signzone -S</strong></span>" will include the DNSKEY
record in the zone, but will not sign with it:</p>
-<pre class="screen">
$ <strong class="userinput"><code>dnssec-keygen -K keys -f KSK -P now -A now+2y example.net</code></strong>
$ <strong class="userinput"><code>dnssec-signzone -S -K keys example.net</code></strong>
</pre>
-<p>To revoke a key, the new command
- <span><strong class="command">dnssec-revoke</strong></span> has been added. This adds the
+
<p>To revoke a key, the new command
+ <span class="command"><strong>dnssec-revoke</strong></span> has been added. This adds the
REVOKED bit to the key flags and re-generates the
<code class="filename">K*.key</code> and
<code class="filename">K*.private</code> files.</p>
-<p>After revoking the active key, the zone must be signed
+
<p>After revoking the active key, the zone must be signed
with both the revoked KSK and the new active KSK. (Smart
signing takes care of this automatically.)</p>
-<p>Once a key has been revoked and used to sign the DNSKEY
+
<p>Once a key has been revoked and used to sign the DNSKEY
RRset in which it appears, that key will never again be
accepted as a valid trust anchor by the resolver. However,
validation can proceed using the new active key (which had been
accepted by the resolver when it was a stand-by key).</p>
-<p>See RFC 5011 for more details on key rollover
+
<p>See RFC 5011 for more details on key rollover
scenarios.</p>
-<p>When a key has been revoked, its key ID changes,
+
<p>When a key has been revoked, its key ID changes,
increasing by 128, and wrapping around at 65535. So, for
example, the key "<code class="filename">Kexample.com.+005+10000</code>" becomes
"<code class="filename">Kexample.com.+005+10128</code>".</p>
-<p>If two keys have IDs exactly 128 apart, and one is
+
<p>If two keys have IDs exactly 128 apart, and one is
revoked, then the two key IDs will collide, causing several
problems. To prevent this,
- <span><strong class="command">dnssec-keygen</strong></span> will not generate a new key if
+ <span class="command"><strong>dnssec-keygen</strong></span> will not generate a new key if
another key is present which may collide. This checking will
only occur if the new keys are written to the same directory
which holds all other keys in use for that zone.</p>
-<p>Older versions of BIND 9 did not have this precaution.
+
<p>Older versions of BIND 9 did not have this precaution.
Exercise caution if using key revocation on keys that were
generated by previous releases, or if using keys stored in
multiple directories or on multiple machines.</p>
-<p>It is expected that a future release of BIND 9 will
+
<p>It is expected that a future release of BIND 9 will
address this problem in a different way, by storing revoked
keys with their original unrevoked key IDs.</p>
+ </div>
</div>
-</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="pkcs11"></a>PKCS#11 (Cryptoki) support</h2></div></div></div>
-<p>
+
+ <p>
PKCS#11 (Public Key Cryptography Standard #11) defines a
platform-independent API for the control of hardware security
modules (HSMs) and other cryptographic support devices.
</p>
-<p>
BIND 9 is known to work with three HSMs: The AEP Keyper, which has
been tested with Debian Linux, Solaris x86 and Windows Server 2003;
the Thales nShield, tested with Debian Linux; and the Sun SCA 6000
a software-based HSM simulator library produced by the OpenDNSSEC
project.
</p>
-<p>
PKCS#11 makes use of a "provider library": a dynamically loadable
library which provides a low-level PKCS#11 interface to drive the HSM
hardware. The PKCS#11 provider library comes from the HSM vendor, and
it is specific to the HSM to be controlled.
</p>
-<p>
There are two available mechanisms for PKCS#11 support in BIND 9:
OpenSSL-based PKCS#11 and native PKCS#11. When using the first
mechanism, BIND uses a modified version of OpenSSL, which loads
OpenSSL completely; BIND loads the provider library itself, and uses
the PKCS#11 API to drive the HSM directly.
</p>
-<div class="sect2" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2613795"></a>Prerequisites</h3></div></div></div>
-<p>
+<a name="id-1.5.13.7"></a>Prerequisites</h3></div></div></div>
+
+ <p>
See the documentation provided by your HSM vendor for
information about installing, initializing, testing and
troubleshooting the HSM.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2613804"></a>Native PKCS#11</h3></div></div></div>
-<p>
+<a name="id-1.5.13.8"></a>Native PKCS#11</h3></div></div></div>
+
+ <p>
Native PKCS#11 mode will only work with an HSM capable of carrying
out <span class="emphasis"><em>every</em></span> cryptographic operation BIND 9 may
need. The HSM's provider library must have a complete implementation
native PKCS#11, it is expected that OpenSSL-based PKCS#11 will
be deprecated.)
</p>
-<p>
To build BIND with native PKCS#11, configure as follows:
</p>
-<pre class="screen">
$ <strong class="userinput"><code>cd bind9</code></strong>
$ <strong class="userinput"><code>./configure --enable-native-pkcs11 \
--with-pkcs11=<em class="replaceable"><code>provider-library-path</code></em></code></strong>
</pre>
-<p>
- This will cause all BIND tools, including <span><strong class="command">named</strong></span>
- and the <span><strong class="command">dnssec-*</strong></span> and <span><strong class="command">pkcs11-*</strong></span>
+ This will cause all BIND tools, including <span class="command"><strong>named</strong></span>
+ and the <span class="command"><strong>dnssec-*</strong></span> and <span class="command"><strong>pkcs11-*</strong></span>
tools, to use the PKCS#11 provider library specified in
<em class="replaceable"><code>provider-library-path</code></em> for cryptography.
(The provider library path can be overridden using the
- <code class="option">-E</code> in <span><strong class="command">named</strong></span> and the
- <span><strong class="command">dnssec-*</strong></span> tools, or the <code class="option">-m</code> in
- the <span><strong class="command">pkcs11-*</strong></span> tools.)
+ <code class="option">-E</code> in <span class="command"><strong>named</strong></span> and the
+ <span class="command"><strong>dnssec-*</strong></span> tools, or the <code class="option">-m</code> in
+ the <span class="command"><strong>pkcs11-*</strong></span> tools.)
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2613884"></a>Building SoftHSMv2</h4></div></div></div>
-<p>
+<a name="id-1.5.13.8.7"></a>Building SoftHSMv2</h4></div></div></div>
+
+ <p>
SoftHSMv2, the latest development version of SoftHSM, is available
from
- <a href="https://github.com/opendnssec/SoftHSMv2" target="_top">
+ <a class="ulink" href="https://github.com/opendnssec/SoftHSMv2" target="_top">
https://github.com/opendnssec/SoftHSMv2
</a>.
It is a software library developed by the OpenDNSSEC project
- (<a href="http://www.opendnssec.org" target="_top">
+ (<a class="ulink" href="http://www.opendnssec.org" target="_top">
http://www.opendnssec.org
</a>)
which provides a PKCS#11 interface to a virtual HSM, implemented in
cryptographic functions, but when using it for native PKCS#11 in
BIND, OpenSSL is required.
</p>
-<p>
By default, the SoftHSMv2 configuration file is
<em class="replaceable"><code>prefix</code></em>/etc/softhsm2.conf (where
<em class="replaceable"><code>prefix</code></em> is configured at compile time).
variable. The SoftHSMv2 cryptographic store must be installed and
initialized before using it with BIND.
</p>
-<pre class="screen">
$ <strong class="userinput"><code> cd SoftHSMv2 </code></strong>
$ <strong class="userinput"><code> configure --with-crypto-backend=openssl --prefix=/opt/pkcs11/usr --enable-gost </code></strong>
$ <strong class="userinput"><code> make </code></strong>
$ <strong class="userinput"><code> make install </code></strong>
$ <strong class="userinput"><code> /opt/pkcs11/usr/bin/softhsm-util --init-token 0 --slot 0 --label softhsmv2 </code></strong>
</pre>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2613950"></a>OpenSSL-based PKCS#11</h3></div></div></div>
-<p>
+<a name="id-1.5.13.9"></a>OpenSSL-based PKCS#11</h3></div></div></div>
+
+ <p>
OpenSSL-based PKCS#11 mode uses a modified version of the
OpenSSL library; stock OpenSSL does not fully support PKCS#11.
ISC provides a patch to OpenSSL to correct this. This patch is
modified by ISC to provide new features such as PIN management and
key-by-reference.
</p>
-<p>
There are two "flavors" of PKCS#11 support provided by
the patched OpenSSL, one of which must be chosen at
configuration time. The correct choice depends on the HSM
hardware:
</p>
-<div class="itemizedlist"><ul type="disc">
-<li><p>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
Use 'crypto-accelerator' with HSMs that have hardware
cryptographic acceleration features, such as the SCA 6000
board. This causes OpenSSL to run all supported
cryptographic operations in the HSM.
- </p></li>
-<li><p>
+ </p>
+ </li>
+<li class="listitem">
+ <p>
Use 'sign-only' with HSMs that are designed to
function primarily as secure key storage devices, but lack
hardware acceleration. These devices are highly secure, but
such as zone signing, and to use the system CPU for all
other computationally-intensive operations. The AEP Keyper
is an example of such a device.
- </p></li>
+ </p>
+ </li>
</ul></div>
-<p>
The modified OpenSSL code is included in the BIND 9 release,
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
we use OpenSSL 0.9.8, but the same methods work with OpenSSL
1.0.0 and 1.0.1.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
The latest OpenSSL versions as of this writing (January 2015)
are 0.9.8zc, 1.0.0o, and 1.0.1j.
are released. The version number in the following examples
is expected to change.
</div>
-<p>
Before building BIND 9 with PKCS#11 support, it will be
necessary to build OpenSSL with the patch in place, and configure
it with the path to your HSM's PKCS#11 provider library.
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2613988"></a>Patching OpenSSL</h4></div></div></div>
-<pre class="screen">
-$ <strong class="userinput"><code>wget <a href="" target="_top">http://www.openssl.org/source/openssl-0.9.8zc.tar.gz</a></code></strong>
+<a name="id-1.5.13.9.9"></a>Patching OpenSSL</h4></div></div></div>
+
+ <pre class="screen">
+$ <strong class="userinput"><code>wget <a class="ulink" href="" target="_top">http://www.openssl.org/source/openssl-0.9.8zc.tar.gz</a></code></strong>
</pre>
-<p>Extract the tarball:</p>
-<pre class="screen">
+
<p>Extract the tarball:</p>
$ <strong class="userinput"><code>tar zxf openssl-0.9.8zc.tar.gz</code></strong>
</pre>
-<p>Apply the patch from the BIND 9 release:</p>
-<pre class="screen">
+
<p>Apply the patch from the BIND 9 release:</p>
$ <strong class="userinput"><code>patch -p1 -d openssl-0.9.8zc \
< bind9/bin/pkcs11/openssl-0.9.8zc-patch</code></strong>
</pre>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
Note that the patch file may not be compatible with the
"patch" utility on all operating systems. You may need to
install GNU patch.
</div>
-<p>
When building OpenSSL, place it in a non-standard
location so that it does not interfere with OpenSSL libraries
elsewhere on the system. In the following examples, we choose
to install into "/opt/pkcs11/usr". We will use this location
when we configure BIND 9.
</p>
-<p>
Later, when building BIND 9, the location of the custom-built
OpenSSL library will need to be specified via configure.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2614046"></a>Building OpenSSL for the AEP Keyper on Linux</h4></div></div></div>
-<p>
+<a name="id-1.5.13.9.10"></a>Building OpenSSL for the AEP Keyper on Linux</h4></div></div></div>
+
+
+ <p>
The AEP Keyper is a highly secure key storage device,
but does not provide hardware cryptographic acceleration. It
can carry out cryptographic operations, but it is probably
slower than your system's CPU. Therefore, we choose the
'sign-only' flavor when building OpenSSL.
</p>
-<p>
The Keyper-specific PKCS#11 provider library is
delivered with the Keyper software. In this example, we place
it /opt/pkcs11/usr/lib:
</p>
-<pre class="screen">
$ <strong class="userinput"><code>cp pkcs11.GCC4.0.2.so.4.05 /opt/pkcs11/usr/lib/libpkcs11.so</code></strong>
</pre>
-<p>
This library is only available for Linux as a 32-bit
binary. If we are compiling on a 64-bit Linux system, it is
necessary to force a 32-bit build, by specifying -m32 in the
build options.
</p>
-<p>
Finally, the Keyper library requires threads, so we
must specify -pthread.
</p>
-<pre class="screen">
$ <strong class="userinput"><code>cd openssl-0.9.8zc</code></strong>
$ <strong class="userinput"><code>./Configure linux-generic32 -m32 -pthread \
--pk11-libname=/opt/pkcs11/usr/lib/libpkcs11.so \
--pk11-flavor=sign-only \
--prefix=/opt/pkcs11/usr</code></strong>
</pre>
-<p>
- After configuring, run "<span><strong class="command">make</strong></span>"
- and "<span><strong class="command">make test</strong></span>". If "<span><strong class="command">make
+ After configuring, run "<span class="command"><strong>make</strong></span>"
+ and "<span class="command"><strong>make test</strong></span>". If "<span class="command"><strong>make
test</strong></span>" fails with "pthread_atfork() not found", you forgot to
add the -pthread above.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2614321"></a>Building OpenSSL for the SCA 6000 on Solaris</h4></div></div></div>
-<p>
+<a name="id-1.5.13.9.11"></a>Building OpenSSL for the SCA 6000 on Solaris</h4></div></div></div>
+
+
+ <p>
The SCA-6000 PKCS#11 provider is installed as a system
library, libpkcs11. It is a true crypto accelerator, up to 4
times faster than any CPU, so the flavor shall be
'crypto-accelerator'.
</p>
-<p>
In this example, we are building on Solaris x86 on an
AMD64 system.
</p>
-<pre class="screen">
$ <strong class="userinput"><code>cd openssl-0.9.8zc</code></strong>
$ <strong class="userinput"><code>./Configure solaris64-x86_64-cc \
--pk11-libname=/usr/lib/64/libpkcs11.so \
--pk11-flavor=crypto-accelerator \
--prefix=/opt/pkcs11/usr</code></strong>
</pre>
-<p>
(For a 32-bit build, use "solaris-x86-cc" and /usr/lib/libpkcs11.so.)
</p>
-<p>
After configuring, run
- <span><strong class="command">make</strong></span> and
- <span><strong class="command">make test</strong></span>.
+ <span class="command"><strong>make</strong></span> and
+ <span class="command"><strong>make test</strong></span>.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2640789"></a>Building OpenSSL for SoftHSM</h4></div></div></div>
-<p>
+<a name="id-1.5.13.9.12"></a>Building OpenSSL for SoftHSM</h4></div></div></div>
+
+
+ <p>
SoftHSM (version 1) is a software library developed by the
OpenDNSSEC project
- (<a href="http://www.opendnssec.org" target="_top">
+ (<a class="ulink" href="http://www.opendnssec.org" target="_top">
http://www.opendnssec.org
</a>)
which provides a
less secure than a true HSM, it can allow you to experiment
with PKCS#11 when an HSM is not available.
</p>
-<p>
The SoftHSM cryptographic store must be installed and
initialized before using it with OpenSSL, and the SOFTHSM_CONF
environment variable must always point to the SoftHSM configuration
file:
</p>
-<pre class="screen">
$ <strong class="userinput"><code> cd softhsm-1.3.7 </code></strong>
$ <strong class="userinput"><code> configure --prefix=/opt/pkcs11/usr </code></strong>
$ <strong class="userinput"><code> make </code></strong>
$ <strong class="userinput"><code> echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF </code></strong>
$ <strong class="userinput"><code> /opt/pkcs11/usr/bin/softhsm --init-token 0 --slot 0 --label softhsm </code></strong>
</pre>
-<p>
SoftHSM can perform all cryptographic operations, but
since it only uses your system CPU, there is no advantage to using
it for anything but signing. Therefore, we choose the 'sign-only'
flavor when building OpenSSL.
</p>
-<pre class="screen">
$ <strong class="userinput"><code>cd openssl-0.9.8zc</code></strong>
$ <strong class="userinput"><code>./Configure linux-x86_64 -pthread \
--pk11-libname=/opt/pkcs11/usr/lib/libsofthsm.so \
--pk11-flavor=sign-only \
--prefix=/opt/pkcs11/usr</code></strong>
</pre>
-<p>
- After configuring, run "<span><strong class="command">make</strong></span>"
- and "<span><strong class="command">make test</strong></span>".
+ After configuring, run "<span class="command"><strong>make</strong></span>"
+ and "<span class="command"><strong>make test</strong></span>".
</p>
-</div>
-<p>
+ </div>
Once you have built OpenSSL, run
- "<span><strong class="command">apps/openssl engine pkcs11</strong></span>" to confirm
+ "<span class="command"><strong>apps/openssl engine pkcs11</strong></span>" to confirm
that PKCS#11 support was compiled in correctly. The output
should be one of the following lines, depending on the flavor
selected:
</p>
-<pre class="screen">
(pkcs11) PKCS #11 engine support (sign only)
</pre>
-<p>Or:</p>
-<pre class="screen">
(pkcs11) PKCS #11 engine support (crypto accelerator)
</pre>
-<p>
Next, run
- "<span><strong class="command">apps/openssl engine pkcs11 -t</strong></span>". This will
+ "<span class="command"><strong>apps/openssl engine pkcs11 -t</strong></span>". This will
attempt to initialize the PKCS#11 engine. If it is able to
do so successfully, it will report
- “<span class="quote"><code class="literal">[ available ]</code></span>”.
+ <span class="quote">“<span class="quote"><code class="literal">[ available ]</code></span>”</span>.
</p>
-<p>
If the output is correct, run
- "<span><strong class="command">make install</strong></span>" which will install the
+ "<span class="command"><strong>make install</strong></span>" which will install the
modified OpenSSL suite to <code class="filename">/opt/pkcs11/usr</code>.
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2640945"></a>Configuring BIND 9 for Linux with the AEP Keyper</h4></div></div></div>
-<p>
+<a name="id-1.5.13.9.19"></a>Configuring BIND 9 for Linux with the AEP Keyper</h4></div></div></div>
+
+
+ <p>
To link with the PKCS#11 provider, threads must be
enabled in the BIND 9 build.
</p>
-<p>
The PKCS#11 library for the AEP Keyper is currently
only available as a 32-bit binary. If we are building on a
64-bit host, we must force a 32-bit build by adding "-m32" to
the CC options on the "configure" command line.
</p>
-<pre class="screen">
$ <strong class="userinput"><code>cd ../bind9</code></strong>
$ <strong class="userinput"><code>./configure CC="gcc -m32" --enable-threads \
--with-openssl=/opt/pkcs11/usr \
--with-pkcs11=/opt/pkcs11/usr/lib/libpkcs11.so</code></strong>
</pre>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2640977"></a>Configuring BIND 9 for Solaris with the SCA 6000</h4></div></div></div>
-<p>
+<a name="id-1.5.13.9.20"></a>Configuring BIND 9 for Solaris with the SCA 6000</h4></div></div></div>
+
+
+ <p>
To link with the PKCS#11 provider, threads must be
enabled in the BIND 9 build.
</p>
-<pre class="screen">
$ <strong class="userinput"><code>cd ../bind9</code></strong>
$ <strong class="userinput"><code>./configure CC="cc -xarch=amd64" --enable-threads \
--with-openssl=/opt/pkcs11/usr \
--with-pkcs11=/usr/lib/64/libpkcs11.so</code></strong>
</pre>
-<p>(For a 32-bit build, omit CC="cc -xarch=amd64".)</p>
-<p>
+
<p>(For a 32-bit build, omit CC="cc -xarch=amd64".)</p>
If configure complains about OpenSSL not working, you
may have a 32/64-bit architecture mismatch. Or, you may have
incorrectly specified the path to OpenSSL (it should be the
same as the --prefix argument to the OpenSSL
Configure).
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2641013"></a>Configuring BIND 9 for SoftHSM</h4></div></div></div>
-<pre class="screen">
+<a name="id-1.5.13.9.21"></a>Configuring BIND 9 for SoftHSM</h4></div></div></div>
+
+
+ <pre class="screen">
$ <strong class="userinput"><code>cd ../bind9</code></strong>
$ <strong class="userinput"><code>./configure --enable-threads \
--with-openssl=/opt/pkcs11/usr \
--with-pkcs11=/opt/pkcs11/usr/lib/libsofthsm.so</code></strong>
</pre>
-</div>
-<p>
+ </div>
After configuring, run
- "<span><strong class="command">make</strong></span>",
- "<span><strong class="command">make test</strong></span>" and
- "<span><strong class="command">make install</strong></span>".
+ "<span class="command"><strong>make</strong></span>",
+ "<span class="command"><strong>make test</strong></span>" and
+ "<span class="command"><strong>make install</strong></span>".
</p>
-<p>
(Note: If "make test" fails in the "pkcs11" system test, you may
have forgotten to set the SOFTHSM_CONF environment variable.)
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2641062"></a>PKCS#11 Tools</h3></div></div></div>
-<p>
+<a name="id-1.5.13.10"></a>PKCS#11 Tools</h3></div></div></div>
+
+ <p>
BIND 9 includes a minimal set of tools to operate the
HSM, including
- <span><strong class="command">pkcs11-keygen</strong></span> to generate a new key pair
+ <span class="command"><strong>pkcs11-keygen</strong></span> to generate a new key pair
within the HSM,
- <span><strong class="command">pkcs11-list</strong></span> to list objects currently
+ <span class="command"><strong>pkcs11-list</strong></span> to list objects currently
available,
- <span><strong class="command">pkcs11-destroy</strong></span> to remove objects, and
- <span><strong class="command">pkcs11-tokens</strong></span> to list available tokens.
+ <span class="command"><strong>pkcs11-destroy</strong></span> to remove objects, and
+ <span class="command"><strong>pkcs11-tokens</strong></span> to list available tokens.
</p>
-<p>
In UNIX/Linux builds, these tools are built only if BIND
9 is configured with the --with-pkcs11 option. (Note: If
--with-pkcs11 is set to "yes", rather than to the path of the
PKCS11_PROVIDER environment variable to specify the path to the
provider.)
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2641098"></a>Using the HSM</h3></div></div></div>
-<p>
+<a name="id-1.5.13.11"></a>Using the HSM</h3></div></div></div>
+
+ <p>
For OpenSSL-based PKCS#11, we must first set up the runtime
environment so the OpenSSL and PKCS#11 libraries can be loaded:
</p>
-<pre class="screen">
$ <strong class="userinput"><code>export LD_LIBRARY_PATH=/opt/pkcs11/usr/lib:${LD_LIBRARY_PATH}</code></strong>
</pre>
-<p>
- This causes <span><strong class="command">named</strong></span> and other binaries to load
+ This causes <span class="command"><strong>named</strong></span> and other binaries to load
the OpenSSL library from <code class="filename">/opt/pkcs11/usr/lib</code>
rather than from the default location. This step is not necessary
when using native PKCS#11.
</p>
-<p>
Some HSMs require other environment variables to be set.
For example, when operating an AEP Keyper, it is necessary to
specify the location of the "machine" file, which stores
<code class="filename">/opt/Keyper/PKCS11Provider/machine</code>,
use:
</p>
-<pre class="screen">
$ <strong class="userinput"><code>export KEYPER_LIBRARY_PATH=/opt/Keyper/PKCS11Provider</code></strong>
</pre>
-<p>
Such environment variables must be set whenever running
any tool that uses the HSM, including
- <span><strong class="command">pkcs11-keygen</strong></span>,
- <span><strong class="command">pkcs11-list</strong></span>,
- <span><strong class="command">pkcs11-destroy</strong></span>,
- <span><strong class="command">dnssec-keyfromlabel</strong></span>,
- <span><strong class="command">dnssec-signzone</strong></span>,
- <span><strong class="command">dnssec-keygen</strong></span>, and
- <span><strong class="command">named</strong></span>.
+ <span class="command"><strong>pkcs11-keygen</strong></span>,
+ <span class="command"><strong>pkcs11-list</strong></span>,
+ <span class="command"><strong>pkcs11-destroy</strong></span>,
+ <span class="command"><strong>dnssec-keyfromlabel</strong></span>,
+ <span class="command"><strong>dnssec-signzone</strong></span>,
+ <span class="command"><strong>dnssec-keygen</strong></span>, and
+ <span class="command"><strong>named</strong></span>.
</p>
-<p>
We can now create and use keys in the HSM. In this case,
we will create a 2048 bit key and give it the label
"sample-ksk":
</p>
-<pre class="screen">
$ <strong class="userinput"><code>pkcs11-keygen -b 2048 -l sample-ksk</code></strong>
</pre>
-<p>To confirm that the key exists:</p>
-<pre class="screen">
+
<p>To confirm that the key exists:</p>
$ <strong class="userinput"><code>pkcs11-list</code></strong>
Enter PIN:
object[0]: handle 2147483658 class 3 label[8] 'sample-ksk' id[0]
object[1]: handle 2147483657 class 2 label[8] 'sample-ksk' id[0]
</pre>
-<p>
Before using this key to sign a zone, we must create a
pair of BIND 9 key files. The "dnssec-keyfromlabel" utility
does this. In this case, we will be using the HSM key
"sample-ksk" as the key-signing key for "example.net":
</p>
-<pre class="screen">
$ <strong class="userinput"><code>dnssec-keyfromlabel -l sample-ksk -f KSK example.net</code></strong>
</pre>
-<p>
The resulting K*.key and K*.private files can now be used
to sign the zone. Unlike normal K* files, which contain both
public and private key data, these files will contain only the
remains stored within the HSM. Signing with the private key takes
place inside the HSM.
</p>
-<p>
If you wish to generate a second key in the HSM for use
as a zone-signing key, follow the same procedure above, using a
different keylabel, a smaller key size, and omitting "-f KSK"
from the dnssec-keyfromlabel arguments:
</p>
-<p>
(Note: When using OpenSSL-based PKCS#11 the label is an arbitrary
string which identifies the key. With native PKCS#11, the label is
a PKCS#11 URI string which may include other details about the key
and the HSM, including its PIN. See
- <a href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel"><span class="refentrytitle"><span class="application">dnssec-keyfromlabel</span></span>(8)</a> for details.)
+ <a class="xref" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel"><span class="refentrytitle"><span class="application">dnssec-keyfromlabel</span></span>(8)</a> for details.)
</p>
-<pre class="screen">
$ <strong class="userinput"><code>pkcs11-keygen -b 1024 -l sample-zsk</code></strong>
$ <strong class="userinput"><code>dnssec-keyfromlabel -l sample-zsk example.net</code></strong>
</pre>
-<p>
Alternatively, you may prefer to generate a conventional
on-disk key, using dnssec-keygen:
</p>
-<pre class="screen">
$ <strong class="userinput"><code>dnssec-keygen example.net</code></strong>
</pre>
-<p>
This provides less security than an HSM key, but since
HSMs can be slow or cumbersome to use for security reasons, it
may be more efficient to reserve HSM keys for use in the less
there is no speed advantage to using on-disk keys, as cryptographic
operations will be done by the HSM regardless.)
</p>
-<p>
Now you can sign the zone. (Note: If not using the -S
- option to <span><strong class="command">dnssec-signzone</strong></span>, it will be
+ option to <span class="command"><strong>dnssec-signzone</strong></span>, it will be
necessary to add the contents of both <code class="filename">K*.key</code>
files to the zone master file before signing it.)
</p>
-<pre class="screen">
$ <strong class="userinput"><code>dnssec-signzone -S example.net</code></strong>
Enter PIN:
Verifying the zone using the following algorithms:
Algorithm: NSEC3RSASHA1: ZSKs: 1, KSKs: 1 active, 0 revoked, 0 stand-by
example.net.signed
</pre>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2641452"></a>Specifying the engine on the command line</h3></div></div></div>
-<p>
+<a name="id-1.5.13.12"></a>Specifying the engine on the command line</h3></div></div></div>
+
+ <p>
When using OpenSSL-based PKCS#11, the "engine" to be used by
- OpenSSL can be specified in <span><strong class="command">named</strong></span> and all of
- the BIND <span><strong class="command">dnssec-*</strong></span> tools by using the "-E
+ OpenSSL can be specified in <span class="command"><strong>named</strong></span> and all of
+ the BIND <span class="command"><strong>dnssec-*</strong></span> tools by using the "-E
<engine>" command line option. If BIND 9 is built with
the --with-pkcs11 option, this option defaults to "pkcs11".
Specifying the engine will generally not be necessary unless
for some reason you wish to use a different OpenSSL
engine.
</p>
-<p>
If you wish to disable use of the "pkcs11" engine —
for troubleshooting purposes, or because the HSM is unavailable
— set the engine to the empty string. For example:
</p>
-<pre class="screen">
$ <strong class="userinput"><code>dnssec-signzone -E '' -S example.net</code></strong>
</pre>
-<p>
This causes
- <span><strong class="command">dnssec-signzone</strong></span> to run as if it were compiled
+ <span class="command"><strong>dnssec-signzone</strong></span> to run as if it were compiled
without the --with-pkcs11 option.
</p>
-<p>
When built with native PKCS#11 mode, the "engine" option has a
different meaning: it specifies the path to the PKCS#11 provider
library. This may be useful when testing a new provider library.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2641500"></a>Running named with automatic zone re-signing</h3></div></div></div>
-<p>
- If you want <span><strong class="command">named</strong></span> to dynamically re-sign zones
+<a name="id-1.5.13.13"></a>Running named with automatic zone re-signing</h3></div></div></div>
+
+ <p>
+ If you want <span class="command"><strong>named</strong></span> to dynamically re-sign zones
using HSM keys, and/or to to sign new records inserted via nsupdate,
- then <span><strong class="command">named</strong></span> must have access to the HSM PIN. In OpenSSL-based PKCS#11,
+ then <span class="command"><strong>named</strong></span> must have access to the HSM PIN. In OpenSSL-based PKCS#11,
this is accomplished by placing the PIN into the openssl.cnf file
(in the above examples,
<code class="filename">/opt/pkcs11/usr/ssl/openssl.cnf</code>).
</p>
-<p>
The location of the openssl.cnf file can be overridden by
setting the OPENSSL_CONF environment variable before running
- <span><strong class="command">named</strong></span>.
+ <span class="command"><strong>named</strong></span>.
</p>
-<p>Sample openssl.cnf:</p>
-<pre class="programlisting">
+
<p>Sample openssl.cnf:</p>
+
<pre class="programlisting">
openssl_conf = openssl_def
[ openssl_def ]
engines = engine_section
[ pkcs11_section ]
PIN = <em class="replaceable"><code><PLACE PIN HERE></code></em>
</pre>
-<p>
This will also allow the dnssec-* tools to access the HSM
without PIN entry. (The pkcs11-* tools access the HSM directly,
not via OpenSSL, so a PIN will still be required to use
them.)
</p>
-<p>
In native PKCS#11 mode, the PIN can be provided in a file specified
as an attribute of the key's label. For example, if a key had the label
<strong class="userinput"><code>pkcs11:object=local-zsk;pin-source=/etc/hsmpin</code></strong>,
then the PIN would be read from the file
<code class="filename">/etc/hsmpin</code>.
</p>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Warning</h3>
-<p>
Placing the HSM's PIN in a text file in this manner may reduce the
security advantage of using an HSM. Be sure this is what you want to
do before configuring the system in this way.
</p>
+ </div>
+ </div>
</div>
-</div>
-</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="dlz-info"></a>DLZ (Dynamically Loadable Zones)</h2></div></div></div>
-<p>
+
+ <p>
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
written for any other.
</p>
-<p>
- Historically, DLZ drivers had to be statically linked with the <span><strong class="command">named</strong></span>
+ Historically, DLZ drivers had to be statically linked with the <span class="command"><strong>named</strong></span>
binary and were turned on via a configure option at compile time (for
example, <strong class="userinput"><code>"configure --with-dlz-ldap"</code></strong>).
Currently, the drivers provided in the BIND 9 tarball in
<code class="filename">contrib/dlz/drivers</code> are still linked this
way.
</p>
-<p>
In BIND 9.8 and higher, it is possible to link some DLZ modules
dynamically at runtime, via the DLZ "dlopen" driver, which acts as a
generic wrapper around a shared object implementing the DLZ API. The
- "dlopen" driver is linked into <span><strong class="command">named</strong></span> by default, so configure options
+ "dlopen" driver is linked into <span class="command"><strong>named</strong></span> by default, so configure options
are no longer necessary when using these dynamically linkable drivers,
but are still needed for the older drivers in
<code class="filename">contrib/dlz/drivers</code>.
</p>
-<p>
- When the DLZ module provides data to <span><strong class="command">named</strong></span>, it does so in text format.
- The response is converted to DNS wire format by <span><strong class="command">named</strong></span>. This
+
+ <p>
+ When the DLZ module provides data to <span class="command"><strong>named</strong></span>, it does so in text format.
+ The response is converted to DNS wire format by <span class="command"><strong>named</strong></span>. This
conversion, and the lack of any internal caching, places significant
limits on the query performance of DLZ modules. Consequently, DLZ is
not recommended for use on high-volume servers. However, it can be
DNS notify; slaves are not automatically informed of changes to the
zones in the database.)
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2613331"></a>Configuring DLZ</h3></div></div></div>
-<p>
- A DLZ database is configured with a <span><strong class="command">dlz</strong></span>
+<a name="id-1.5.14.7"></a>Configuring DLZ</h3></div></div></div>
+
+ <p>
+ A DLZ database is configured with a <span class="command"><strong>dlz</strong></span>
statement in <code class="filename">named.conf</code>:
</p>
-<pre class="screen">
dlz example {
- database "dlopen driver.so <code class="option">args</code>";
- search yes;
+ database "dlopen driver.so <code class="option">args</code>";
+ search yes;
};
</pre>
-<p>
This specifies a DLZ module to search when answering queries; the
module is implemented in <code class="filename">driver.so</code> and is
loaded at runtime by the dlopen DLZ driver. Multiple
- <span><strong class="command">dlz</strong></span> statements can be specified; when
+ <span class="command"><strong>dlz</strong></span> statements can be specified; when
answering a query, all DLZ modules with <code class="option">search</code>
set to <code class="literal">yes</code> will be queried to find out if
they contain an answer for the query name; the best available
answer will be returned to the client.
</p>
-<p>
The <code class="option">search</code> option in the above example can be
omitted, because <code class="literal">yes</code> is the default value.
</p>
-<p>
If <code class="option">search</code> is set to <code class="literal">no</code>, then
this DLZ module is <span class="emphasis"><em>not</em></span> searched for the best
match when a query is received. Instead, zones in this DLZ must be
zone's data. For example, to implement NXDOMAIN redirection using
a DLZ module for back-end storage of redirection rules:
</p>
-<pre class="screen">
dlz other {
- database "dlopen driver.so <code class="option">args</code>";
- search no;
+ database "dlopen driver.so <code class="option">args</code>";
+ search no;
};
zone "." {
- type redirect;
- dlz other;
+ type redirect;
+ dlz other;
};
</pre>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2613473"></a>Sample DLZ Driver</h3></div></div></div>
-<p>
+<a name="id-1.5.14.8"></a>Sample DLZ Driver</h3></div></div></div>
+
+ <p>
For guidance in implementation of DLZ modules, the directory
<code class="filename">contrib/dlz/example</code> contains a basic
dynamically-linkable DLZ module--i.e., one which can be
loaded at runtime by the "dlopen" DLZ driver.
The example sets up a single zone, whose name is passed
- to the module as an argument in the <span><strong class="command">dlz</strong></span>
+ to the module as an argument in the <span class="command"><strong>dlz</strong></span>
statement:
</p>
-<pre class="screen">
dlz other {
- database "dlopen driver.so example.nil";
+ database "dlopen driver.so example.nil";
};
</pre>
-<p>
In the above example, the module is configured to create a zone
"example.nil", which can answer queries and AXFR requests, and
accept DDNS updates. At runtime, prior to any updates, the zone
contains an SOA, NS, and a single A record at the apex:
</p>
-<pre class="screen">
example.nil. 3600 IN SOA example.nil. hostmaster.example.nil. (
- 123 900 600 86400 3600
- )
+ 123 900 600 86400 3600
+ )
example.nil. 3600 IN NS example.nil.
example.nil. 1800 IN A 10.53.0.1
</pre>
-<p>
The sample driver is capable of retrieving information about the
querying client, and altering its response on the basis of this
information. To demonstrate this feature, the example driver
e.g., by providing different address records for a particular name
depending on the network from which the query arrived.
</p>
-<p>
Documentation of the DLZ module API can be found in
<code class="filename">contrib/dlz/example/README</code>. This directory also
contains the header file <code class="filename">dlz_minimal.h</code>, which
defines the API and should be included by any dynamically-linkable
DLZ module.
</p>
+ </div>
</div>
-</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="dyndb-info"></a>DynDB (Dynamic Database)</h2></div></div></div>
-<p>
+
+ <p>
DynDB is an extension to BIND 9 which, like DLZ
- (see <a href="Bv9ARM.ch04.html#dlz-info" title="DLZ (Dynamically Loadable Zones)">the section called “DLZ (Dynamically Loadable Zones)”</a>), allows zone data to be
+ (see <a class="xref" href="Bv9ARM.ch04.html#dlz-info" title="DLZ (Dynamically Loadable Zones)">the section called “DLZ (Dynamically Loadable Zones)”</a>), allows zone data to be
retrieved from an external database. Unlike DLZ, a DynDB module
provides a full-featured BIND zone database interface. Where
DLZ translates DNS queries into real-time database lookups,
data source, providing the same performance and functionality
as zones served natively by BIND.
</p>
-<p>
A DynDB module supporting LDAP has been created by Red Hat
and is available from
- <a href="https://fedorahosted.org/bind-dyndb-ldap/" target="_top">https://fedorahosted.org/bind-dyndb-ldap/</a>.
+ <a class="ulink" href="https://fedorahosted.org/bind-dyndb-ldap/" target="_top">https://fedorahosted.org/bind-dyndb-ldap/</a>.
</p>
-<p>
A sample DynDB module for testing and developer guidance
is included with the BIND source code, in the directory
<code class="filename">bin/tests/system/dyndb/driver</code>.
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2668419"></a>Configuring DynDB</h3></div></div></div>
-<p>
- A DynDB database is configured with a <span><strong class="command">dyndb</strong></span>
+<a name="id-1.5.15.6"></a>Configuring DynDB</h3></div></div></div>
+
+ <p>
+ A DynDB database is configured with a <span class="command"><strong>dyndb</strong></span>
statement in <code class="filename">named.conf</code>:
</p>
-<pre class="screen">
dyndb example "driver.so" {
<em class="replaceable"><code>parameters</code></em>
};
</pre>
-<p>
The file <code class="filename">driver.so</code> is a DynDB module which
implements the full DNS database API. Multiple
- <span><strong class="command">dyndb</strong></span> statements can be specified, to load
+ <span class="command"><strong>dyndb</strong></span> statements can be specified, to load
different drivers or multiple instances of the same driver.
Zones provided by a DynDB module are added to the view's zone
table, and are treated as normal authoritative zones when BIND
is responding to queries. Zone configuration is handled internally
by the DynDB module.
</p>
-<p>
The <em class="replaceable"><code>parameters</code></em> are passed as an opaque
string to the DynDB module's initialization routine. Configuration
syntax will differ depending on the driver.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2614349"></a>Sample DynDB Module</h3></div></div></div>
-<p>
+<a name="id-1.5.15.7"></a>Sample DynDB Module</h3></div></div></div>
+
+ <p>
For guidance in implementation of DynDB modules, the directory
<code class="filename">bin/tests/system/dyndb/driver</code>.
contains a basic DynDB module.
The example sets up two zones, whose names are passed
- to the module as arguments in the <span><strong class="command">dyndb</strong></span>
+ to the module as arguments in the <span class="command"><strong>dyndb</strong></span>
statement:
</p>
-<pre class="screen">
dyndb sample "sample.so" { example.nil. arpa. };
</pre>
-<p>
In the above example, the module is configured to create a zone
"example.nil", which can answer queries and AXFR requests, and
accept DDNS updates. At runtime, prior to any updates, the zone
contains an SOA, NS, and a single A record at the apex:
</p>
-<pre class="screen">
example.nil. 86400 IN SOA example.nil. example.nil. (
0 28800 7200 604800 86400
)
example.nil. 86400 IN NS example.nil.
example.nil. 86400 IN A 127.0.0.1
</pre>
-<p>
When the zone is updated dynamically, the DynDB module will determine
whether the updated RR is an address (i.e., type A or AAAA) and if
so, it will automatically update the corresponding PTR record in a
reverse zone. (Updates are not stored permanently; all updates are
lost when the server is restarted.)
</p>
+ </div>
</div>
-</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id
2571527"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div>
-<p>
+<a name="id
-1.5.16"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div>
<acronym class="acronym">BIND</acronym> 9 fully supports all currently
defined forms of IPv6 name to address and address to name
lookups. It will also use IPv6 addresses to make queries when
running on an IPv6 capable system.
</p>
-<p>
+
+ <p>
For forward lookups, <acronym class="acronym">BIND</acronym> 9 supports
only AAAA records. RFC 3363 deprecated the use of A6 records,
and client-side support for A6 records was accordingly removed
for A6 records, and accept zone transfer for a zone containing A6
records.
</p>
-<p>
+
+ <p>
For IPv6 reverse lookups, <acronym class="acronym">BIND</acronym> 9 supports
the traditional "nibble" format used in the
<span class="emphasis"><em>ip6.arpa</em></span> domain, as well as the older, deprecated
In particular, an authoritative <acronym class="acronym">BIND</acronym> 9
name server will not load a zone file containing binary labels.
</p>
-<p>
+
+ <p>
For an overview of the format and structure of IPv6 addresses,
- see <a href="Bv9ARM.ch11.html#ipv6addresses" title="IPv6 addresses (AAAA)">the section called “IPv6 addresses (AAAA)”</a>.
+ see <a class="xref" href="Bv9ARM.ch11.html#ipv6addresses" title="IPv6 addresses (AAAA)">the section called “IPv6 addresses (AAAA)”</a>.
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2571794"></a>Address Lookups Using AAAA Records</h3></div></div></div>
-<p>
+<a name="id-1.5.16.7"></a>Address Lookups Using AAAA Records</h3></div></div></div>
+
+
+ <p>
The IPv6 AAAA record is a parallel to the IPv4 A record,
and, unlike the deprecated A6 record, specifies the entire
IPv6 address in a single record. For example,
</p>
+
<pre class="programlisting">
$ORIGIN example.com.
host 3600 IN AAAA 2001:db8::1
</pre>
-<p>
+
+ <p>
Use of IPv4-in-IPv6 mapped addresses is not recommended.
If a host has an IPv4 address, use an A record, not
a AAAA, with <code class="literal">::ffff:192.168.42.1</code> as
the address.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2571815"></a>Address to Name Lookups Using Nibble Format</h3></div></div></div>
-<p>
+<a name="id-1.5.16.8"></a>Address to Name Lookups Using Nibble Format</h3></div></div></div>
+
+
+ <p>
When looking up an address in nibble format, the address
components are simply reversed, just as in IPv4, and
<code class="literal">ip6.arpa.</code> is appended to the
a host with address
<code class="literal">2001:db8::1</code>.
</p>
+
<pre class="programlisting">
$ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 14400 IN PTR (
host.example.com. )
</pre>
-</div>
-</div>
-</div>
+
+ </div>
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 5. The BIND 9 Lightweight Resolver</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch04.html" title="Chapter 4. Advanced DNS Features">
<link rel="next" href="Bv9ARM.ch06.html" title="Chapter 6. BIND 9 Configuration Reference">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch05"></a>Chapter 5. The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch05"></a>Chapter 5. The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch05.html#id2571848">The Lightweight Resolver Library</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt>
+<dl class="toc">
+<dt><span class="section"><a href="Bv9ARM.ch05.html#id-1.6.3">The Lightweight Resolver Library</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt>
</dl>
</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2571848"></a>The Lightweight Resolver Library</h2></div></div></div>
-<p>
+<a name="id-1.6.3"></a>The Lightweight Resolver Library</h2></div></div></div>
+
+ <p>
Traditionally applications have been linked with a stub resolver
library that sends recursive DNS queries to a local caching name
server.
</p>
-<p>
IPv6 once introduced new complexity into the resolution process,
such as following A6 chains and DNAME records, and simultaneous
lookup of IPv4 and IPv6 addresses. Though most of the complexity was
then removed, these are hard or impossible
to implement in a traditional stub resolver.
</p>
-<p>
<acronym class="acronym">BIND</acronym> 9 therefore can also provide resolution
services to local clients
using a combination of a lightweight resolver library and a resolver
a simple UDP-based protocol, the "lightweight resolver protocol"
that is distinct from and simpler than the full DNS protocol.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="lwresd"></a>Running a Resolver Daemon</h2></div></div></div>
-<p>
+
+
+ <p>
To use the lightweight resolver interface, the system must
- run the resolver daemon <span><strong class="command">lwresd</strong></span> or a
+ run the resolver daemon <span class="command"><strong>lwresd</strong></span> or a
local
- name server configured with a <span><strong class="command">lwres</strong></span>
+ name server configured with a <span class="command"><strong>lwres</strong></span>
statement.
</p>
-<p>
+
+ <p>
By default, applications using the lightweight resolver library will
make
UDP requests to the IPv4 loopback address (127.0.0.1) on port 921.
The
- address can be overridden by <span><strong class="command">lwserver</strong></span>
+ address can be overridden by <span class="command"><strong>lwserver</strong></span>
lines in
<code class="filename">/etc/resolv.conf</code>.
</p>
-<p>
+
+ <p>
The daemon currently only looks in the DNS, but in the future
it may use other sources such as <code class="filename">/etc/hosts</code>,
NIS, etc.
</p>
-<p>
- The <span><strong class="command">lwresd</strong></span> daemon is essentially a
+
+ <p>
+ The <span class="command"><strong>lwresd</strong></span> daemon is essentially a
caching-only name server that responds to requests using the
lightweight
resolver protocol rather than the DNS protocol. Because it needs
to run on each host, it is designed to require no or minimal
configuration.
Unless configured otherwise, it uses the name servers listed on
- <span><strong class="command">nameserver</strong></span> lines in <code class="filename">/etc/resolv.conf</code>
+ <span class="command"><strong>nameserver</strong></span> lines in <code class="filename">/etc/resolv.conf</code>
as forwarders, but is also capable of doing the resolution
autonomously if
none are specified.
</p>
-<p>
- The <span><strong class="command">lwresd</strong></span> daemon may also be
+ The <span class="command"><strong>lwresd</strong></span> daemon may also be
configured with a
<code class="filename">named.conf</code> style configuration file,
in
<code class="filename">/etc/lwresd.conf</code> by default. A name
server may also
be configured to act as a lightweight resolver daemon using the
- <span><strong class="command">lwres</strong></span> statement in <code class="filename">named.conf</code>.
+ <span class="command"><strong>lwres</strong></span> statement in <code class="filename">named.conf</code>.
</p>
-<p>
- The number of client queries that the <span><strong class="command">lwresd</strong></span>
+ The number of client queries that the <span class="command"><strong>lwresd</strong></span>
daemon is able to serve can be set using the
<code class="option">lwres-tasks</code> and <code class="option">lwres-clients</code>
statements in the configuration.
</p>
-</div>
-</div>
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 6. BIND 9 Configuration Reference</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch05.html" title="Chapter 5. The BIND 9 Lightweight Resolver">
<link rel="next" href="Bv9ARM.ch07.html" title="Chapter 7. BIND 9 Security Considerations">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch06"></a>Chapter 6. <acronym class="acronym">BIND</acronym> 9 Configuration Reference</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch06"></a>Chapter 6. <acronym class="acronym">BIND</acronym> 9 Configuration Reference</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
+<dl class="toc">
+<dt><span class="sect
ion"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
<dd><dl>
-<dt><span class="sect
2"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2564126">Comment Syntax</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.6">Comment Syntax</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574276"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.7"><span class="command"><strong>acl</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#acl"><span class="command"><strong>acl</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574466"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.9"><span class="command"><strong>controls</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span class="command"><strong>controls</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574893"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574910"><span><strong class="command">include</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.11"><span class="command"><strong>include</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.12"><span class="command"><strong>include</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574934"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574957"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575051"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575187"><span><strong class="command">logging</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.13"><span class="command"><strong>key</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.14"><span class="command"><strong>key</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.15"><span class="command"><strong>logging</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.16"><span class="command"><strong>logging</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576512"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576677"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576773"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576822"><span><strong class="command">masters</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.17"><span class="command"><strong>lwres</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.18"><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.19"><span class="command"><strong>masters</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.20"><span class="command"><strong>masters</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576843"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.21"><span class="command"><strong>options</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#options"><span class="command"><strong>options</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span class="command"><strong>server</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span class="command"><strong>server</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#statschannels"><span><strong class="command">statistics-channels</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2592781"><span><strong class="command">statistics-channels</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statschannels"><span class="command"><strong>statistics-channels</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.26"><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#trusted-keys"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593147"><span><strong class="command">trusted-keys</strong></span> Statement Definition
+<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted-keys"><span class="command"><strong>trusted-keys</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.28"><span class="command"><strong>trusted-keys</strong></span> Statement Definition
and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593269"><span><strong class="command">managed-keys</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#managed-keys"><span><strong class="command">managed-keys</strong></span> Statement Definition
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.29"><span class="command"><strong>managed-keys</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#managed-keys"><span class="command"><strong>managed-keys</strong></span> Statement Definition
and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593704"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span class="command"><strong>view</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.32"><span class="command"><strong>view</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span class="command"><strong>zone</strong></span>
Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2595733"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.34"><span class="command"><strong>zone</strong></span> Statement Definition and Usage</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2599438">Zone File</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7">Zone File</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2602566">Discussion of MX Records</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603113">Inverse Mapping in IPv4</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603308">Other Zone File Directives</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603581"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.4">Discussion of MX Records</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.6">Inverse Mapping in IPv4</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.7">Other Zone File Directives</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.8"><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statsfile">The Statistics File</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt></dl></dd>
</dl>
</div>
-<p>
+
+
+ <p>
<acronym class="acronym">BIND</acronym> 9 configuration is broadly similar
to <acronym class="acronym">BIND</acronym> 8; however, there are a few new
areas
if they can be more efficiently implemented using the new features
found in <acronym class="acronym">BIND</acronym> 9.
</p>
-<p>
+
+ <p>
<acronym class="acronym">BIND</acronym> 4 configuration files can be
converted to the new format
using the shell script
<code class="filename">contrib/named-bootconf/named-bootconf.sh</code>.
</p>
-<div class="sect1" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="configuration_file_elements"></a>Configuration File Elements</h2></div></div></div>
-<p>
+
+ <p>
Following is a list of elements used throughout the <acronym class="acronym">BIND</acronym> configuration
file documentation:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.855in" class="1">
+<col width="3.770in" class="2">
</colgroup>
<tbody>
<tr>
<td>
<p>
The name of an <code class="varname">address_match_list</code> as
- defined by the <span><strong class="command">acl</strong></span> statement.
+ defined by the <span class="command"><strong>acl</strong></span> statement.
</p>
</td>
</tr>
<code class="varname">ip_addr</code>,
<code class="varname">ip_prefix</code>, <code class="varname">key_id</code>,
or <code class="varname">acl_name</code> elements, see
- <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a>.
+ <a class="xref" href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a>.
</p>
</td>
</tr>
<td>
<p>
One to four integers valued 0 through
- 255 separated by dots (`.'), such as <span><strong class="command">123</strong></span>,
- <span><strong class="command">45.67</strong></span> or <span><strong class="command">89.123.45.67</strong></span>.
+ 255 separated by dots (`.'), such as <span class="command"><strong>123</strong></span>,
+ <span class="command"><strong>45.67</strong></span> or <span class="command"><strong>89.123.45.67</strong></span>.
</p>
</td>
</tr>
</td>
<td>
<p>
- An IPv6 address, such as <span><strong class="command">2001:db8::1234</strong></span>.
+ An IPv6 address, such as <span class="command"><strong>2001:db8::1234</strong></span>.
IPv6 scoped addresses that have ambiguity on their
scope zones must be disambiguated by an appropriate
zone ID with the percent character (`%') as
currently only interface names as link identifiers
are supported, assuming one-to-one mapping between
interfaces and links. For example, a link-local
- address <span><strong class="command">fe80::1</strong></span> on the link
- attached to the interface <span><strong class="command">ne0</strong></span>
- can be specified as <span><strong class="command">fe80::1%ne0</strong></span>.
+ address <span class="command"><strong>fe80::1</strong></span> on the link
+ attached to the interface <span class="command"><strong>ne0</strong></span>
+ can be specified as <span class="command"><strong>fe80::1%ne0</strong></span>.
Note that on most systems link-local addresses
always have the ambiguity, and need to be
disambiguated.
netmask.
Trailing zeros in a <code class="varname">ip_addr</code>
may omitted.
- For example, <span><strong class="command">127/8</strong></span> is the
- network <span><strong class="command">127.0.0.0</strong></span> with
- netmask <span><strong class="command">255.0.0.0</strong></span> and <span><strong class="command">1.2.3.0/28</strong></span> is
- network <span><strong class="command">1.2.3.0</strong></span> with netmask <span><strong class="command">255.255.255.240</strong></span>.
+ For example, <span class="command"><strong>127/8</strong></span> is the
+ network <span class="command"><strong>127.0.0.0</strong></span> with
+ netmask <span class="command"><strong>255.0.0.0</strong></span> and <span class="command"><strong>1.2.3.0/28</strong></span> is
+ network <span class="command"><strong>1.2.3.0</strong></span> with netmask <span class="command"><strong>255.255.255.240</strong></span>.
</p>
<p>
When specifying a prefix involving a IPv6 scoped address
Integers may take values
0 <= value <= 18446744073709551615, though
certain parameters
- (such as <span><strong class="command">max-journal-size</strong></span>) may
+ (such as <span class="command"><strong>max-journal-size</strong></span>) may
use a more limited range within these extremes.
In most cases, setting a value to 0 does not
literally mean zero; it means "undefined" or
</td>
</tr>
</tbody>
-</table></div>
-<div class="sect2" lang="en">
+</table>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="address_match_lists"></a>Address Match Lists</h3></div></div></div>
-<div class="sect3" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2573174"></a>Syntax</h4></div></div></div>
+<a name="id-1.7.5.5.3"></a>Syntax</h4></div></div></div>
+
+
<pre class="programlisting"><code class="varname">address_match_list</code> = address_match_list_element ;
[<span class="optional"> address_match_list_element; ... </span>]
<code class="varname">address_match_list_element</code> = [<span class="optional"> ! </span>] (ip_address [<span class="optional">/length</span>] |
key key_id | acl_name | { address_match_list } )
</pre>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2573202"></a>Definition and Usage</h4></div></div></div>
-<p>
+<a name="id-1.7.5.5.4"></a>Definition and Usage</h4></div></div></div>
+
+ <p>
Address match lists are primarily used to determine access
control for various server operations. They are also used in
- the <span><strong class="command">listen-on</strong></span> and <span><strong class="command">sortlist</strong></span>
+ the <span class="command"><strong>listen-on</strong></span> and <span class="command"><strong>sortlist</strong></span>
statements. The elements which constitute an address match
list can be any of the following:
</p>
-<div class="itemizedlist"><ul type="disc">
-<li>an IP address (IPv4 or IPv6)</li>
-<li>an IP prefix (in `/' notation)</li>
-<li>
- a key ID, as defined by the <span><strong class="command">key</strong></span>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ an IP address (IPv4 or IPv6)
+ </li>
+<li class="listitem">
+ an IP prefix (in `/' notation)
+ </li>
+<li class="listitem">
+
+ a key ID, as defined by the <span class="command"><strong>key</strong></span>
statement
- </li>
-<li>the name of an address match list defined with
- the <span><strong class="command">acl</strong></span> statement
- </li>
-<li>a nested address match list enclosed in braces</li>
+
+ </li>
+<li class="listitem">
+ the name of an address match list defined with
+ the <span class="command"><strong>acl</strong></span> statement
+
+ </li>
+<li class="listitem">
+ a nested address match list enclosed in braces
+ </li>
</ul></div>
-<p>
+
+ <p>
Elements can be negated with a leading exclamation mark (`!'),
and the match list names "any", "none", "localhost", and
"localnets" are predefined. More information on those names
can be found in the description of the acl statement.
</p>
-<p>
+
+ <p>
The addition of the key clause made the name of this syntactic
element something of a misnomer, since security keys can be used
to validate access without regard to a host or network address.
Nonetheless, the term "address match list" is still used
throughout the documentation.
</p>
-<p>
+
+ <p>
When a given IP address or prefix is compared to an address
match list, the comparison takes place in approximately O(1)
time. However, key comparisons require that the list of keys
be traversed until a matching key is found, and therefore may
be somewhat slower.
</p>
-<p>
+
+ <p>
The interpretation of a match depends on whether the list is being
- used for access control, defining <span><strong class="command">listen-on</strong></span> ports, or in a
- <span><strong class="command">sortlist</strong></span>, and whether the element was negated.
+ used for access control, defining <span class="command"><strong>listen-on</strong></span> ports, or in a
+ <span class="command"><strong>sortlist</strong></span>, and whether the element was negated.
</p>
-<p>
+
+ <p>
When used as an access control list, a non-negated match
allows access and a negated match denies access. If
there is no match, access is denied. The clauses
- <span><strong class="command">allow-notify</strong></span>,
- <span><strong class="command">allow-recursion</strong></span>,
- <span><strong class="command">allow-recursion-on</strong></span>,
- <span><strong class="command">allow-query</strong></span>,
- <span><strong class="command">allow-query-on</strong></span>,
- <span><strong class="command">allow-query-cache</strong></span>,
- <span><strong class="command">allow-query-cache-on</strong></span>,
- <span><strong class="command">allow-transfer</strong></span>,
- <span><strong class="command">allow-update</strong></span>,
- <span><strong class="command">allow-update-forwarding</strong></span>,
- <span><strong class="command">blackhole</strong></span>, and
- <span><strong class="command">keep-response-order</strong></span> all use address match
- lists. Similarly, the <span><strong class="command">listen-on</strong></span> option will cause the
+ <span class="command"><strong>allow-notify</strong></span>,
+ <span class="command"><strong>allow-recursion</strong></span>,
+ <span class="command"><strong>allow-recursion-on</strong></span>,
+ <span class="command"><strong>allow-query</strong></span>,
+ <span class="command"><strong>allow-query-on</strong></span>,
+ <span class="command"><strong>allow-query-cache</strong></span>,
+ <span class="command"><strong>allow-query-cache-on</strong></span>,
+ <span class="command"><strong>allow-transfer</strong></span>,
+ <span class="command"><strong>allow-update</strong></span>,
+ <span class="command"><strong>allow-update-forwarding</strong></span>,
+ <span class="command"><strong>blackhole</strong></span>, and
+ <span class="command"><strong>keep-response-order</strong></span> all use address match
+ lists. Similarly, the <span class="command"><strong>listen-on</strong></span> option will cause the
server to refuse queries on any of the machine's
addresses which do not match the list.
</p>
-<p>
+
+ <p>
Order of insertion is significant. If more than one element
in an ACL is found to match a given IP address or prefix,
preference will be given to the one that came
defines a subset of another element in the list should
come before the broader element, regardless of whether
either is negated. For example, in
- <span><strong class="command">1.2.3/24; ! 1.2.3.13;</strong></span>
+ <span class="command"><strong>1.2.3/24; ! 1.2.3.13;</strong></span>
the 1.2.3.13 element is completely useless because the
algorithm will match any lookup for 1.2.3.13 to the 1.2.3/24
- element. Using <span><strong class="command">! 1.2.3.13; 1.2.3/24</strong></span> fixes
+ element. Using <span class="command"><strong>! 1.2.3.13; 1.2.3/24</strong></span> fixes
that problem by having 1.2.3.13 blocked by the negation, but
all other 1.2.3.* hosts fall through.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2564126"></a>Comment Syntax</h3></div></div></div>
-<p>
+<a name="id-1.7.5.6"></a>Comment Syntax</h3></div></div></div>
+
+
+ <p>
The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for
comments to appear
anywhere that whitespace may appear in a <acronym class="acronym">BIND</acronym> configuration
file. To appeal to programmers of all kinds, they can be written
in the C, C++, or shell/perl style.
</p>
-<div class="sect3" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2564141"></a>Syntax</h4></div></div></div>
-<p>
+<a name="id-1.7.5.6.4"></a>Syntax</h4></div></div></div>
+
+
+ <p>
</p>
<pre class="programlisting">/* This is a <acronym class="acronym">BIND</acronym> comment as in C */</pre>
<p>
# and perl</pre>
<p>
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2564171"></a>Definition and Usage</h4></div></div></div>
-<p>
+<a name="id-1.7.5.6.5"></a>Definition and Usage</h4></div></div></div>
+
+ <p>
Comments may appear anywhere that whitespace may appear in
a <acronym class="acronym">BIND</acronym> configuration file.
</p>
-<p>
C-style comments start with the two characters /* (slash,
star) and end with */ (star, slash). Because they are completely
delimited with these characters, they can be used to comment only
a portion of a line or to span multiple lines.
</p>
-<p>
C-style comments cannot be nested. For example, the following
is not valid because the entire comment ends with the first */:
</p>
-<p>
</p>
<pre class="programlisting">/* This is the start of a comment.
<p>
</p>
-<p>
+
+ <p>
C++-style comments start with the two characters // (slash,
slash) and continue to the end of the physical line. They cannot
be continued across multiple physical lines; to have one logical
comment span multiple lines, each line must use the // pair.
For example:
</p>
-<p>
</p>
<pre class="programlisting">// This is the start of a comment. The next line
<p>
</p>
-<p>
Shell-style (or perl-style, if you prefer) comments start
with the character <code class="literal">#</code> (number sign)
and continue to the end of the
physical line, as in C++ comments.
For example:
</p>
-<p>
+
+ <p>
</p>
<pre class="programlisting"># This is the start of a comment. The next line
<p>
</p>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
+
+ <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Warning</h3>
-<p>
You cannot use the semicolon (`;') character
to start a comment such as you would in a zone file. The
semicolon indicates the end of a configuration
statement.
</p>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="Configuration_File_Grammar"></a>Configuration File Grammar</h2></div></div></div>
-<p>
+
+
+ <p>
A <acronym class="acronym">BIND</acronym> 9 configuration consists of
statements and comments.
Statements end with a semicolon. Statements and comments are the
statements contain a block of sub-statements, which are also
terminated with a semicolon.
</p>
-<p>
+
+ <p>
The following statements are supported:
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.336in" class="1">
+<col width="3.778in" class="2">
</colgroup>
<tbody>
<tr>
<td>
- <p><span><strong class="command">acl</strong></span></p>
+ <p><span class="command"><strong>acl</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">controls</strong></span></p>
+ <p><span class="command"><strong>controls</strong></span></p>
</td>
<td>
<p>
declares control channels to be used
- by the <span><strong class="command">rndc</strong></span> utility.
+ by the <span class="command"><strong>rndc</strong></span> utility.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">include</strong></span></p>
+ <p><span class="command"><strong>include</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">key</strong></span></p>
+ <p><span class="command"><strong>key</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">logging</strong></span></p>
+ <p><span class="command"><strong>logging</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">lwres</strong></span></p>
+ <p><span class="command"><strong>lwres</strong></span></p>
</td>
<td>
<p>
- configures <span><strong class="command">named</strong></span> to
- also act as a light-weight resolver daemon (<span><strong class="command">lwresd</strong></span>).
+ configures <span class="command"><strong>named</strong></span> to
+ also act as a light-weight resolver daemon (<span class="command"><strong>lwresd</strong></span>).
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">masters</strong></span></p>
+ <p><span class="command"><strong>masters</strong></span></p>
</td>
<td>
<p>
defines a named masters list for
inclusion in stub and slave zones'
- <span><strong class="command">masters</strong></span> or
- <span><strong class="command">also-notify</strong></span> lists.
+ <span class="command"><strong>masters</strong></span> or
+ <span class="command"><strong>also-notify</strong></span> lists.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">options</strong></span></p>
+ <p><span class="command"><strong>options</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">server</strong></span></p>
+ <p><span class="command"><strong>server</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">statistics-channels</strong></span></p>
+ <p><span class="command"><strong>statistics-channels</strong></span></p>
</td>
<td>
<p>
declares communication channels to get access to
- <span><strong class="command">named</strong></span> statistics.
+ <span class="command"><strong>named</strong></span> statistics.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">trusted-keys</strong></span></p>
+ <p><span class="command"><strong>trusted-keys</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">managed-keys</strong></span></p>
+ <p><span class="command"><strong>managed-keys</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">view</strong></span></p>
+ <p><span class="command"><strong>view</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">zone</strong></span></p>
+ <p><span class="command"><strong>zone</strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
-<p>
- The <span><strong class="command">logging</strong></span> and
- <span><strong class="command">options</strong></span> statements may only occur once
+</table>
+ </div>
+
+ <p>
+ The <span class="command"><strong>logging</strong></span> and
+ <span class="command"><strong>options</strong></span> statements may only occur once
per
configuration.
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2574276"></a><span><strong class="command">acl</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">acl</strong></span> acl-name {
+<a name="id-1.7.6.7"></a><span class="command"><strong>acl</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>acl</strong></span> acl-name {
address_match_list
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="acl"></a><span><strong class="command">acl</strong></span> Statement Definition and
+<a name="acl"></a><span class="command"><strong>acl</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">acl</strong></span> statement assigns a symbolic
+
+
+ <p>
+ The <span class="command"><strong>acl</strong></span> statement assigns a symbolic
name to an address match list. It gets its name from a primary
use of address match lists: Access Control Lists (ACLs).
</p>
-<p>
+
+ <p>
The following ACLs are built-in:
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.130in" class="1">
+<col width="4.000in" class="2">
</colgroup>
<tbody>
<tr>
<td>
- <p><span><strong class="command">any</strong></span></p>
+ <p><span class="command"><strong>any</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">none</strong></span></p>
+ <p><span class="command"><strong>none</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">localhost</strong></span></p>
+ <p><span class="command"><strong>localhost</strong></span></p>
</td>
<td>
<p>
Matches the IPv4 and IPv6 addresses of all network
interfaces on the system. When addresses are
- added or removed, the <span><strong class="command">localhost</strong></span>
+ added or removed, the <span class="command"><strong>localhost</strong></span>
ACL element is updated to reflect the changes.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">localnets</strong></span></p>
+ <p><span class="command"><strong>localnets</strong></span></p>
</td>
<td>
<p>
Matches any host on an IPv4 or IPv6 network
for which the system has an interface.
When addresses are added or removed,
- the <span><strong class="command">localnets</strong></span>
+ the <span class="command"><strong>localnets</strong></span>
ACL element is updated to reflect the changes.
Some systems do not provide a way to determine the prefix
lengths of
local IPv6 addresses.
- In such a case, <span><strong class="command">localnets</strong></span>
+ In such a case, <span class="command"><strong>localnets</strong></span>
only matches the local
- IPv6 addresses, just like <span><strong class="command">localhost</strong></span>.
+ IPv6 addresses, just like <span class="command"><strong>localhost</strong></span>.
</p>
</td>
</tr>
</tbody>
-</table></div>
-</div>
-<div class="sect2" lang="en">
+</table>
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2574466"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">controls</strong></span> {
+<a name="id-1.7.6.9"></a><span class="command"><strong>controls</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>controls</strong></span> {
[ inet ( ip_addr | * ) [ port ip_port ]
allow { <em class="replaceable"><code> address_match_list </code></em> }
keys { <em class="replaceable"><code>key_list</code></em> }; ]
[ unix ...; ]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="controls_statement_definition_and_usage"></a><span><strong class="command">controls</strong></span> Statement Definition and
+<a name="controls_statement_definition_and_usage"></a><span class="command"><strong>controls</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">controls</strong></span> statement declares control
+
+
+ <p>
+ The <span class="command"><strong>controls</strong></span> statement declares control
channels to be used by system administrators to control the
operation of the name server. These control channels are
- used by the <span><strong class="command">rndc</strong></span> utility to send
+ used by the <span class="command"><strong>rndc</strong></span> utility to send
commands to and retrieve non-DNS results from a name server.
</p>
-<p>
- An <span><strong class="command">inet</strong></span> control channel is a TCP socket
- listening at the specified <span><strong class="command">ip_port</strong></span> on the
- specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6
- address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code> (asterisk) is
+
+ <p>
+ An <span class="command"><strong>inet</strong></span> control channel is a TCP socket
+ listening at the specified <span class="command"><strong>ip_port</strong></span> on the
+ specified <span class="command"><strong>ip_addr</strong></span>, which can be an IPv4 or IPv6
+ address. An <span class="command"><strong>ip_addr</strong></span> of <code class="literal">*</code> (asterisk) is
interpreted as the IPv4 wildcard address; connections will be
accepted on any of the system's IPv4 addresses.
To listen on the IPv6 wildcard address,
- use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>.
- If you will only use <span><strong class="command">rndc</strong></span> on the local host,
+ use an <span class="command"><strong>ip_addr</strong></span> of <code class="literal">::</code>.
+ If you will only use <span class="command"><strong>rndc</strong></span> on the local host,
using the loopback address (<code class="literal">127.0.0.1</code>
or <code class="literal">::1</code>) is recommended for maximum security.
</p>
-<p>
+
+ <p>
If no port is specified, port 953 is used. The asterisk
- "<code class="literal">*</code>" cannot be used for <span><strong class="command">ip_port</strong></span>.
+ "<code class="literal">*</code>" cannot be used for <span class="command"><strong>ip_port</strong></span>.
</p>
-<p>
+
+ <p>
The ability to issue commands over the control channel is
- restricted by the <span><strong class="command">allow</strong></span> and
- <span><strong class="command">keys</strong></span> clauses.
+ restricted by the <span class="command"><strong>allow</strong></span> and
+ <span class="command"><strong>keys</strong></span> clauses.
Connections to the control channel are permitted based on the
- <span><strong class="command">address_match_list</strong></span>. This is for simple
- IP address based filtering only; any <span><strong class="command">key_id</strong></span>
- elements of the <span><strong class="command">address_match_list</strong></span>
+ <span class="command"><strong>address_match_list</strong></span>. This is for simple
+ IP address based filtering only; any <span class="command"><strong>key_id</strong></span>
+ elements of the <span class="command"><strong>address_match_list</strong></span>
are ignored.
</p>
-<p>
- A <span><strong class="command">unix</strong></span> control channel is a UNIX domain
+
+ <p>
+ A <span class="command"><strong>unix</strong></span> control channel is a UNIX domain
socket listening at the specified path in the file system.
- Access to the socket is specified by the <span><strong class="command">perm</strong></span>,
- <span><strong class="command">owner</strong></span> and <span><strong class="command">group</strong></span> clauses.
+ Access to the socket is specified by the <span class="command"><strong>perm</strong></span>,
+ <span class="command"><strong>owner</strong></span> and <span class="command"><strong>group</strong></span> clauses.
Note on some platforms (SunOS and Solaris) the permissions
- (<span><strong class="command">perm</strong></span>) are applied to the parent directory
+ (<span class="command"><strong>perm</strong></span>) are applied to the parent directory
as the permissions on the socket itself are ignored.
</p>
-<p>
+
+ <p>
The primary authorization mechanism of the command
- channel is the <span><strong class="command">key_list</strong></span>, which
- contains a list of <span><strong class="command">key_id</strong></span>s.
- Each <span><strong class="command">key_id</strong></span> in the <span><strong class="command">key_list</strong></span>
+ channel is the <span class="command"><strong>key_list</strong></span>, which
+ contains a list of <span class="command"><strong>key_id</strong></span>s.
+ Each <span class="command"><strong>key_id</strong></span> in the <span class="command"><strong>key_list</strong></span>
is authorized to execute commands over the control channel.
- See <a href="Bv9ARM.ch03.html#rndc">Remote Name Daemon Control application</a> in <a href="Bv9ARM.ch03.html#admin_tools" title="Administrative Tools">the section called “Administrative Tools”</a>)
- for information about configuring keys in <span><strong class="command">rndc</strong></span>.
+ See <a class="xref" href="Bv9ARM.ch03.html#rndc">Remote Name Daemon Control application</a> in <a class="xref" href="Bv9ARM.ch03.html#admin_tools" title="Administrative Tools">the section called “Administrative Tools”</a>)
+ for information about configuring keys in <span class="command"><strong>rndc</strong></span>.
</p>
-<p>
- If no <span><strong class="command">controls</strong></span> statement is present,
- <span><strong class="command">named</strong></span> will set up a default
+
+ <p>
+ If no <span class="command"><strong>controls</strong></span> statement is present,
+ <span class="command"><strong>named</strong></span> will set up a default
control channel listening on the loopback address 127.0.0.1
and its IPv6 counterpart ::1.
- In this case, and also when the <span><strong class="command">controls</strong></span> statement
- is present but does not have a <span><strong class="command">keys</strong></span> clause,
- <span><strong class="command">named</strong></span> will attempt to load the command channel key
+ In this case, and also when the <span class="command"><strong>controls</strong></span> statement
+ is present but does not have a <span class="command"><strong>keys</strong></span> clause,
+ <span class="command"><strong>named</strong></span> will attempt to load the command channel key
from the file <code class="filename">rndc.key</code> in
<code class="filename">/etc</code> (or whatever <code class="varname">sysconfdir</code>
was specified as when <acronym class="acronym">BIND</acronym> was built).
To create a <code class="filename">rndc.key</code> file, run
<strong class="userinput"><code>rndc-confgen -a</code></strong>.
</p>
-<p>
+
+ <p>
The <code class="filename">rndc.key</code> feature was created to
ease the transition of systems from <acronym class="acronym">BIND</acronym> 8,
which did not have digital signatures on its command channel
- messages and thus did not have a <span><strong class="command">keys</strong></span> clause.
+ messages and thus did not have a <span class="command"><strong>keys</strong></span> clause.
It makes it possible to use an existing <acronym class="acronym">BIND</acronym> 8
configuration file in <acronym class="acronym">BIND</acronym> 9 unchanged,
- and still have <span><strong class="command">rndc</strong></span> work the same way
- <span><strong class="command">ndc</strong></span> worked in BIND 8, simply by executing the
+ and still have <span class="command"><strong>rndc</strong></span> work the same way
+ <span class="command"><strong>ndc</strong></span> worked in BIND 8, simply by executing the
command <strong class="userinput"><code>rndc-confgen -a</code></strong> after BIND 9 is
installed.
</p>
-<p>
+
+ <p>
Since the <code class="filename">rndc.key</code> feature
is only intended to allow the backward-compatible usage of
<acronym class="acronym">BIND</acronym> 8 configuration files, this
those things. The <code class="filename">rndc.key</code> file
also has its
permissions set such that only the owner of the file (the user that
- <span><strong class="command">named</strong></span> is running as) can access it.
+ <span class="command"><strong>named</strong></span> is running as) can access it.
If you
desire greater flexibility in allowing other users to access
- <span><strong class="command">rndc</strong></span> commands, then you need to create
+ <span class="command"><strong>rndc</strong></span> commands, then you need to create
a
<code class="filename">rndc.conf</code> file and make it group
readable by a group
that contains the users who should have access.
</p>
-<p>
+
+ <p>
To disable the command channel, use an empty
- <span><strong class="command">controls</strong></span> statement:
- <span><strong class="command">controls { };</strong></span>.
+ <span class="command"><strong>controls</strong></span> statement:
+ <span class="command"><strong>controls { };</strong></span>.
</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2574893"></a><span><strong class="command">include</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">include</strong></span> <em class="replaceable"><code>filename</code></em>;</pre>
-</div>
-<div class="sect2" lang="en">
+<a name="id-1.7.6.11"></a><span class="command"><strong>include</strong></span> Statement Grammar</h3></div></div></div>
+
+ <pre class="programlisting"><span class="command"><strong>include</strong></span> <em class="replaceable"><code>filename</code></em>;</pre>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2574910"></a><span><strong class="command">include</strong></span> Statement Definition and
+<a name="id-1.7.6.12"></a><span class="command"><strong>include</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">include</strong></span> statement inserts the
- specified file at the point where the <span><strong class="command">include</strong></span>
- statement is encountered. The <span><strong class="command">include</strong></span>
+
+
+ <p>
+ The <span class="command"><strong>include</strong></span> statement inserts the
+ specified file at the point where the <span class="command"><strong>include</strong></span>
+ statement is encountered. The <span class="command"><strong>include</strong></span>
statement facilitates the administration of configuration
files
by permitting the reading or writing of some things but not
others. For example, the statement could include private keys
that are readable only by the name server.
</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2574934"></a><span><strong class="command">key</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">key</strong></span> <em class="replaceable"><code>key_id</code></em> {
+<a name="id-1.7.6.13"></a><span class="command"><strong>key</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>key</strong></span> <em class="replaceable"><code>key_id</code></em> {
algorithm <em class="replaceable"><code>algorithm_id</code></em>;
secret <em class="replaceable"><code>secret_string</code></em>;
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2574957"></a><span><strong class="command">key</strong></span> Statement Definition and Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">key</strong></span> statement defines a shared
- secret key for use with TSIG (see <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>)
+<a name="id-1.7.6.14"></a><span class="command"><strong>key</strong></span> Statement Definition and Usage</h3></div></div></div>
+
+
+ <p>
+ The <span class="command"><strong>key</strong></span> statement defines a shared
+ secret key for use with TSIG (see <a class="xref" href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>)
or the command channel
- (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
- Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and
+ (see <a class="xref" href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called “<span class="command"><strong>controls</strong></span> Statement Definition and
Usage”</a>).
</p>
-<p>
- The <span><strong class="command">key</strong></span> statement can occur at the
+
+ <p>
+ The <span class="command"><strong>key</strong></span> statement can occur at the
top level
- of the configuration file or inside a <span><strong class="command">view</strong></span>
- statement. Keys defined in top-level <span><strong class="command">key</strong></span>
+ of the configuration file or inside a <span class="command"><strong>view</strong></span>
+ statement. Keys defined in top-level <span class="command"><strong>key</strong></span>
statements can be used in all views. Keys intended for use in
- a <span><strong class="command">controls</strong></span> statement
- (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
- Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and
+ a <span class="command"><strong>controls</strong></span> statement
+ (see <a class="xref" href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called “<span class="command"><strong>controls</strong></span> Statement Definition and
Usage”</a>)
must be defined at the top level.
</p>
-<p>
+
+ <p>
The <em class="replaceable"><code>key_id</code></em>, also known as the
key name, is a domain name uniquely identifying the key. It can
- be used in a <span><strong class="command">server</strong></span>
+ be used in a <span class="command"><strong>server</strong></span>
statement to cause requests sent to that
server to be signed with this key, or in address match lists to
verify that incoming requests have been signed with a key
matching this name, algorithm, and secret.
</p>
-<p>
+
+ <p>
The <em class="replaceable"><code>algorithm_id</code></em> is a string
that specifies a security/authentication algorithm. The
- <span><strong class="command">named</strong></span> server supports <code class="literal">hmac-md5</code>,
+ <span class="command"><strong>named</strong></span> server supports <code class="literal">hmac-md5</code>,
<code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
<code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>
and <code class="literal">hmac-sha512</code> TSIG authentication.
to be used by the algorithm, and is treated as a base-64
encoded string.
</p>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2575051"></a><span><strong class="command">logging</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">logging</strong></span> {
- [ <span><strong class="command">channel</strong></span> <em class="replaceable"><code>channel_name</code></em> {
- ( <span><strong class="command">file</strong></span> <em class="replaceable"><code>path_name</code></em>
- [ <span><strong class="command">versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <span><strong class="command">unlimited</strong></span> ) ]
- [ <span><strong class="command">size</strong></span> <em class="replaceable"><code>size_spec</code></em> ]
- | <span><strong class="command">syslog</strong></span> <em class="replaceable"><code>syslog_facility</code></em>
- | <span><strong class="command">stderr</strong></span>
- | <span><strong class="command">null</strong></span> );
- [ <span><strong class="command">severity</strong></span> (<code class="option">critical</code> | <code class="option">error</code> | <code class="option">warning</code> | <code class="option">notice</code> |
+<a name="id-1.7.6.15"></a><span class="command"><strong>logging</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>logging</strong></span> {
+ [ <span class="command"><strong>channel</strong></span> <em class="replaceable"><code>channel_name</code></em> {
+ ( <span class="command"><strong>file</strong></span> <em class="replaceable"><code>path_name</code></em>
+ [ <span class="command"><strong>versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <span class="command"><strong>unlimited</strong></span> ) ]
+ [ <span class="command"><strong>size</strong></span> <em class="replaceable"><code>size_spec</code></em> ]
+ | <span class="command"><strong>syslog</strong></span> <em class="replaceable"><code>syslog_facility</code></em>
+ | <span class="command"><strong>stderr</strong></span>
+ | <span class="command"><strong>null</strong></span> );
+ [ <span class="command"><strong>severity</strong></span> (<code class="option">critical</code> | <code class="option">error</code> | <code class="option">warning</code> | <code class="option">notice</code> |
<code class="option">info</code> | <code class="option">debug</code> [ <em class="replaceable"><code>level</code></em> ] | <code class="option">dynamic</code> ); ]
- [ <span><strong class="command">print-category</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
- [ <span><strong class="command">print-severity</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
- [ <span><strong class="command">print-time</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
- [ <span><strong class="command">buffered</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
+ [ <span class="command"><strong>print-category</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
+ [ <span class="command"><strong>print-severity</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
+ [ <span class="command"><strong>print-time</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
+ [ <span class="command"><strong>buffered</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
}; ]
- [ <span><strong class="command">category</strong></span> <em class="replaceable"><code>category_name</code></em> {
+ [ <span class="command"><strong>category</strong></span> <em class="replaceable"><code>category_name</code></em> {
<em class="replaceable"><code>channel_name</code></em> ; [ <em class="replaceable"><code>channel_name</code></em> ; ... ]
}; ]
...
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2575187"></a><span><strong class="command">logging</strong></span> Statement Definition and
+<a name="id-1.7.6.16"></a><span class="command"><strong>logging</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">logging</strong></span> statement configures a
+
+
+ <p>
+ The <span class="command"><strong>logging</strong></span> statement configures a
wide
- variety of logging options for the name server. Its <span><strong class="command">channel</strong></span> phrase
+ variety of logging options for the name server. Its <span class="command"><strong>channel</strong></span> phrase
associates output methods, format options and severity levels with
- a name that can then be used with the <span><strong class="command">category</strong></span> phrase
+ a name that can then be used with the <span class="command"><strong>category</strong></span> phrase
to select how various classes of messages are logged.
</p>
-<p>
- Only one <span><strong class="command">logging</strong></span> statement is used to
+ Only one <span class="command"><strong>logging</strong></span> statement is used to
define
- as many channels and categories as are wanted. If there is no <span><strong class="command">logging</strong></span> statement,
+ as many channels and categories as are wanted. If there is no <span class="command"><strong>logging</strong></span> statement,
the logging configuration will be:
</p>
+
<pre class="programlisting">logging {
category default { default_syslog; default_debug; };
category unmatched { null; };
};
</pre>
-<p>
- If <span><strong class="command">named</strong></span> is started with the
+
+ <p>
+ If <span class="command"><strong>named</strong></span> is started with the
<code class="option">-L</code> option, it logs to the specified file
at startup, instead of using syslog. In this case the logging
configuration will be:
</p>
+
<pre class="programlisting">logging {
category default { default_logfile; default_debug; };
category unmatched { null; };
};
</pre>
-<p>
+
+ <p>
In <acronym class="acronym">BIND</acronym> 9, the logging configuration
is only established when
the entire configuration file has been parsed. In <acronym class="acronym">BIND</acronym> 8, it was
- established as soon as the <span><strong class="command">logging</strong></span>
+ established as soon as the <span class="command"><strong>logging</strong></span>
statement
was parsed. When the server is starting up, all logging messages
regarding syntax errors in the configuration file go to the default
channels, or to standard error if the <code class="option">-g</code> option
was specified.
</p>
-<div class="sect3" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2575252"></a>The <span><strong class="command">channel</strong></span> Phrase</h4></div></div></div>
-<p>
+<a name="id-1.7.6.16.9"></a>The <span class="command"><strong>channel</strong></span> Phrase</h4></div></div></div>
+
+
+ <p>
All log output goes to one or more <span class="emphasis"><em>channels</em></span>;
you can make as many of them as you want.
</p>
-<p>
+
+ <p>
Every channel definition must include a destination clause that
says whether messages selected for the channel go to a file, to a
particular syslog facility, to the standard error stream, or are
discarded. It can optionally also limit the message severity level
that will be accepted by the channel (the default is
- <span><strong class="command">info</strong></span>), and whether to include a
- <span><strong class="command">named</strong></span>-generated time stamp, the
+ <span class="command"><strong>info</strong></span>), and whether to include a
+ <span class="command"><strong>named</strong></span>-generated time stamp, the
category name
and/or severity level (the default is not to include any).
</p>
-<p>
- The <span><strong class="command">null</strong></span> destination clause
+
+ <p>
+ The <span class="command"><strong>null</strong></span> destination clause
causes all messages sent to the channel to be discarded;
in that case, other options for the channel are meaningless.
</p>
-<p>
- The <span><strong class="command">file</strong></span> destination clause directs
+
+ <p>
+ The <span class="command"><strong>file</strong></span> destination clause directs
the channel
to a disk file. It can include limitations
both on how large the file is allowed to become, and how many
versions
of the file will be saved each time the file is opened.
</p>
-<p>
- If you use the <span><strong class="command">versions</strong></span> log file
+
+ <p>
+ If you use the <span class="command"><strong>versions</strong></span> log file
option, then
- <span><strong class="command">named</strong></span> will retain that many backup
+ <span class="command"><strong>named</strong></span> will retain that many backup
versions of the file by
renaming them when opening. For example, if you choose to keep
three old versions
<code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed
to <code class="filename">lamers.log.1</code>, and <code class="filename">lamers.log</code> is
renamed to <code class="filename">lamers.log.0</code>.
- You can say <span><strong class="command">versions unlimited</strong></span> to
+ You can say <span class="command"><strong>versions unlimited</strong></span> to
not limit
the number of versions.
- If a <span><strong class="command">size</strong></span> option is associated with
+ If a <span class="command"><strong>size</strong></span> option is associated with
the log file,
then renaming is only done when the file being opened exceeds the
indicated size. No backup versions are kept by default; any
existing
log file is simply appended.
</p>
-<p>
- The <span><strong class="command">size</strong></span> option for files is used
+
+ <p>
+ The <span class="command"><strong>size</strong></span> option for files is used
to limit log
- growth. If the file ever exceeds the size, then <span><strong class="command">named</strong></span> will
- stop writing to the file unless it has a <span><strong class="command">versions</strong></span> option
+ growth. If the file ever exceeds the size, then <span class="command"><strong>named</strong></span> will
+ stop writing to the file unless it has a <span class="command"><strong>versions</strong></span> option
associated with it. If backup versions are kept, the files are
rolled as
described above and a new one begun. If there is no
- <span><strong class="command">versions</strong></span> option, no more data will
+ <span class="command"><strong>versions</strong></span> option, no more data will
be written to the log
until some out-of-band mechanism removes or truncates the log to
less than the
the
file.
</p>
-<p>
- Example usage of the <span><strong class="command">size</strong></span> and
- <span><strong class="command">versions</strong></span> options:
+
+ <p>
+ Example usage of the <span class="command"><strong>size</strong></span> and
+ <span class="command"><strong>versions</strong></span> options:
</p>
+
<pre class="programlisting">channel an_example_channel {
file "example.log" versions 3 size 20m;
print-time yes;
print-category yes;
};
</pre>
-<p>
- The <span><strong class="command">syslog</strong></span> destination clause
+
+ <p>
+ The <span class="command"><strong>syslog</strong></span> destination clause
directs the
channel to the system log. Its argument is a
- syslog facility as described in the <span><strong class="command">syslog</strong></span> man
- page. Known facilities are <span><strong class="command">kern</strong></span>, <span><strong class="command">user</strong></span>,
- <span><strong class="command">mail</strong></span>, <span><strong class="command">daemon</strong></span>, <span><strong class="command">auth</strong></span>,
- <span><strong class="command">syslog</strong></span>, <span><strong class="command">lpr</strong></span>, <span><strong class="command">news</strong></span>,
- <span><strong class="command">uucp</strong></span>, <span><strong class="command">cron</strong></span>, <span><strong class="command">authpriv</strong></span>,
- <span><strong class="command">ftp</strong></span>, <span><strong class="command">local0</strong></span>, <span><strong class="command">local1</strong></span>,
- <span><strong class="command">local2</strong></span>, <span><strong class="command">local3</strong></span>, <span><strong class="command">local4</strong></span>,
- <span><strong class="command">local5</strong></span>, <span><strong class="command">local6</strong></span> and
- <span><strong class="command">local7</strong></span>, however not all facilities
+ syslog facility as described in the <span class="command"><strong>syslog</strong></span> man
+ page. Known facilities are <span class="command"><strong>kern</strong></span>, <span class="command"><strong>user</strong></span>,
+ <span class="command"><strong>mail</strong></span>, <span class="command"><strong>daemon</strong></span>, <span class="command"><strong>auth</strong></span>,
+ <span class="command"><strong>syslog</strong></span>, <span class="command"><strong>lpr</strong></span>, <span class="command"><strong>news</strong></span>,
+ <span class="command"><strong>uucp</strong></span>, <span class="command"><strong>cron</strong></span>, <span class="command"><strong>authpriv</strong></span>,
+ <span class="command"><strong>ftp</strong></span>, <span class="command"><strong>local0</strong></span>, <span class="command"><strong>local1</strong></span>,
+ <span class="command"><strong>local2</strong></span>, <span class="command"><strong>local3</strong></span>, <span class="command"><strong>local4</strong></span>,
+ <span class="command"><strong>local5</strong></span>, <span class="command"><strong>local6</strong></span> and
+ <span class="command"><strong>local7</strong></span>, however not all facilities
are supported on
all operating systems.
- How <span><strong class="command">syslog</strong></span> will handle messages
+ How <span class="command"><strong>syslog</strong></span> will handle messages
sent to
- this facility is described in the <span><strong class="command">syslog.conf</strong></span> man
- page. If you have a system which uses a very old version of <span><strong class="command">syslog</strong></span> that
- only uses two arguments to the <span><strong class="command">openlog()</strong></span> function,
+ this facility is described in the <span class="command"><strong>syslog.conf</strong></span> man
+ page. If you have a system which uses a very old version of <span class="command"><strong>syslog</strong></span> that
+ only uses two arguments to the <span class="command"><strong>openlog()</strong></span> function,
then this clause is silently ignored.
</p>
-<p>
On Windows machines syslog messages are directed to the EventViewer.
</p>
-<p>
- The <span><strong class="command">severity</strong></span> clause works like <span><strong class="command">syslog</strong></span>'s
+ The <span class="command"><strong>severity</strong></span> clause works like <span class="command"><strong>syslog</strong></span>'s
"priorities", except that they can also be used if you are writing
- straight to a file rather than using <span><strong class="command">syslog</strong></span>.
+ straight to a file rather than using <span class="command"><strong>syslog</strong></span>.
Messages which are not at least of the severity level given will
not be selected for the channel; messages of higher severity
levels
will be accepted.
</p>
-<p>
- If you are using <span><strong class="command">syslog</strong></span>, then the <span><strong class="command">syslog.conf</strong></span> priorities
+ If you are using <span class="command"><strong>syslog</strong></span>, then the <span class="command"><strong>syslog.conf</strong></span> priorities
will also determine what eventually passes through. For example,
- defining a channel facility and severity as <span><strong class="command">daemon</strong></span> and <span><strong class="command">debug</strong></span> but
- only logging <span><strong class="command">daemon.warning</strong></span> via <span><strong class="command">syslog.conf</strong></span> will
- cause messages of severity <span><strong class="command">info</strong></span> and
- <span><strong class="command">notice</strong></span> to
- be dropped. If the situation were reversed, with <span><strong class="command">named</strong></span> writing
- messages of only <span><strong class="command">warning</strong></span> or higher,
- then <span><strong class="command">syslogd</strong></span> would
+ defining a channel facility and severity as <span class="command"><strong>daemon</strong></span> and <span class="command"><strong>debug</strong></span> but
+ only logging <span class="command"><strong>daemon.warning</strong></span> via <span class="command"><strong>syslog.conf</strong></span> will
+ cause messages of severity <span class="command"><strong>info</strong></span> and
+ <span class="command"><strong>notice</strong></span> to
+ be dropped. If the situation were reversed, with <span class="command"><strong>named</strong></span> writing
+ messages of only <span class="command"><strong>warning</strong></span> or higher,
+ then <span class="command"><strong>syslogd</strong></span> would
print all messages it received from the channel.
</p>
-<p>
- The <span><strong class="command">stderr</strong></span> destination clause
+
+ <p>
+ The <span class="command"><strong>stderr</strong></span> destination clause
directs the
channel to the server's standard error stream. This is intended
for
example
when debugging a configuration.
</p>
-<p>
+
+ <p>
The server can supply extensive debugging information when
it is in debugging mode. If the server's global debug level is
greater
than zero, then debugging mode will be active. The global debug
- level is set either by starting the <span><strong class="command">named</strong></span> server
+ level is set either by starting the <span class="command"><strong>named</strong></span> server
with the <code class="option">-d</code> flag followed by a positive integer,
- or by running <span><strong class="command">rndc trace</strong></span>.
+ or by running <span class="command"><strong>rndc trace</strong></span>.
The global debug level
- can be set to zero, and debugging mode turned off, by running <span><strong class="command">rndc
+ can be set to zero, and debugging mode turned off, by running <span class="command"><strong>rndc
notrace</strong></span>. All debugging messages in the server have a debug
level, and higher debug levels give more detailed output. Channels
that specify a specific debug severity, for example:
</p>
+
<pre class="programlisting">channel specific_debug_level {
file "foo";
severity debug 3;
};
</pre>
-<p>
+
+ <p>
will get debugging output of level 3 or less any time the
server is in debugging mode, regardless of the global debugging
- level. Channels with <span><strong class="command">dynamic</strong></span>
+ level. Channels with <span class="command"><strong>dynamic</strong></span>
severity use the
server's global debug level to determine what messages to print.
</p>
-<p>
- If <span><strong class="command">print-time</strong></span> has been turned on,
+ If <span class="command"><strong>print-time</strong></span> has been turned on,
then
- the date and time will be logged. <span><strong class="command">print-time</strong></span> may
- be specified for a <span><strong class="command">syslog</strong></span> channel,
+ the date and time will be logged. <span class="command"><strong>print-time</strong></span> may
+ be specified for a <span class="command"><strong>syslog</strong></span> channel,
but is usually
- pointless since <span><strong class="command">syslog</strong></span> also logs
+ pointless since <span class="command"><strong>syslog</strong></span> also logs
the date and
- time. If <span><strong class="command">print-category</strong></span> is
+ time. If <span class="command"><strong>print-category</strong></span> is
requested, then the
- category of the message will be logged as well. Finally, if <span><strong class="command">print-severity</strong></span> is
- on, then the severity level of the message will be logged. The <span><strong class="command">print-</strong></span> options may
+ category of the message will be logged as well. Finally, if <span class="command"><strong>print-severity</strong></span> is
+ on, then the severity level of the message will be logged. The <span class="command"><strong>print-</strong></span> options may
be used in any combination, and will always be printed in the
following
order: time, category, severity. Here is an example where all
- three <span><strong class="command">print-</strong></span> options
+ three <span class="command"><strong>print-</strong></span> options
are on:
</p>
-<p>
+
+ <p>
<code class="computeroutput">28-Feb-2000 15:05:32.863 general: notice: running</code>
</p>
-<p>
- If <span><strong class="command">buffered</strong></span> has been turned on the output
+
+ <p>
+ If <span class="command"><strong>buffered</strong></span> has been turned on the output
to files will not be flushed after each log entry. By default
all log messages are flushed.
</p>
-<p>
+
+ <p>
There are four predefined channels that are used for
- <span><strong class="command">named</strong></span>'s default logging as follows.
- If <span><strong class="command">named</strong></span> is started with the
+ <span class="command"><strong>named</strong></span>'s default logging as follows.
+ If <span class="command"><strong>named</strong></span> is started with the
<code class="option">-L</code> then a
- fifth channel <span><strong class="command">default_logfile</strong></span> is added.
+ fifth channel <span class="command"><strong>default_logfile</strong></span> is added.
How they are
- used is described in <a href="Bv9ARM.ch06.html#the_category_phrase" title="The category Phrase">the section called “The <span><strong class="command">category</strong></span> Phrase”</a>.
+ used is described in <a class="xref" href="Bv9ARM.ch06.html#the_category_phrase" title="The category Phrase">the section called “The <span class="command"><strong>category</strong></span> Phrase”</a>.
</p>
+
<pre class="programlisting">channel default_syslog {
// send to syslog's daemon facility
syslog daemon;
severity dynamic;
};
</pre>
-<p>
- The <span><strong class="command">default_debug</strong></span> channel has the
+
+ <p>
+ The <span class="command"><strong>default_debug</strong></span> channel has the
special
property that it only produces output when the server's debug
level is
nonzero. It normally writes to a file called <code class="filename">named.run</code>
in the server's working directory.
</p>
-<p>
+
+ <p>
For security reasons, when the <code class="option">-u</code>
command line option is used, the <code class="filename">named.run</code> file
- is created only after <span><strong class="command">named</strong></span> has
+ is created only after <span class="command"><strong>named</strong></span> has
changed to the
- new UID, and any debug output generated while <span><strong class="command">named</strong></span> is
+ new UID, and any debug output generated while <span class="command"><strong>named</strong></span> is
starting up and still running as root is discarded. If you need
to capture this output, you must run the server with the <code class="option">-L</code>
option to specify a default logfile, or the <code class="option">-g</code>
option to log to standard error which you can redirect to a file.
</p>
-<p>
+
+ <p>
Once a channel is defined, it cannot be redefined. Thus you
cannot alter the built-in channels directly, but you can modify
the default logging by pointing categories at channels you have
defined.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="the_category_phrase"></a>The <span><strong class="command">category</strong></span> Phrase</h4></div></div></div>
-<p>
+<a name="the_category_phrase"></a>The <span class="command"><strong>category</strong></span> Phrase</h4></div></div></div>
+
+
+ <p>
There are many categories, so you can send the logs you want
to see wherever you want, without seeing logs you don't want. If
you don't specify a list of channels for a category, then log
messages
- in that category will be sent to the <span><strong class="command">default</strong></span> category
+ in that category will be sent to the <span class="command"><strong>default</strong></span> category
instead. If you don't specify a default category, the following
"default default" is used:
</p>
+
<pre class="programlisting">category default { default_syslog; default_debug; };
</pre>
-<p>
- If you start <span><strong class="command">named</strong></span> with the
+
+ <p>
+ If you start <span class="command"><strong>named</strong></span> with the
<code class="option">-L</code> option then the default category is:
</p>
+
<pre class="programlisting">category default { default_logfile; default_debug; };
</pre>
-<p>
+
+ <p>
As an example, let's say you want to log security events to
a file, but you also want keep the default logging behavior. You'd
specify the following:
</p>
+
<pre class="programlisting">channel my_security_channel {
file "my_security_file";
severity info;
default_syslog;
default_debug;
};</pre>
-<p>
- To discard all messages in a category, specify the <span><strong class="command">null</strong></span> channel:
+
+ <p>
+ To discard all messages in a category, specify the <span class="command"><strong>null</strong></span> channel:
</p>
+
<pre class="programlisting">category xfer-out { null; };
category notify { null; };
</pre>
-<p>
+
+ <p>
Following are the available categories and brief descriptions
of the types of log information they contain. More
categories may be added in future <acronym class="acronym">BIND</acronym> releases.
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.150in" class="1">
+<col width="3.350in" class="2">
</colgroup>
<tbody>
<tr>
<td>
- <p><span><strong class="command">client</strong></span></p>
+ <p><span class="command"><strong>client</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">cname</strong></span></p>
+ <p><span class="command"><strong>cname</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">config</strong></span></p>
+ <p><span class="command"><strong>config</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">database</strong></span></p>
+ <p><span class="command"><strong>database</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">default</strong></span></p>
+ <p><span class="command"><strong>default</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">delegation-only</strong></span></p>
+ <p><span class="command"><strong>delegation-only</strong></span></p>
</td>
<td>
<p>
Delegation only. Logs queries that have been
forced to NXDOMAIN as the result of a
delegation-only zone or a
- <span><strong class="command">delegation-only</strong></span> in a
+ <span class="command"><strong>delegation-only</strong></span> in a
forward, hint or stub zone declaration.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">dispatch</strong></span></p>
+ <p><span class="command"><strong>dispatch</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">dnssec</strong></span></p>
+ <p><span class="command"><strong>dnssec</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">dnssec</strong></span></p>
+ <p><span class="command"><strong>dnstap</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">edns-disabled</strong></span></p>
+ <p><span class="command"><strong>edns-disabled</strong></span></p>
</td>
<td>
<p>
number of false-positive reports.
</p>
<p>
- Note: eventually <span><strong class="command">named</strong></span> will have to stop
+ Note: eventually <span class="command"><strong>named</strong></span> will have to stop
treating such timeouts as due to RFC 1034 non
compliance and start treating it as plain
packet loss. Falsely classifying packet
</tr>
<tr>
<td>
- <p><span><strong class="command">general</strong></span></p>
+ <p><span class="command"><strong>general</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">lame-servers</strong></span></p>
+ <p><span class="command"><strong>lame-servers</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">network</strong></span></p>
+ <p><span class="command"><strong>network</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">notify</strong></span></p>
+ <p><span class="command"><strong>notify</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">queries</strong></span></p>
+ <p><span class="command"><strong>queries</strong></span></p>
</td>
<td>
<p>
Specify where queries should be logged to.
</p>
<p>
- At startup, specifying the category <span><strong class="command">queries</strong></span> will also
- enable query logging unless <span><strong class="command">querylog</strong></span> option has been
+ At startup, specifying the category <span class="command"><strong>queries</strong></span> will also
+ enable query logging unless <span class="command"><strong>querylog</strong></span> option has been
specified.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">query-errors</strong></span></p>
+ <p><span class="command"><strong>query-errors</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">rate-limit</strong></span></p>
+ <p><span class="command"><strong>rate-limit</strong></span></p>
</td>
<td>
<p>
The start, periodic, and final notices of the
rate limiting of a stream of responses are logged at
- <span><strong class="command">info</strong></span> severity in this category.
+ <span class="command"><strong>info</strong></span> severity in this category.
These messages include a hash value of the domain name
of the response and the name itself,
except when there is insufficient memory to record
</p>
<p>
Rate limiting of individual requests
- is logged in the <span><strong class="command">query-errors</strong></span> category.
+ is logged in the <span class="command"><strong>query-errors</strong></span> category.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">resolver</strong></span></p>
+ <p><span class="command"><strong>resolver</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">rpz</strong></span></p>
+ <p><span class="command"><strong>rpz</strong></span></p>
</td>
<td>
<p>
Information about errors in response policy zone files,
rewritten responses, and at the highest
- <span><strong class="command">debug</strong></span> levels, mere rewriting
+ <span class="command"><strong>debug</strong></span> levels, mere rewriting
attempts.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">security</strong></span></p>
+ <p><span class="command"><strong>security</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">spill</strong></span></p>
+ <p><span class="command"><strong>spill</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">unmatched</strong></span></p>
+ <p><span class="command"><strong>unmatched</strong></span></p>
</td>
<td>
<p>
- Messages that <span><strong class="command">named</strong></span> was unable to determine the
- class of or for which there was no matching <span><strong class="command">view</strong></span>.
- A one line summary is also logged to the <span><strong class="command">client</strong></span> category.
+ Messages that <span class="command"><strong>named</strong></span> was unable to determine the
+ class of or for which there was no matching <span class="command"><strong>view</strong></span>.
+ A one line summary is also logged to the <span class="command"><strong>client</strong></span> category.
This category is best sent to a file or stderr, by
default it is sent to
- the <span><strong class="command">null</strong></span> channel.
+ the <span class="command"><strong>null</strong></span> channel.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">update</strong></span></p>
+ <p><span class="command"><strong>update</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">update-security</strong></span></p>
+ <p><span class="command"><strong>update-security</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">xfer-in</strong></span></p>
+ <p><span class="command"><strong>xfer-in</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">xfer-out</strong></span></p>
+ <p><span class="command"><strong>xfer-out</strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
+</table>
</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2576060"></a>The <span><strong class="command">query-errors</strong></span> Category</h4></div></div></div>
-<p>
- The <span><strong class="command">query-errors</strong></span> category is
+<a name="id-1.7.6.16.11"></a>The <span class="command"><strong>query-errors</strong></span> Category</h4></div></div></div>
+ The <span class="command"><strong>query-errors</strong></span> category is
specifically intended for debugging purposes: To identify
why and how specific queries result in responses which
indicate an error.
Messages of this category are therefore only logged
- with <span><strong class="command">debug</strong></span> levels.
+ with <span class="command"><strong>debug</strong></span> levels.
</p>
-<p>
+
+ <p>
At the debug levels of 1 or higher, each response with the
rcode of SERVFAIL is logged as follows:
</p>
-<p>
<code class="computeroutput">client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880</code>
</p>
-<p>
This means an error resulting in SERVFAIL was
detected at line 3880 of source file
<code class="filename">query.c</code>.
help identify the cause of SERVFAIL for an
authoritative server.
</p>
-<p>
At the debug levels of 2 or higher, detailed context
information of recursive resolutions that resulted in
SERVFAIL is logged.
The log message will look like as follows:
</p>
-<p>
</p>
<pre class="programlisting">
</pre>
<p>
</p>
-<p>
The first part before the colon shows that a recursive
resolution for AAAA records of www.example.com completed
in 30.000183 seconds and the final result that led to the
SERVFAIL was determined at line 2970 of source file
<code class="filename">resolver.c</code>.
</p>
-<p>
The following part shows the detected final result and the
latest result of DNSSEC validation.
The latter is always success when no validation attempt
to a timeout in 30 seconds.
DNSSEC validation was probably not attempted.
</p>
-<p>
The last part enclosed in square brackets shows statistics
information collected for this particular resolution
attempt.
The meaning of the other fields is summarized in the
following table.
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.150in" class="1">
+<col width="3.350in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
At the debug levels of 3 or higher, the same messages
as those at the debug 1 level are logged for other errors
than SERVFAIL.
Note that negative responses such as NXDOMAIN are not
regarded as errors here.
</p>
-<p>
At the debug levels of 4 or higher, the same messages
as those at the debug 2 level are logged for other errors
than SERVFAIL.
This is because any unexpected results can be difficult to
debug in the recursion case.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2576512"></a><span><strong class="command">lwres</strong></span> Statement Grammar</h3></div></div></div>
-<p>
- This is the grammar of the <span><strong class="command">lwres</strong></span>
+<a name="id-1.7.6.17"></a><span class="command"><strong>lwres</strong></span> Statement Grammar</h3></div></div></div>
+
+
+ <p>
+ This is the grammar of the <span class="command"><strong>lwres</strong></span>
statement in the <code class="filename">named.conf</code> file:
</p>
-<pre class="programlisting"><span><strong class="command">lwres</strong></span> {
+
+<pre class="programlisting"><span class="command"><strong>lwres</strong></span> {
[<span class="optional"> listen-on { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
[<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> view <em class="replaceable"><code>view_name</code></em>; </span>]
[<span class="optional"> lwres-clients <em class="replaceable"><code>number</code></em>; </span>]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2576677"></a><span><strong class="command">lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">lwres</strong></span> statement configures the
+<a name="id-1.7.6.18"></a><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
+
+
+ <p>
+ The <span class="command"><strong>lwres</strong></span> statement configures the
name
server to also act as a lightweight resolver server. (See
- <a href="Bv9ARM.ch05.html#lwresd" title="Running a Resolver Daemon">the section called “Running a Resolver Daemon”</a>.) There may be multiple
- <span><strong class="command">lwres</strong></span> statements configuring
+ <a class="xref" href="Bv9ARM.ch05.html#lwresd" title="Running a Resolver Daemon">the section called “Running a Resolver Daemon”</a>.) There may be multiple
+ <span class="command"><strong>lwres</strong></span> statements configuring
lightweight resolver servers with different properties.
</p>
-<p>
- The <span><strong class="command">listen-on</strong></span> statement specifies a
+
+ <p>
+ The <span class="command"><strong>listen-on</strong></span> statement specifies a
list of
IPv4 addresses (and ports) that this instance of a lightweight
resolver daemon
127.0.0.1,
port 921.
</p>
-<p>
- The <span><strong class="command">view</strong></span> statement binds this
+
+ <p>
+ The <span class="command"><strong>view</strong></span> statement binds this
instance of a
lightweight resolver daemon to a view in the DNS namespace, so that
the
is
used, and if there is no default view, an error is triggered.
</p>
-<p>
- The <span><strong class="command">search</strong></span> statement is equivalent to
+
+ <p>
+ The <span class="command"><strong>search</strong></span> statement is equivalent to
the
- <span><strong class="command">search</strong></span> statement in
+ <span class="command"><strong>search</strong></span> statement in
<code class="filename">/etc/resolv.conf</code>. It provides a
list of domains
which are appended to relative names in queries.
</p>
-<p>
- The <span><strong class="command">ndots</strong></span> statement is equivalent to
+
+ <p>
+ The <span class="command"><strong>ndots</strong></span> statement is equivalent to
the
- <span><strong class="command">ndots</strong></span> statement in
+ <span class="command"><strong>ndots</strong></span> statement in
<code class="filename">/etc/resolv.conf</code>. It indicates the
minimum
number of dots in a relative domain name that should result in an
exact match lookup before search path elements are appended.
</p>
-<p>
The <code class="option">lwres-tasks</code> statement specifies the number
of worker threads the lightweight resolver will dedicate to serving
clients. By default the number is the same as the number of CPUs on
the system; this can be overridden using the <code class="option">-n</code>
command line option when starting the server.
</p>
-<p>
The <code class="option">lwres-clients</code> specifies
the number of client objects per thread the lightweight
resolver should create to serve client queries.
By default, if the lightweight resolver runs as a part
- of <span><strong class="command">named</strong></span>, 256 client objects are
- created for each task; if it runs as <span><strong class="command">lwresd</strong></span>,
+ of <span class="command"><strong>named</strong></span>, 256 client objects are
+ created for each task; if it runs as <span class="command"><strong>lwresd</strong></span>,
1024 client objects are created for each thread. The maximum
value is 32768; higher values will be silently ignored and
the maximum will be used instead.
Note that setting too high a value may overconsume
system resources.
</p>
-<p>
The maximum number of client queries that the lightweight
resolver can handle at any one time equals
<code class="option">lwres-tasks</code> times <code class="option">lwres-clients</code>.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2576773"></a><span><strong class="command">masters</strong></span> Statement Grammar</h3></div></div></div>
+<a name="id-1.7.6.19"></a><span class="command"><strong>masters</strong></span> Statement Grammar</h3></div></div></div>
+
+
<pre class="programlisting">
-<span><strong class="command">masters</strong></span> <em class="replaceable"><code>name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> |
+<span class="command"><strong>masters</strong></span> <em class="replaceable"><code>name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> |
<em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] };
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2576822"></a><span><strong class="command">masters</strong></span> Statement Definition and
+<a name="id-1.7.6.20"></a><span class="command"><strong>masters</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p><span><strong class="command">masters</strong></span>
+
+ <p><span class="command"><strong>masters</strong></span>
lists allow for a common set of masters to be easily used by
- multiple stub and slave zones in their <span><strong class="command">masters</strong></span>
- or <span><strong class="command">also-notify</strong></span> lists.
+ multiple stub and slave zones in their <span class="command"><strong>masters</strong></span>
+ or <span class="command"><strong>also-notify</strong></span> lists.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2576843"></a><span><strong class="command">options</strong></span> Statement Grammar</h3></div></div></div>
-<p>
- This is the grammar of the <span><strong class="command">options</strong></span>
+<a name="id-1.7.6.21"></a><span class="command"><strong>options</strong></span> Statement Grammar</h3></div></div></div>
+
+
+ <p>
+ This is the grammar of the <span class="command"><strong>options</strong></span>
statement in the <code class="filename">named.conf</code> file:
</p>
-<pre class="programlisting"><span><strong class="command">options</strong></span> {
+
+<pre class="programlisting"><span class="command"><strong>options</strong></span> {
[<span class="optional"> attach-cache <em class="replaceable"><code>cache_name</code></em>; </span>]
[<span class="optional"> version <em class="replaceable"><code>version_string</code></em>; </span>]
[<span class="optional"> hostname <em class="replaceable"><code>hostname_string</code></em>; </span>]
[<span class="optional">v6-bias <em class="replaceable"><code>number</code></em> ; </span>]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="options"></a><span><strong class="command">options</strong></span> Statement Definition and
+<a name="options"></a><span class="command"><strong>options</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">options</strong></span> statement sets up global
+
+
+ <p>
+ The <span class="command"><strong>options</strong></span> statement sets up global
options
to be used by <acronym class="acronym">BIND</acronym>. This statement
may appear only
- once in a configuration file. If there is no <span><strong class="command">options</strong></span>
+ once in a configuration file. If there is no <span class="command"><strong>options</strong></span>
statement, an options block with each option set to its default will
be used.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">attach-cache</strong></span></span></dt>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>attach-cache</strong></span></span></dt>
<dd>
-<p>
Allows multiple views to share a single cache
database.
Each view has its own cache database by default, but
share a single cache to save memory and possibly
improve resolution efficiency by using this option.
</p>
-<p>
- The <span><strong class="command">attach-cache</strong></span> option
- may also be specified in <span><strong class="command">view</strong></span>
+
+ <p>
+ The <span class="command"><strong>attach-cache</strong></span> option
+ may also be specified in <span class="command"><strong>view</strong></span>
statements, in which case it overrides the
- global <span><strong class="command">attach-cache</strong></span> option.
+ global <span class="command"><strong>attach-cache</strong></span> option.
</p>
-<p>
+
+ <p>
The <em class="replaceable"><code>cache_name</code></em> specifies
the cache to be shared.
- When the <span><strong class="command">named</strong></span> server configures
+ When the <span class="command"><strong>named</strong></span> server configures
views which are supposed to share a cache, it
creates a cache with the specified name for the
first view of these sharing views.
The rest of the views will simply refer to the
already created cache.
</p>
-<p>
+
+ <p>
One common configuration to share a cache would be to
allow all views to share a single cache.
This can be done by specifying
- the <span><strong class="command">attach-cache</strong></span> as a global
+ the <span class="command"><strong>attach-cache</strong></span> as a global
option with an arbitrary name.
</p>
-<p>
+
+ <p>
Another possible operation is to allow a subset of
all views to share a cache while the others to
retain their own caches.
For example, if there are three views A, B, and C,
and only A and B should share a cache, specify the
- <span><strong class="command">attach-cache</strong></span> option as a view A (or
+ <span class="command"><strong>attach-cache</strong></span> option as a view A (or
B)'s option, referring to the other view name:
</p>
+
<pre class="programlisting">
view "A" {
// this view has its own cache
...
};
</pre>
-<p>
+
+ <p>
Views that share a cache must have the same policy
on configurable parameters that may affect caching.
The current implementation requires the following
configurable options be consistent among these
views:
- <span><strong class="command">check-names</strong></span>,
- <span><strong class="command">cleaning-interval</strong></span>,
- <span><strong class="command">dnssec-accept-expired</strong></span>,
- <span><strong class="command">dnssec-validation</strong></span>,
- <span><strong class="command">max-cache-ttl</strong></span>,
- <span><strong class="command">max-ncache-ttl</strong></span>,
- <span><strong class="command">max-cache-size</strong></span>, and
- <span><strong class="command">zero-no-soa-ttl</strong></span>.
+ <span class="command"><strong>check-names</strong></span>,
+ <span class="command"><strong>cleaning-interval</strong></span>,
+ <span class="command"><strong>dnssec-accept-expired</strong></span>,
+ <span class="command"><strong>dnssec-validation</strong></span>,
+ <span class="command"><strong>max-cache-ttl</strong></span>,
+ <span class="command"><strong>max-ncache-ttl</strong></span>,
+ <span class="command"><strong>max-cache-size</strong></span>, and
+ <span class="command"><strong>zero-no-soa-ttl</strong></span>.
</p>
-<p>
+
+ <p>
Note that there may be other parameters that may
cause confusion if they are inconsistent for
different views that share a single cache.
configuration differences in different views do
not cause disruption with a shared cache.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">directory</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>directory</strong></span></span></dt>
+<dd>
+ <p>
The working directory of the server.
Any non-absolute pathnames in the configuration file will be
taken
which the server
was started. The directory specified should be an absolute
path.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnstap</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnstap</strong></span></span></dt>
<dd>
-<p>
- <span><strong class="command">dnstap</strong></span> is a fast, flexible method
+ <span class="command"><strong>dnstap</strong></span> is a fast, flexible method
for capturing and logging DNS traffic. Developed by
Robert Edmonds at Farsight Security, Inc., and supported
- by multiple DNS implementations, <span><strong class="command">dnstap</strong></span>
+ by multiple DNS implementations, <span class="command"><strong>dnstap</strong></span>
uses
- <span><strong class="command">libfstrm</strong></span> (a lightweight high-speed
+ <span class="command"><strong>libfstrm</strong></span> (a lightweight high-speed
framing library, see
- <a href="https://github.com/farsightsec/fstrm" target="_top">https://github.com/farsightsec/fstrm</a>) to send
+ <a class="ulink" href="https://github.com/farsightsec/fstrm" target="_top">https://github.com/farsightsec/fstrm</a>) to send
event payloads which are encoded using Protocol Buffers
- (<span><strong class="command">libprotobuf-c</strong></span>, a mechanism for
+ (<span class="command"><strong>libprotobuf-c</strong></span>, a mechanism for
serializing structured data developed
by Google, Inc.; see
- <a href="https://developers.google.com/protocol-buffers/" target="_top">https://developers.google.com/protocol-buffers</a>).
+ <a class="ulink" href="https://developers.google.com/protocol-buffers/" target="_top">https://developers.google.com/protocol-buffers</a>).
</p>
-<p>
- To enable <span><strong class="command">dnstap</strong></span> at compile time,
- the <span><strong class="command">fstrm</strong></span> and <span><strong class="command">protobuf-c</strong></span>
+ To enable <span class="command"><strong>dnstap</strong></span> at compile time,
+ the <span class="command"><strong>fstrm</strong></span> and <span class="command"><strong>protobuf-c</strong></span>
libraries must be available, and BIND must be configured with
<code class="option">--enable-dnstap</code>.
</p>
-<p>
- The <span><strong class="command">dnstap</strong></span> option is a bracketed list
+ The <span class="command"><strong>dnstap</strong></span> option is a bracketed list
of message types to be logged. These may be set differently
for each view. Supported types are <code class="literal">client</code>,
<code class="literal">auth</code>, <code class="literal">resolver</code>, and
<code class="literal">forwarder</code>. Specifying type
- <code class="literal">all</code> will cause all <span><strong class="command">dnstap</strong></span>
+ <code class="literal">all</code> will cause all <span class="command"><strong>dnstap</strong></span>
messages to be logged, regardless of type.
</p>
-<p>
Each type may take an additional argument to indicate whether
to log <code class="literal">query</code> messages or
<code class="literal">response</code> messages; if not specified,
both queries and responses are logged.
</p>
-<p>
Example: To log all authoritative queries and responses,
recursive client responses, and upstream queries sent by
the resolver, use:
</pre>
<p>
</p>
-<p>
- Logged <span><strong class="command">dnstap</strong></span> messages can be parsed
- using the <span><strong class="command">dnstap-read</strong></span> utility (see
- <a href="man.dnstap-read.html" title="dnstap-read"><span class="refentrytitle"><span class="application">dnstap-read</span></span>(1)</a> for details).
+ Logged <span class="command"><strong>dnstap</strong></span> messages can be parsed
+ using the <span class="command"><strong>dnstap-read</strong></span> utility (see
+ <a class="xref" href="man.dnstap-read.html" title="dnstap-read"><span class="refentrytitle"><span class="application">dnstap-read</span></span>(1)</a> for details).
</p>
-<p>
- For more information on <span><strong class="command">dnstap</strong></span>, see
- <a href="http://dnstap.info" target="_top">http://dnstap.info</a>.
+ For more information on <span class="command"><strong>dnstap</strong></span>, see
+ <a class="ulink" href="http://dnstap.info" target="_top">http://dnstap.info</a>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">dnstap-output</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnstap-output</strong></span></span></dt>
<dd>
-<p>
- Configures the path to which the <span><strong class="command">dnstap</strong></span>
- frame stream will be sent if <span><strong class="command">dnstap</strong></span>
+ Configures the path to which the <span class="command"><strong>dnstap</strong></span>
+ frame stream will be sent if <span class="command"><strong>dnstap</strong></span>
is enabled at compile time and active.
</p>
-<p>
The first argument is either <code class="literal">file</code> or
<code class="literal">unix</code>, indicating whether the destination
is a file or a UNIX domain socket. The second argument
is the path of the file or socket. (Note: when using a
- socket, <span><strong class="command">dnstap</strong></span> messages will
+ socket, <span class="command"><strong>dnstap</strong></span> messages will
only be sent if another process such as
- <span><strong class="command">fstrm_capture</strong></span>
- (provided with <span><strong class="command">libfstrm</strong></span>) is listening on
+ <span class="command"><strong>fstrm_capture</strong></span>
+ (provided with <span class="command"><strong>libfstrm</strong></span>) is listening on
the socket.)
</p>
-<p>
- <span><strong class="command">dnstap-output</strong></span> can only be set globally
- in <span><strong class="command">options</strong></span>. Currently, it can only be
- set once while <span><strong class="command">named</strong></span> is running;
+ <span class="command"><strong>dnstap-output</strong></span> can only be set globally
+ in <span class="command"><strong>options</strong></span>. Currently, it can only be
+ set once while <span class="command"><strong>named</strong></span> is running;
once set, it cannot be changed by
- <span><strong class="command">rndc reload</strong></span> or
- <span><strong class="command">rndc reconfig</strong></span>.
+ <span class="command"><strong>rndc reload</strong></span> or
+ <span class="command"><strong>rndc reconfig</strong></span>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">dnstap-identity</strong></span></span></dt>
-<dd><p>
- Specifies an <span><strong class="command">identity</strong></span> string to send in
- <span><strong class="command">dnstap</strong></span> messages. If set to
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnstap-identity</strong></span></span></dt>
+<dd>
+ <p>
+ Specifies an <span class="command"><strong>identity</strong></span> string to send in
+ <span class="command"><strong>dnstap</strong></span> messages. If set to
<code class="literal">hostname</code>, which is the default, the
server's hostname will be sent. If set to
<code class="literal">none</code>, no identity string will be sent.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnstap-version</strong></span></span></dt>
-<dd><p>
- Specifies a <span><strong class="command">version</strong></span> string to send in
- <span><strong class="command">dnstap</strong></span> messages. The default is the
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnstap-version</strong></span></span></dt>
+<dd>
+ <p>
+ Specifies a <span class="command"><strong>version</strong></span> string to send in
+ <span class="command"><strong>dnstap</strong></span> messages. The default is the
version number of the BIND release. If set to
<code class="literal">none</code>, no version string will be sent.
- </p></dd>
-<dt><span class="term"><span><strong class="command">geoip-directory</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>geoip-directory</strong></span></span></dt>
+<dd>
+ <p>
Specifies the directory containing GeoIP
<code class="filename">.dat</code> database files for GeoIP
initialization. By default, this option is unset
and the GeoIP support will use libGeoIP's
built-in directory.
- (For details, see <a href="Bv9ARM.ch06.html#acl" title="acl Statement Definition and
- Usage">the section called “<span><strong class="command">acl</strong></span> Statement Definition and
+ (For details, see <a class="xref" href="Bv9ARM.ch06.html#acl" title="acl Statement Definition and Usage">the section called “<span class="command"><strong>acl</strong></span> Statement Definition and
Usage”</a> about the
- <span><strong class="command">geoip</strong></span> ACL.)
- </p></dd>
-<dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>geoip</strong></span> ACL.)
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>key-directory</strong></span></span></dt>
+<dd>
+ <p>
When performing dynamic update of secure zones, the
directory where the public and private DNSSEC key files
should be found, if different than the current working
<code class="filename">bind.keys</code>,
<code class="filename">rndc.key</code> or
<code class="filename">session.key</code>.)
- </p></dd>
-<dt><span class="term"><span><strong class="command">managed-keys-directory</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>managed-keys-directory</strong></span></span></dt>
<dd>
-<p>
Specifies the directory in which to store the files that
track managed DNSSEC keys. By default, this is the working
directory.
</p>
-<p>
- If <span><strong class="command">named</strong></span> is not configured to use views,
+ If <span class="command"><strong>named</strong></span> is not configured to use views,
then managed keys for the server will be tracked in a single
file called <code class="filename">managed-keys.bind</code>.
Otherwise, managed keys will be tracked in separate files,
followed by the extension
<code class="filename">.mkeys</code>.
</p>
-<p>
(Note: in previous releases, file names for views
always used the SHA256 hash of the view name. To ensure
compatibility after upgrade, if a file using the old
name format is found to exist, it will be used instead
of the new format.)
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">named-xfer</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>named-xfer</strong></span></span></dt>
+<dd>
+ <p>
<span class="emphasis"><em>This option is obsolete.</em></span> It
was used in <acronym class="acronym">BIND</acronym> 8 to specify
- the pathname to the <span><strong class="command">named-xfer</strong></span>
+ the pathname to the <span class="command"><strong>named-xfer</strong></span>
program. In <acronym class="acronym">BIND</acronym> 9, no separate
- <span><strong class="command">named-xfer</strong></span> program is needed;
+ <span class="command"><strong>named-xfer</strong></span> program is needed;
its functionality is built into the name server.
- </p></dd>
-<dt><span class="term"><span><strong class="command">tkey-gssapi-keytab</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>tkey-gssapi-keytab</strong></span></span></dt>
+<dd>
+ <p>
The KRB5 keytab file to use for GSS-TSIG updates. If
this option is set and tkey-gssapi-credential is not
set, then updates will be allowed with any key
matching a principal in the specified keytab.
- </p></dd>
-<dt><span class="term"><span><strong class="command">tkey-gssapi-credential</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>tkey-gssapi-credential</strong></span></span></dt>
+<dd>
+ <p>
The security credential with which the server should
authenticate keys requested by the GSS-TSIG protocol.
Currently only Kerberos 5 authentication is available
The location keytab file can be overridden using the
tkey-gssapi-keytab option. Normally this principal is
of the form "<strong class="userinput"><code>DNS/</code></strong><code class="varname">server.domain</code>".
- To use GSS-TSIG, <span><strong class="command">tkey-domain</strong></span> must
+ To use GSS-TSIG, <span class="command"><strong>tkey-domain</strong></span> must
also be set if a specific keytab is not set with
tkey-gssapi-keytab.
- </p></dd>
-<dt><span class="term"><span><strong class="command">tkey-domain</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>tkey-domain</strong></span></span></dt>
+<dd>
+ <p>
The domain appended to the names of all shared keys
- generated with <span><strong class="command">TKEY</strong></span>. When a
- client requests a <span><strong class="command">TKEY</strong></span> exchange,
+ generated with <span class="command"><strong>TKEY</strong></span>. When a
+ client requests a <span class="command"><strong>TKEY</strong></span> exchange,
it may or may not specify the desired name for the
key. If present, the name of the shared key will
be <code class="varname">client specified part</code> +
<code class="varname">tkey-domain</code>. Otherwise, the
name of the shared key will be <code class="varname">random hex
digits</code> + <code class="varname">tkey-domain</code>.
- In most cases, the <span><strong class="command">domainname</strong></span>
+ In most cases, the <span class="command"><strong>domainname</strong></span>
should be the server's domain name, or an otherwise
non-existent subdomain like
"_tkey.<code class="varname">domainname</code>". If you are
using GSS-TSIG, this variable must be defined, unless
you specify a specific keytab using tkey-gssapi-keytab.
- </p></dd>
-<dt><span class="term"><span><strong class="command">tkey-dhkey</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>tkey-dhkey</strong></span></span></dt>
+<dd>
+ <p>
The Diffie-Hellman key used by the server
to generate shared keys with clients using the Diffie-Hellman
mode
- of <span><strong class="command">TKEY</strong></span>. The server must be
+ of <span class="command"><strong>TKEY</strong></span>. The server must be
able to load the
public and private keys from files in the working directory.
In
most cases, the keyname should be the server's host name.
- </p></dd>
-<dt><span class="term"><span><strong class="command">cache-file</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>cache-file</strong></span></span></dt>
+<dd>
+ <p>
This is for testing only. Do not use.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dump-file</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dump-file</strong></span></span></dt>
+<dd>
+ <p>
The pathname of the file the server dumps
the database to when instructed to do so with
- <span><strong class="command">rndc dumpdb</strong></span>.
+ <span class="command"><strong>rndc dumpdb</strong></span>.
If not specified, the default is <code class="filename">named_dump.db</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">memstatistics-file</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>memstatistics-file</strong></span></span></dt>
+<dd>
+ <p>
The pathname of the file the server writes memory
usage statistics to on exit. If not specified,
the default is <code class="filename">named.memstats</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">lock-file</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>lock-file</strong></span></span></dt>
<dd>
-<p>
- The pathname of a file on which <span><strong class="command">named</strong></span> will
+ The pathname of a file on which <span class="command"><strong>named</strong></span> will
attempt to acquire a file lock when starting up for
the first time; if unsuccessful, the server will
will terminate, under the assumption that another
server is already running. If not specified, the default is
<code class="filename">/var/run/named/named.lock</code>.
</p>
-<p>
- Specifying <span><strong class="command">lock-file none</strong></span> disables the
- use of a lock file. <span><strong class="command">lock-file</strong></span> is
- ignored if <span><strong class="command">named</strong></span> was run using the <code class="option">-X</code>
+ Specifying <span class="command"><strong>lock-file none</strong></span> disables the
+ use of a lock file. <span class="command"><strong>lock-file</strong></span> is
+ ignored if <span class="command"><strong>named</strong></span> was run using the <code class="option">-X</code>
option, which overrides it. Changes to
- <span><strong class="command">lock-file</strong></span> are ignored if
- <span><strong class="command">named</strong></span> is being reloaded or
+ <span class="command"><strong>lock-file</strong></span> are ignored if
+ <span class="command"><strong>named</strong></span> is being reloaded or
reconfigured; it is only effective when the server is
first started up.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">pid-file</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>pid-file</strong></span></span></dt>
+<dd>
+ <p>
The pathname of the file the server writes its process ID
in. If not specified, the default is
<code class="filename">/var/run/named/named.pid</code>.
The PID file is used by programs that want to send signals to
the running
- name server. Specifying <span><strong class="command">pid-file none</strong></span> disables the
+ name server. Specifying <span class="command"><strong>pid-file none</strong></span> disables the
use of a PID file — no file will be written and any
- existing one will be removed. Note that <span><strong class="command">none</strong></span>
+ existing one will be removed. Note that <span class="command"><strong>none</strong></span>
is a keyword, not a filename, and therefore is not enclosed
in
double quotes.
- </p></dd>
-<dt><span class="term"><span><strong class="command">recursing-file</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>recursing-file</strong></span></span></dt>
+<dd>
+ <p>
The pathname of the file the server dumps
the queries that are currently recursing when instructed
- to do so with <span><strong class="command">rndc recursing</strong></span>.
+ to do so with <span class="command"><strong>rndc recursing</strong></span>.
If not specified, the default is <code class="filename">named.recursing</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">statistics-file</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>statistics-file</strong></span></span></dt>
+<dd>
+ <p>
The pathname of the file the server appends statistics
- to when instructed to do so using <span><strong class="command">rndc stats</strong></span>.
+ to when instructed to do so using <span class="command"><strong>rndc stats</strong></span>.
If not specified, the default is <code class="filename">named.stats</code> in the
server's current directory. The format of the file is
described
- in <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">bindkeys-file</strong></span></span></dt>
-<dd><p>
+ in <a class="xref" href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>bindkeys-file</strong></span></span></dt>
+<dd>
+ <p>
The pathname of a file to override the built-in trusted
- keys provided by <span><strong class="command">named</strong></span>.
- See the discussion of <span><strong class="command">dnssec-lookaside</strong></span>
- and <span><strong class="command">dnssec-validation</strong></span> for details.
+ keys provided by <span class="command"><strong>named</strong></span>.
+ See the discussion of <span class="command"><strong>dnssec-lookaside</strong></span>
+ and <span class="command"><strong>dnssec-validation</strong></span> for details.
If not specified, the default is
<code class="filename">/etc/bind.keys</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">secroots-file</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>secroots-file</strong></span></span></dt>
+<dd>
+ <p>
The pathname of the file the server dumps
security roots to when instructed to do so with
- <span><strong class="command">rndc secroots</strong></span>.
+ <span class="command"><strong>rndc secroots</strong></span>.
If not specified, the default is
<code class="filename">named.secroots</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">session-keyfile</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>session-keyfile</strong></span></span></dt>
+<dd>
+ <p>
The pathname of the file into which to write a TSIG
- session key generated by <span><strong class="command">named</strong></span> for use by
- <span><strong class="command">nsupdate -l</strong></span>. If not specified, the
+ session key generated by <span class="command"><strong>named</strong></span> for use by
+ <span class="command"><strong>nsupdate -l</strong></span>. If not specified, the
default is <code class="filename">/var/run/named/session.key</code>.
- (See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>, and in
+ (See <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>, and in
particular the discussion of the
- <span><strong class="command">update-policy</strong></span> statement's
+ <span class="command"><strong>update-policy</strong></span> statement's
<strong class="userinput"><code>local</code></strong> option for more
information about this feature.)
- </p></dd>
-<dt><span class="term"><span><strong class="command">session-keyname</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>session-keyname</strong></span></span></dt>
+<dd>
+ <p>
The key name to use for the TSIG session key.
If not specified, the default is "local-ddns".
- </p></dd>
-<dt><span class="term"><span><strong class="command">session-keyalg</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>session-keyalg</strong></span></span></dt>
+<dd>
+ <p>
The algorithm to use for the TSIG session key.
Valid values are hmac-sha1, hmac-sha224, hmac-sha256,
hmac-sha384, hmac-sha512 and hmac-md5. If not
specified, the default is hmac-sha256.
- </p></dd>
-<dt><span class="term"><span><strong class="command">port</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>port</strong></span></span></dt>
+<dd>
+ <p>
The UDP/TCP port number the server uses for
receiving and sending DNS protocol traffic.
The default is 53. This option is mainly intended for server
a server using a port other than 53 will not be able to
communicate with
the global DNS.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dscp</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dscp</strong></span></span></dt>
+<dd>
+ <p>
The global Differentiated Services Code Point (DSCP)
value to classify outgoing DNS traffic on operating
systems that support DSCP. Valid values are 0 through 63.
It is not configured by default.
- </p></dd>
-<dt><span class="term"><span><strong class="command">random-device</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>random-device</strong></span></span></dt>
+<dd>
+ <p>
The source of entropy to be used by the server. Entropy is
primarily needed
for DNSSEC operations, such as TKEY transactions and dynamic
is
<code class="filename">/dev/random</code>
(or equivalent) when present, and none otherwise. The
- <span><strong class="command">random-device</strong></span> option takes
+ <span class="command"><strong>random-device</strong></span> option takes
effect during
the initial configuration load at server startup time and
is ignored on subsequent reloads.
- </p></dd>
-<dt><span class="term"><span><strong class="command">preferred-glue</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>preferred-glue</strong></span></span></dt>
+<dd>
+ <p>
If specified, the listed type (A or AAAA) will be emitted
before other glue
in the additional section of a query response.
The default is to prefer A records when responding
to queries that arrived via IPv4 and AAAA when
responding to queries that arrived via IPv6.
- </p></dd>
+ </p>
+ </dd>
<dt>
-<a name="root_delegation_only"></a><span class="term"><span><strong class="command">root-delegation-only</strong></span></span>
+<a name="root_delegation_only"></a><span class="term"><span class="command"><strong>root-delegation-only</strong></span></span>
</dt>
<dd>
-<p>
Turn on enforcement of delegation-only in TLDs
(top level domains) and root zones with an optional
exclude list.
</p>
-<p>
DS queries are expected to be made to and be answered by
delegation only zones. Such queries and responses are
treated as an exception to delegation-only processing
and are not converted to NXDOMAIN responses provided
a CNAME is not discovered at the query name.
</p>
-<p>
If a delegation only zone server also serves a child
zone it is not always possible to determine whether
an answer comes from the delegation only zone or the
all these checks there is still a possibility of
false negatives when a child zone is being served.
</p>
-<p>
Similarly false positives can arise from empty nodes
(no records at the name) in the delegation only zone
when the query type is not ANY.
</p>
-<p>
Note some TLDs are not delegation only (e.g. "DE", "LV",
"US" and "MUSEUM"). This list is not exhaustive.
</p>
+
<pre class="programlisting">
options {
root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
};
</pre>
-</dd>
-<dt><span class="term"><span><strong class="command">disable-algorithms</strong></span></span></dt>
+
+ </dd>
+<dt><span class="term"><span class="command"><strong>disable-algorithms</strong></span></span></dt>
<dd>
-<p>
Disable the specified DNSSEC algorithms at and below the
specified name.
- Multiple <span><strong class="command">disable-algorithms</strong></span>
+ Multiple <span class="command"><strong>disable-algorithms</strong></span>
statements are allowed.
- Only the best match <span><strong class="command">disable-algorithms</strong></span>
+ Only the best match <span class="command"><strong>disable-algorithms</strong></span>
clause will be used to determine which algorithms are used.
</p>
-<p>
If all supported algorithms are disabled, the zones covered
- by the <span><strong class="command">disable-algorithms</strong></span> will be treated
+ by the <span class="command"><strong>disable-algorithms</strong></span> will be treated
as insecure.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">disable-ds-digests</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>disable-ds-digests</strong></span></span></dt>
<dd>
-<p>
Disable the specified DS/DLV digest types at and below the
specified name.
- Multiple <span><strong class="command">disable-ds-digests</strong></span>
+ Multiple <span class="command"><strong>disable-ds-digests</strong></span>
statements are allowed.
- Only the best match <span><strong class="command">disable-ds-digests</strong></span>
+ Only the best match <span class="command"><strong>disable-ds-digests</strong></span>
clause will be used to determine which digest types are used.
</p>
-<p>
If all supported digest types are disabled, the zones covered
- by the <span><strong class="command">disable-ds-digests</strong></span> will be treated
+ by the <span class="command"><strong>disable-ds-digests</strong></span> will be treated
as insecure.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">dnssec-lookaside</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-lookaside</strong></span></span></dt>
<dd>
-<p>
- When set, <span><strong class="command">dnssec-lookaside</strong></span> provides the
+ When set, <span class="command"><strong>dnssec-lookaside</strong></span> provides the
validator with an alternate method to validate DNSKEY
records at the top of a zone. When a DNSKEY is at or
below a domain specified by the deepest
- <span><strong class="command">dnssec-lookaside</strong></span>, and the normal DNSSEC
+ <span class="command"><strong>dnssec-lookaside</strong></span>, and the normal DNSSEC
validation has left the key untrusted, the trust-anchor
will be appended to the key name and a DLV record will be
looked up to see if it can validate the key. If the DLV
record validates a DNSKEY (similarly to the way a DS
record does) the DNSKEY RRset is deemed to be trusted.
</p>
-<p>
- If <span><strong class="command">dnssec-lookaside</strong></span> is set to
+ If <span class="command"><strong>dnssec-lookaside</strong></span> is set to
<strong class="userinput"><code>auto</code></strong>, then built-in default
values for the DLV domain and trust anchor will be
used, along with a built-in key for validation.
</p>
-<p>
- If <span><strong class="command">dnssec-lookaside</strong></span> is set to
+ If <span class="command"><strong>dnssec-lookaside</strong></span> is set to
<strong class="userinput"><code>no</code></strong>, then dnssec-lookaside
is not used.
</p>
-<p>
The default DLV key is stored in the file
<code class="filename">bind.keys</code>;
- <span><strong class="command">named</strong></span> will load that key at
- startup if <span><strong class="command">dnssec-lookaside</strong></span> is set to
+ <span class="command"><strong>named</strong></span> will load that key at
+ startup if <span class="command"><strong>dnssec-lookaside</strong></span> is set to
<code class="constant">auto</code>. A copy of the file is
installed along with <acronym class="acronym">BIND</acronym> 9, and is
current as of the release date. If the DLV key expires, a
new copy of <code class="filename">bind.keys</code> can be downloaded
- from <a href="https://www.isc.org/solutions/dlv/" target="_top">https://www.isc.org/solutions/dlv/</a>.
+ from <a class="ulink" href="https://www.isc.org/solutions/dlv/" target="_top">https://www.isc.org/solutions/dlv/</a>.
</p>
-<p>
(To prevent problems if <code class="filename">bind.keys</code> is
not found, the current key is also compiled in to
- <span><strong class="command">named</strong></span>. Relying on this is not
- recommended, however, as it requires <span><strong class="command">named</strong></span>
+ <span class="command"><strong>named</strong></span>. Relying on this is not
+ recommended, however, as it requires <span class="command"><strong>named</strong></span>
to be recompiled with a new key when the DLV key expires.)
</p>
-<p>
- NOTE: <span><strong class="command">named</strong></span> only loads certain specific
+ NOTE: <span class="command"><strong>named</strong></span> only loads certain specific
keys from <code class="filename">bind.keys</code>: those for the
DLV zone and for the DNS root zone. The file cannot be
used to store keys for other zones.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">dnssec-must-be-secure</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-must-be-secure</strong></span></span></dt>
+<dd>
+ <p>
Specify hierarchies which must be or may not be secure
(signed and validated). If <strong class="userinput"><code>yes</code></strong>,
- then <span><strong class="command">named</strong></span> will only accept answers if
+ then <span class="command"><strong>named</strong></span> will only accept answers if
they are secure. If <strong class="userinput"><code>no</code></strong>, then normal
DNSSEC validation applies allowing for insecure answers to
be accepted. The specified domain must be under a
- <span><strong class="command">trusted-keys</strong></span> or
- <span><strong class="command">managed-keys</strong></span> statement, or
- <span><strong class="command">dnssec-lookaside</strong></span> must be active.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dns64</strong></span></span></dt>
+ <span class="command"><strong>trusted-keys</strong></span> or
+ <span class="command"><strong>managed-keys</strong></span> statement, or
+ <span class="command"><strong>dnssec-lookaside</strong></span> must be active.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dns64</strong></span></span></dt>
<dd>
-<p>
- This directive instructs <span><strong class="command">named</strong></span> to
+ This directive instructs <span class="command"><strong>named</strong></span> to
return mapped IPv4 addresses to AAAA queries when
there are no AAAA records. It is intended to be
used in conjunction with a NAT64. Each
- <span><strong class="command">dns64</strong></span> defines one DNS64 prefix.
+ <span class="command"><strong>dns64</strong></span> defines one DNS64 prefix.
Multiple DNS64 prefixes can be defined.
</p>
-<p>
Compatible IPv6 prefixes have lengths of 32, 40, 48, 56,
64 and 96 as per RFC 6052.
</p>
-<p>
Additionally a reverse IP6.ARPA zone will be created for
the prefix to provide a mapping from the IP6.ARPA names
to the corresponding IN-ADDR.ARPA names using synthesized
- CNAMEs. <span><strong class="command">dns64-server</strong></span> and
- <span><strong class="command">dns64-contact</strong></span> can be used to specify
+ CNAMEs. <span class="command"><strong>dns64-server</strong></span> and
+ <span class="command"><strong>dns64-contact</strong></span> can be used to specify
the name of the server and contact for the zones. These
are settable at the view / options level. These are
not settable on a per-prefix basis.
</p>
-<p>
- Each <span><strong class="command">dns64</strong></span> supports an optional
- <span><strong class="command">clients</strong></span> ACL that determines which
+ Each <span class="command"><strong>dns64</strong></span> supports an optional
+ <span class="command"><strong>clients</strong></span> ACL that determines which
clients are affected by this directive. If not defined,
it defaults to <strong class="userinput"><code>any;</code></strong>.
</p>
-<p>
- Each <span><strong class="command">dns64</strong></span> supports an optional
- <span><strong class="command">mapped</strong></span> ACL that selects which
+ Each <span class="command"><strong>dns64</strong></span> supports an optional
+ <span class="command"><strong>mapped</strong></span> ACL that selects which
IPv4 addresses are to be mapped in the corresponding
A RRset. If not defined it defaults to
<strong class="userinput"><code>any;</code></strong>.
</p>
-<p>
Normally, DNS64 won't apply to a domain name that
owns one or more AAAA records; these records will
simply be returned. The optional
- <span><strong class="command">exclude</strong></span> ACL allows specification
+ <span class="command"><strong>exclude</strong></span> ACL allows specification
of a list of IPv6 addresses that will be ignored
if they appear in a domain name's AAAA records, and
DNS64 will be applied to any A records the domain
- name owns. If not defined, <span><strong class="command">exclude</strong></span>
+ name owns. If not defined, <span class="command"><strong>exclude</strong></span>
defaults to none.
</p>
-<p>
- A optional <span><strong class="command">suffix</strong></span> can also
+ A optional <span class="command"><strong>suffix</strong></span> can also
be defined to set the bits trailing the mapped
IPv4 address bits. By default these bits are
set to <strong class="userinput"><code>::</code></strong>. The bits
matching the prefix and mapped IPv4 address
must be zero.
</p>
-<p>
- If <span><strong class="command">recursive-only</strong></span> is set to
- <span><strong class="command">yes</strong></span> the DNS64 synthesis will
+ If <span class="command"><strong>recursive-only</strong></span> is set to
+ <span class="command"><strong>yes</strong></span> the DNS64 synthesis will
only happen for recursive queries. The default
- is <span><strong class="command">no</strong></span>.
+ is <span class="command"><strong>no</strong></span>.
</p>
-<p>
- If <span><strong class="command">break-dnssec</strong></span> is set to
- <span><strong class="command">yes</strong></span> the DNS64 synthesis will
+ If <span class="command"><strong>break-dnssec</strong></span> is set to
+ <span class="command"><strong>yes</strong></span> the DNS64 synthesis will
happen even if the result, if validated, would
cause a DNSSEC validation failure. If this option
- is set to <span><strong class="command">no</strong></span> (the default), the DO
+ is set to <span class="command"><strong>no</strong></span> (the default), the DO
is set on the incoming query, and there are RRSIGs on
the applicable records, then synthesis will not happen.
</p>
suffix ::;
};
</pre>
-</dd>
-<dt><span class="term"><span><strong class="command">dnssec-loadkeys-interval</strong></span></span></dt>
-<dd><p>
- When a zone is configured with <span><strong class="command">auto-dnssec
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-loadkeys-interval</strong></span></span></dt>
+<dd>
+ <p>
+ When a zone is configured with <span class="command"><strong>auto-dnssec
maintain;</strong></span> its key repository must be checked
periodically to see if any new keys have been added
or any existing keys' timing metadata has been updated
- (see <a href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
- <a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The
- <span><strong class="command">dnssec-loadkeys-interval</strong></span> option
+ (see <a class="xref" href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
+ <a class="xref" href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The
+ <span class="command"><strong>dnssec-loadkeys-interval</strong></span> option
sets the frequency of automatic repository checks, in
minutes. The default is <code class="literal">60</code> (1 hour),
the minimum is <code class="literal">1</code> (1 minute), and the
maximum is <code class="literal">1440</code> (24 hours); any higher
value is silently reduced.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnssec-update-mode</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-update-mode</strong></span></span></dt>
<dd>
-<p>
If this option is set to its default value of
<code class="literal">maintain</code> in a zone of type
<code class="literal">master</code> which is DNSSEC-signed
and configured to allow dynamic updates (see
- <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>), and
- if <span><strong class="command">named</strong></span> has access to the
+ <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>), and
+ if <span class="command"><strong>named</strong></span> has access to the
private signing key(s) for the zone, then
- <span><strong class="command">named</strong></span> will automatically sign all new
+ <span class="command"><strong>named</strong></span> will automatically sign all new
or changed records and maintain signatures for the zone
by regenerating RRSIG records whenever they approach
their expiration date.
</p>
-<p>
If the option is changed to <code class="literal">no-resign</code>,
- then <span><strong class="command">named</strong></span> will sign all new or
+ then <span class="command"><strong>named</strong></span> will sign all new or
changed records, but scheduled maintenance of
signatures is disabled.
</p>
-<p>
- With either of these settings, <span><strong class="command">named</strong></span>
+ With either of these settings, <span class="command"><strong>named</strong></span>
will reject updates to a DNSSEC-signed zone when the
signing keys are inactive or unavailable to
- <span><strong class="command">named</strong></span>. (A planned third option,
+ <span class="command"><strong>named</strong></span>. (A planned third option,
<code class="literal">external</code>, will disable all automatic
signing and allow DNSSEC data to be submitted into a zone
via dynamic update; this is not yet implemented.)
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">nta-lifetime</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>nta-lifetime</strong></span></span></dt>
<dd>
-<p>
Species the default lifetime, in seconds,
that will be used for negative trust anchors added
- via <span><strong class="command">rndc nta</strong></span>.
+ via <span class="command"><strong>rndc nta</strong></span>.
</p>
-<p>
A negative trust anchor selectively disables
DNSSEC validation for zones that are known to be
failing because of misconfiguration rather than
an attack. When data to be validated is
at or below an active NTA (and above any other
- configured trust anchors), <span><strong class="command">named</strong></span> will
+ configured trust anchors), <span class="command"><strong>named</strong></span> will
abort the DNSSEC validation process and treat the data as
insecure rather than bogus. This continues until the
NTA's lifetime is elapsed. NTAs persist
- across <span><strong class="command">named</strong></span> restarts.
+ across <span class="command"><strong>named</strong></span> restarts.
</p>
-<p>
For convenience, TTL-style time unit suffixes can be
used to specify the NTA lifetime in seconds, minutes
or hours. <code class="option">nta-lifetime</code> defaults to
one hour. It cannot exceed one week.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">nta-recheck</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>nta-recheck</strong></span></span></dt>
<dd>
-<p>
Species how often to check whether negative
- trust anchors added via <span><strong class="command">rndc nta</strong></span>
+ trust anchors added via <span class="command"><strong>rndc nta</strong></span>
are still necessary.
</p>
-<p>
A negative trust anchor is normally used when a
domain has stopped validating due to operator error;
it temporarily disables DNSSEC validation for that
domain. In the interest of ensuring that DNSSEC
validation is turned back on as soon as possible,
- <span><strong class="command">named</strong></span> will periodically send a
+ <span class="command"><strong>named</strong></span> will periodically send a
query to the domain, ignoring negative trust anchors,
to find out whether it can now be validated. If so,
the negative trust anchor is allowed to expire early.
</p>
-<p>
Validity checks can be disabled for an individual
- NTA by using <span><strong class="command">rndc nta -f</strong></span>, or
+ NTA by using <span class="command"><strong>rndc nta -f</strong></span>, or
for all NTAs by setting <code class="option">nta-recheck</code>
to zero.
</p>
-<p>
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. It
cannot be longer than <code class="option">nta-lifetime</code>
(which cannot be longer than a week).
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">max-zone-ttl</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-zone-ttl</strong></span></span></dt>
<dd>
-<p>
Specifies a maximum permissible TTL value in seconds.
For convenience, TTL-style time unit suffixes may be
used to specify the maximum value.
<code class="option">max-zone-ttl</code> will cause the zone to
be rejected.
</p>
-<p>
This is useful in DNSSEC-signed zones because when
rolling to a new DNSKEY, the old key needs to remain
available until RRSIG records have expired from
that the largest TTL in the zone will be no higher
than the set value.
</p>
-<p>
(NOTE: Because <code class="constant">map</code>-format files
load directly into memory, this option cannot be
used with them.)
</p>
-<p>
The default value is <code class="constant">unlimited</code>.
A <code class="option">max-zone-ttl</code> of zero is treated as
<code class="constant">unlimited</code>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">serial-update-method</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>serial-update-method</strong></span></span></dt>
<dd>
-<p>
Zones configured for dynamic DNS may use this
option to set the update method that will be used for
the zone serial number in the SOA record.
</p>
-<p>
With the default setting of
- <span><strong class="command">serial-update-method increment;</strong></span>, the
+ <span class="command"><strong>serial-update-method increment;</strong></span>, the
SOA serial number will be incremented by one each time
the zone is updated.
</p>
-<p>
When set to
- <span><strong class="command">serial-update-method unixtime;</strong></span>, the
+ <span class="command"><strong>serial-update-method unixtime;</strong></span>, the
SOA serial number will be set to the number of seconds
since the UNIX epoch, unless the serial number is
already greater than or equal to that value, in which
case it is simply incremented by one.
</p>
-<p>
When set to
- <span><strong class="command">serial-update-method date;</strong></span>, the
+ <span class="command"><strong>serial-update-method date;</strong></span>, the
new SOA serial number will be the current date
in the form "YYYYMMDD", followed by two zeroes,
unless the existing serial number is already greater
than or equal to that value, in which case it is
incremented by one.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>zone-statistics</strong></span></span></dt>
<dd>
-<p>
If <strong class="userinput"><code>full</code></strong>, the server will collect
statistical data on all zones (unless specifically
turned off on a per-zone basis by specifying
- <span><strong class="command">zone-statistics terse</strong></span> or
- <span><strong class="command">zone-statistics none</strong></span>
- in the <span><strong class="command">zone</strong></span> statement).
+ <span class="command"><strong>zone-statistics terse</strong></span> or
+ <span class="command"><strong>zone-statistics none</strong></span>
+ in the <span class="command"><strong>zone</strong></span> statement).
The default is <strong class="userinput"><code>terse</code></strong>, providing
minimal statistics on zones (including name and
current serial number, but not query type
counters).
</p>
-<p>
These statistics may be accessed via the
- <span><strong class="command">statistics-channel</strong></span> or
- using <span><strong class="command">rndc stats</strong></span>, which
+ <span class="command"><strong>statistics-channel</strong></span> or
+ using <span class="command"><strong>rndc stats</strong></span>, which
will dump them to the file listed
- in the <span><strong class="command">statistics-file</strong></span>. See
- also <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>.
+ in the <span class="command"><strong>statistics-file</strong></span>. See
+ also <a class="xref" href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>.
</p>
-<p>
For backward compatibility with earlier versions
- of BIND 9, the <span><strong class="command">zone-statistics</strong></span>
+ of BIND 9, the <span class="command"><strong>zone-statistics</strong></span>
option can also accept <strong class="userinput"><code>yes</code></strong>
or <strong class="userinput"><code>no</code></strong>; <strong class="userinput"><code>yes</code></strong>
has the same meaning as <strong class="userinput"><code>full</code></strong>.
as <strong class="userinput"><code>none</code></strong>; previously, it
was the same as <strong class="userinput"><code>terse</code></strong>.
</p>
-</dd>
+ </dd>
</dl></div>
-<div class="sect3" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="boolean_options"></a>Boolean Options</h4></div></div></div>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">automatic-interface-scan</strong></span></span></dt>
+
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>automatic-interface-scan</strong></span></span></dt>
<dd>
-<p>
If <strong class="userinput"><code>yes</code></strong> and supported by the OS,
automatically rescan network interfaces when the interface
addresses are added or removed. The default is
<strong class="userinput"><code>yes</code></strong>.
</p>
-<p>
Currently the OS needs to support routing sockets for
- <span><strong class="command">automatic-interface-scan</strong></span> to be
+ <span class="command"><strong>automatic-interface-scan</strong></span> to be
supported.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">allow-new-zones</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-new-zones</strong></span></span></dt>
+<dd>
+ <p>
If <strong class="userinput"><code>yes</code></strong>, then zones can be
- added at runtime via <span><strong class="command">rndc addzone</strong></span>.
+ added at runtime via <span class="command"><strong>rndc addzone</strong></span>.
The default is <strong class="userinput"><code>no</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">auth-nxdomain</strong></span></span></dt>
-<dd><p>
- If <strong class="userinput"><code>yes</code></strong>, then the <span><strong class="command">AA</strong></span> bit
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>auth-nxdomain</strong></span></span></dt>
+<dd>
+ <p>
+ If <strong class="userinput"><code>yes</code></strong>, then the <span class="command"><strong>AA</strong></span> bit
is always set on NXDOMAIN responses, even if the server is
not actually
authoritative. The default is <strong class="userinput"><code>no</code></strong>;
a change from <acronym class="acronym">BIND</acronym> 8. If you
are using very old DNS software, you
may need to set it to <strong class="userinput"><code>yes</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">deallocate-on-exit</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>deallocate-on-exit</strong></span></span></dt>
+<dd>
+ <p>
This option was used in <acronym class="acronym">BIND</acronym>
8 to enable checking
for memory leaks on exit. <acronym class="acronym">BIND</acronym> 9 ignores the option and always performs
the checks.
- </p></dd>
-<dt><span class="term"><span><strong class="command">memstatistics</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>memstatistics</strong></span></span></dt>
+<dd>
+ <p>
Write memory statistics to the file specified by
- <span><strong class="command">memstatistics-file</strong></span> at exit.
+ <span class="command"><strong>memstatistics-file</strong></span> at exit.
The default is <strong class="userinput"><code>no</code></strong> unless
'-m record' is specified on the command line in
which case it is <strong class="userinput"><code>yes</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dialup</strong></span></span></dt>
<dd>
-<p>
If <strong class="userinput"><code>yes</code></strong>, then the
server treats all zones as if they are doing zone transfers
across
according
to zone type and concentrates the zone maintenance so that
it all
- happens in a short interval, once every <span><strong class="command">heartbeat-interval</strong></span> and
+ happens in a short interval, once every <span class="command"><strong>heartbeat-interval</strong></span> and
hopefully during the one call. It also suppresses some of
the normal
zone maintenance traffic. The default is <strong class="userinput"><code>no</code></strong>.
</p>
-<p>
- The <span><strong class="command">dialup</strong></span> option
- may also be specified in the <span><strong class="command">view</strong></span> and
- <span><strong class="command">zone</strong></span> statements,
- in which case it overrides the global <span><strong class="command">dialup</strong></span>
+ The <span class="command"><strong>dialup</strong></span> option
+ may also be specified in the <span class="command"><strong>view</strong></span> and
+ <span class="command"><strong>zone</strong></span> statements,
+ in which case it overrides the global <span class="command"><strong>dialup</strong></span>
option.
</p>
-<p>
If the zone is a master zone, then the server will send out a
NOTIFY
request to all the slaves (default). This should trigger the
to verify the zone while the connection is active.
The set of servers to which NOTIFY is sent can be controlled
by
- <span><strong class="command">notify</strong></span> and <span><strong class="command">also-notify</strong></span>.
+ <span class="command"><strong>notify</strong></span> and <span class="command"><strong>also-notify</strong></span>.
</p>
-<p>
If the
zone is a slave or stub zone, then the server will suppress
the regular
"zone up to date" (refresh) queries and only perform them
when the
- <span><strong class="command">heartbeat-interval</strong></span> expires in
+ <span class="command"><strong>heartbeat-interval</strong></span> expires in
addition to sending
NOTIFY requests.
</p>
-<p>
Finer control can be achieved by using
<strong class="userinput"><code>notify</code></strong> which only sends NOTIFY
messages,
suppresses the normal refresh queries, <strong class="userinput"><code>refresh</code></strong>
which suppresses normal refresh processing and sends refresh
queries
- when the <span><strong class="command">heartbeat-interval</strong></span>
+ when the <span class="command"><strong>heartbeat-interval</strong></span>
expires, and
<strong class="userinput"><code>passive</code></strong> which just disables normal
refresh
processing.
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
-<col>
-<col>
+<col width="1.150in" class="1">
+<col width="1.150in" class="2">
+<col width="1.150in" class="3">
+<col width="1.150in" class="4">
</colgroup>
<tbody>
<tr>
</tr>
<tr>
<td>
- <p><span><strong class="command">no</strong></span> (default)</p>
+ <p><span class="command"><strong>no</strong></span> (default)</p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">yes</strong></span></p>
+ <p><span class="command"><strong>yes</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">notify</strong></span></p>
+ <p><span class="command"><strong>notify</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">refresh</strong></span></p>
+ <p><span class="command"><strong>refresh</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">passive</strong></span></p>
+ <p><span class="command"><strong>passive</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">notify-passive</strong></span></p>
+ <p><span class="command"><strong>notify-passive</strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+
+ <p>
Note that normal NOTIFY processing is not affected by
- <span><strong class="command">dialup</strong></span>.
+ <span class="command"><strong>dialup</strong></span>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">fake-iquery</strong></span></span></dt>
-<dd><p>
+
+ </dd>
+<dt><span class="term"><span class="command"><strong>fake-iquery</strong></span></span></dt>
+<dd>
+ <p>
In <acronym class="acronym">BIND</acronym> 8, this option
enabled simulating the obsolete DNS query type
IQUERY. <acronym class="acronym">BIND</acronym> 9 never does
IQUERY simulation.
- </p></dd>
-<dt><span class="term"><span><strong class="command">fetch-glue</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>fetch-glue</strong></span></span></dt>
+<dd>
+ <p>
This option is obsolete.
In BIND 8, <strong class="userinput"><code>fetch-glue yes</code></strong>
caused the server to attempt to fetch glue resource records
data section of a response. This is now considered a bad
idea
and BIND 9 never does it.
- </p></dd>
-<dt><span class="term"><span><strong class="command">flush-zones-on-shutdown</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>flush-zones-on-shutdown</strong></span></span></dt>
+<dd>
+ <p>
When the nameserver exits due receiving SIGTERM,
flush or do not flush any pending zone writes. The default
is
- <span><strong class="command">flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">geoip-use-ecs</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>geoip-use-ecs</strong></span></span></dt>
+<dd>
+ <p>
When BIND is compiled with GeoIP support and configured
with "geoip" ACL elements, this option indicates whether
the EDNS Client Subnet option, if present in a request,
should be used for matching against the GeoIP database.
The default is
- <span><strong class="command">geoip-use-ecs</strong></span> <strong class="userinput"><code>yes</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">has-old-clients</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>geoip-use-ecs</strong></span> <strong class="userinput"><code>yes</code></strong>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>has-old-clients</strong></span></span></dt>
+<dd>
+ <p>
This option was incorrectly implemented
in <acronym class="acronym">BIND</acronym> 8, and is ignored by <acronym class="acronym">BIND</acronym> 9.
To achieve the intended effect
of
- <span><strong class="command">has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify
- the two separate options <span><strong class="command">auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong>
- and <span><strong class="command">rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead.
- </p></dd>
-<dt><span class="term"><span><strong class="command">host-statistics</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify
+ the two separate options <span class="command"><strong>auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong>
+ and <span class="command"><strong>rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>host-statistics</strong></span></span></dt>
+<dd>
+ <p>
In BIND 8, this enables keeping of
statistics for every host that the name server interacts
with.
Not implemented in BIND 9.
- </p></dd>
-<dt><span class="term"><span><strong class="command">maintain-ixfr-base</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>maintain-ixfr-base</strong></span></span></dt>
+<dd>
+ <p>
<span class="emphasis"><em>This option is obsolete</em></span>.
It was used in <acronym class="acronym">BIND</acronym> 8 to
determine whether a transaction log was
kept for Incremental Zone Transfer. <acronym class="acronym">BIND</acronym> 9 maintains a transaction
log whenever possible. If you need to disable outgoing
incremental zone
- transfers, use <span><strong class="command">provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">minimal-responses</strong></span></span></dt>
-<dd><p>
+ transfers, use <span class="command"><strong>provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>minimal-responses</strong></span></span></dt>
+<dd>
+ <p>
If <strong class="userinput"><code>yes</code></strong>, then when generating
responses the server will only add records to the authority
and additional data sections when they are required (e.g.
delegations, negative responses). This may improve the
performance of the server.
The default is <strong class="userinput"><code>no</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">multiple-cnames</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>multiple-cnames</strong></span></span></dt>
+<dd>
+ <p>
This option was used in <acronym class="acronym">BIND</acronym> 8 to allow
a domain name to have multiple CNAME records in violation of
the DNS standards. <acronym class="acronym">BIND</acronym> 9.2 onwards
always strictly enforces the CNAME rules both in master
files and dynamic updates.
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify</strong></span></span></dt>
<dd>
-<p>
If <strong class="userinput"><code>yes</code></strong> (the default),
DNS NOTIFY messages are sent when a zone the server is
authoritative for
- changes, see <a href="Bv9ARM.ch04.html#notify" title="Notify">the section called “Notify”</a>. The messages are
+ changes, see <a class="xref" href="Bv9ARM.ch04.html#notify" title="Notify">the section called “Notify”</a>. The messages are
sent to the
servers listed in the zone's NS records (except the master
server identified
in the SOA MNAME field), and to any servers listed in the
- <span><strong class="command">also-notify</strong></span> option.
+ <span class="command"><strong>also-notify</strong></span> option.
</p>
-<p>
If <strong class="userinput"><code>master-only</code></strong>, notifies are only
sent
for master zones.
If <strong class="userinput"><code>explicit</code></strong>, notifies are sent only
to
- servers explicitly listed using <span><strong class="command">also-notify</strong></span>.
+ servers explicitly listed using <span class="command"><strong>also-notify</strong></span>.
If <strong class="userinput"><code>no</code></strong>, no notifies are sent.
</p>
-<p>
- The <span><strong class="command">notify</strong></span> option may also be
- specified in the <span><strong class="command">zone</strong></span>
+ The <span class="command"><strong>notify</strong></span> option may also be
+ specified in the <span class="command"><strong>zone</strong></span>
statement,
- in which case it overrides the <span><strong class="command">options notify</strong></span> statement.
+ in which case it overrides the <span class="command"><strong>options notify</strong></span> statement.
It would only be necessary to turn off this option if it
caused slaves
to crash.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">notify-to-soa</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-to-soa</strong></span></span></dt>
+<dd>
+ <p>
If <strong class="userinput"><code>yes</code></strong> do not check the nameservers
in the NS RRset against the SOA MNAME. Normally a NOTIFY
message is not sent to the SOA MNAME (SOA ORIGIN) as it is
hidden master configurations and in that case you would
want the ultimate master to still send NOTIFY messages to
all the nameservers listed in the NS RRset.
- </p></dd>
-<dt><span class="term"><span><strong class="command">recursion</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>recursion</strong></span></span></dt>
+<dd>
+ <p>
If <strong class="userinput"><code>yes</code></strong>, and a
DNS query requests recursion, then the server will attempt
to do
return a
referral response. The default is
<strong class="userinput"><code>yes</code></strong>.
- Note that setting <span><strong class="command">recursion no</strong></span> does not prevent
+ Note that setting <span class="command"><strong>recursion no</strong></span> does not prevent
clients from getting data from the server's cache; it only
prevents new data from being cached as an effect of client
queries.
Caching may still occur as an effect the server's internal
operation, such as NOTIFY address lookups.
- See also <span><strong class="command">fetch-glue</strong></span> above.
- </p></dd>
-<dt><span class="term"><span><strong class="command">request-nsid</strong></span></span></dt>
-<dd><p>
+ See also <span class="command"><strong>fetch-glue</strong></span> above.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>request-nsid</strong></span></span></dt>
+<dd>
+ <p>
If <strong class="userinput"><code>yes</code></strong>, then an empty EDNS(0)
NSID (Name Server Identifier) option is sent with all
queries to authoritative name servers during iterative
resolution. If the authoritative server returns an NSID
option in its response, then its contents are logged in
- the <span><strong class="command">resolver</strong></span> category at level
- <span><strong class="command">info</strong></span>.
+ the <span class="command"><strong>resolver</strong></span> category at level
+ <span class="command"><strong>info</strong></span>.
The default is <strong class="userinput"><code>no</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">request-sit</strong></span></span></dt>
-<dd></dd>
-<dt><span class="term"><span><strong class="command">require-server-cookie</strong></span></span></dt>
-<dd></dd>
-<dt><span class="term"><span><strong class="command">send-cookie</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>request-sit</strong></span></span></dt>
+<dd>
+ <p>
+ This experimental option is obsolete.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>require-server-cookie</strong></span></span></dt>
+<dd>
+ <p>
+ Require a valid server cookie before sending a full
+ response to a UDP request from a cookie aware client.
+ BADCOOKIE is sent if there is a bad or no existent
+ server cookie.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>send-cookie</strong></span></span></dt>
+<dd>
+ <p>
If <strong class="userinput"><code>yes</code></strong>, then a COOKIE EDNS
option is sent along with the query. If the
resolver has previously talked to the server, the
response rate limiting (RRL). Resolvers which
do not send a correct COOKIE option may be limited
to receiving smaller responses via the
- <span><strong class="command">nocookie-udp-size</strong></span> option.
- </p></dd>
-<dt><span class="term"><span><strong class="command">nocookie-udp-size</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>nocookie-udp-size</strong></span> option.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>nocookie-udp-size</strong></span></span></dt>
+<dd>
+ <p>
Sets the maximum size of UDP responses that will be
sent to queries without a valid server COOKIE. A value
below 128 will be silently raised to 128. The default
- value is 4096, but the <span><strong class="command">max-udp-size</strong></span>
+ value is 4096, but the <span class="command"><strong>max-udp-size</strong></span>
option may further limit the response size.
- </p></dd>
-<dt><span class="term"><span><strong class="command">sit-secret</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sit-secret</strong></span></span></dt>
+<dd>
+ <p>
This experimental option is obsolete.
- </p></dd>
-<dt><span class="term"><span><strong class="command">cookie-algorithm</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>cookie-algorithm</strong></span></span></dt>
+<dd>
+ <p>
Set the algorithm to be used when generating the
server cookie. One of "aes", "sha1" or "sha256".
The default is "aes" if supported by the cryptographic
library or otherwise "sha256".
- </p></dd>
-<dt><span class="term"><span><strong class="command">cookie-secret</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>cookie-secret</strong></span></span></dt>
+<dd>
+ <p>
If set, this is a shared secret used for generating
and verifying Source Identity Token EDNS options
within an anycast cluster. If not set, the system
shared secret is encoded as a hex string and needs
to be 128 bits for AES128, 160 bits for SHA1 and
256 bits for SHA256.
- </p></dd>
-<dt><span class="term"><span><strong class="command">rfc2308-type1</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>rfc2308-type1</strong></span></span></dt>
<dd>
-<p>
Setting this to <strong class="userinput"><code>yes</code></strong> will
cause the server to send NS records along with the SOA
record for negative
answers. The default is <strong class="userinput"><code>no</code></strong>.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Not yet implemented in <acronym class="acronym">BIND</acronym>
9.
</p>
-</div>
-</dd>
-<dt><span class="term"><span><strong class="command">use-id-pool</strong></span></span></dt>
-<dd><p>
+ </div>
+ </dd>
+<dt><span class="term"><span class="command"><strong>use-id-pool</strong></span></span></dt>
+<dd>
+ <p>
<span class="emphasis"><em>This option is obsolete</em></span>.
<acronym class="acronym">BIND</acronym> 9 always allocates query
IDs from a pool.
- </p></dd>
-<dt><span class="term"><span><strong class="command">use-ixfr</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>use-ixfr</strong></span></span></dt>
+<dd>
+ <p>
<span class="emphasis"><em>This option is obsolete</em></span>.
If you need to disable IXFR to a particular server or
servers, see
- the information on the <span><strong class="command">provide-ixfr</strong></span> option
- in <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
- Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and
+ the information on the <span class="command"><strong>provide-ixfr</strong></span> option
+ in <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called “<span class="command"><strong>server</strong></span> Statement Definition and
Usage”</a>.
See also
- <a href="Bv9ARM.ch04.html#incremental_zone_transfers" title="Incremental Zone Transfers (IXFR)">the section called “Incremental Zone Transfers (IXFR)”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">provide-ixfr</strong></span></span></dt>
-<dd><p>
+ <a class="xref" href="Bv9ARM.ch04.html#incremental_zone_transfers" title="Incremental Zone Transfers (IXFR)">the section called “Incremental Zone Transfers (IXFR)”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>provide-ixfr</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">provide-ixfr</strong></span> in
- <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
- Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and
+ <span class="command"><strong>provide-ixfr</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called “<span class="command"><strong>server</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">request-ixfr</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>request-ixfr</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">request-ixfr</strong></span> in
- <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
- Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and
+ <span class="command"><strong>request-ixfr</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called “<span class="command"><strong>server</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">request-expire</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>request-expire</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">request-expire</strong></span> in
- <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
- Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and
+ <span class="command"><strong>request-expire</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called “<span class="command"><strong>server</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">treat-cr-as-space</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>treat-cr-as-space</strong></span></span></dt>
+<dd>
+ <p>
This option was used in <acronym class="acronym">BIND</acronym>
8 to make
- the server treat carriage return ("<span><strong class="command">\r</strong></span>") characters the same way
+ the server treat carriage return ("<span class="command"><strong>\r</strong></span>") characters the same way
as a space or tab character,
to facilitate loading of zone files on a UNIX system that
were generated
- on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span><strong class="command">\n</strong></span>"
- and NT/DOS "<span><strong class="command">\r\n</strong></span>" newlines
+ on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span class="command"><strong>\n</strong></span>"
+ and NT/DOS "<span class="command"><strong>\r\n</strong></span>" newlines
are always accepted,
and the option is ignored.
- </p></dd>
+ </p>
+ </dd>
<dt>
-<span class="term"><span><strong class="command">additional-from-auth</strong></span>, </span><span class="term"><span><strong class="command">additional-from-cache</strong></span></span>
+<span class="term"><span class="command"><strong>additional-from-auth</strong></span>, </span><span class="term"><span class="command"><strong>additional-from-cache</strong></span></span>
</dt>
<dd>
-<p>
+
+ <p>
These options control the behavior of an authoritative
server when
answering queries which have additional data, or when
following CNAME
and DNAME chains.
</p>
-<p>
+
+ <p>
When both of these options are set to <strong class="userinput"><code>yes</code></strong>
(the default) and a
query is being answered from authoritative data (a zone
what would
otherwise be provided in the additional section.
</p>
-<p>
+
+ <p>
For example, if a query asks for an MX record for host <code class="literal">foo.example.com</code>,
and the record found is "<code class="literal">MX 10 mail.example.net</code>", normally the address
records (A and AAAA) for <code class="literal">mail.example.net</code> will be provided as well,
if known, even though they are not in the example.com zone.
- Setting these options to <span><strong class="command">no</strong></span>
+ Setting these options to <span class="command"><strong>no</strong></span>
disables this behavior and makes
the server only search for additional data in the zone it
answers from.
</p>
-<p>
+
+ <p>
These options are intended for use in authoritative-only
servers, or in authoritative-only views. Attempts to set
- them to <span><strong class="command">no</strong></span> without also
+ them to <span class="command"><strong>no</strong></span> without also
specifying
- <span><strong class="command">recursion no</strong></span> will cause the
+ <span class="command"><strong>recursion no</strong></span> will cause the
server to
ignore the options and log a warning message.
</p>
-<p>
- Specifying <span><strong class="command">additional-from-cache no</strong></span> actually
+
+ <p>
+ Specifying <span class="command"><strong>additional-from-cache no</strong></span> actually
disables the use of the cache not only for additional data
lookups
but also when looking up the answer. This is usually the
correctness of
the cached data is an issue.
</p>
-<p>
+
+ <p>
When a name server is non-recursively queried for a name
that is not
below the apex of any served zone, it normally answers with
upwards referral
comes from the cache, the server will not be able to provide
upwards
- referrals when <span><strong class="command">additional-from-cache no</strong></span>
+ referrals when <span class="command"><strong>additional-from-cache no</strong></span>
has been specified. Instead, it will respond to such
queries
with REFUSED. This should not cause any problems since
upwards referrals are not required for the resolution
process.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">match-mapped-addresses</strong></span></span></dt>
+
+ </dd>
+<dt><span class="term"><span class="command"><strong>match-mapped-addresses</strong></span></span></dt>
<dd>
-<p>
If <strong class="userinput"><code>yes</code></strong>, then an
IPv4-mapped IPv6 address will match any address match
list entries that match the corresponding IPv4 address.
</p>
-<p>
This option was introduced to work around a kernel quirk
in some operating systems that causes IPv4 TCP
connections, such as zone transfers, to be accepted on an
IPv6 socket using mapped addresses. This caused address
match lists designed for IPv4 to fail to match. However,
- <span><strong class="command">named</strong></span> now solves this problem
+ <span class="command"><strong>named</strong></span> now solves this problem
internally. The use of this option is discouraged.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">filter-aaaa-on-v4</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>filter-aaaa-on-v4</strong></span></span></dt>
<dd>
-<p>
This option is only available when
<acronym class="acronym">BIND</acronym> 9 is compiled with the
<strong class="userinput"><code>--enable-filter-aaaa</code></strong> option on the
to DNS clients unless they have connections to the IPv6
Internet. This is not recommended unless absolutely
necessary. The default is <strong class="userinput"><code>no</code></strong>.
- The <span><strong class="command">filter-aaaa-on-v4</strong></span> option
- may also be specified in <span><strong class="command">view</strong></span> statements
- to override the global <span><strong class="command">filter-aaaa-on-v4</strong></span>
+ The <span class="command"><strong>filter-aaaa-on-v4</strong></span> option
+ may also be specified in <span class="command"><strong>view</strong></span> statements
+ to override the global <span class="command"><strong>filter-aaaa-on-v4</strong></span>
option.
</p>
-<p>
If <strong class="userinput"><code>yes</code></strong>,
- the DNS client is at an IPv4 address, in <span><strong class="command">filter-aaaa</strong></span>,
+ the DNS client is at an IPv4 address, in <span class="command"><strong>filter-aaaa</strong></span>,
and if the response does not include DNSSEC signatures,
then all AAAA records are deleted from the response.
This filtering applies to all responses and not only
authoritative responses.
</p>
-<p>
If <strong class="userinput"><code>break-dnssec</code></strong>,
then AAAA records are deleted even when DNSSEC is enabled.
As suggested by the name, this makes the response not verify,
because the DNSSEC protocol is designed detect deletions.
</p>
-<p>
This mechanism can erroneously cause other servers to
not give AAAA records to their clients.
A recursing server with both IPv6 and IPv4 network connections
via IPv4 will be denied AAAA records even if its client is
using IPv6.
</p>
-<p>
This mechanism is applied to authoritative as well as
non-authoritative records.
A client using IPv4 that is not allowed recursion can
erroneously be given AAAA records because the server is not
allowed to check for A records.
</p>
-<p>
Some AAAA records are given to IPv4 clients in glue records.
IPv4 clients that are servers can then erroneously
answer requests for AAAA records received via IPv4.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">filter-aaaa-on-v6</strong></span></span></dt>
-<dd><p>
- Identical to <span><strong class="command">filter-aaaa-on-v4</strong></span>,
+ </dd>
+<dt><span class="term"><span class="command"><strong>filter-aaaa-on-v6</strong></span></span></dt>
+<dd>
+ <p>
+ Identical to <span class="command"><strong>filter-aaaa-on-v4</strong></span>,
except it filters AAAA responses to queries from IPv6
clients instead of IPv4 clients. To filter all
responses, set both options to <strong class="userinput"><code>yes</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>ixfr-from-differences</strong></span></span></dt>
<dd>
-<p>
When <strong class="userinput"><code>yes</code></strong> and the server loads a new
version of a master zone from its zone file or receives a
new version of a slave file via zone transfer, it will
transmitted to downstream slaves as an incremental zone
transfer.
</p>
-<p>
By allowing incremental zone transfers to be used for
non-dynamic zones, this option saves bandwidth at the
expense of increased CPU and memory consumption at the
temporarily allocate memory to hold this complete
difference set.
</p>
-<p><span><strong class="command">ixfr-from-differences</strong></span>
- also accepts <span><strong class="command">master</strong></span> and
- <span><strong class="command">slave</strong></span> at the view and options
+ <p><span class="command"><strong>ixfr-from-differences</strong></span>
+ also accepts <span class="command"><strong>master</strong></span> and
+ <span class="command"><strong>slave</strong></span> at the view and options
levels which causes
- <span><strong class="command">ixfr-from-differences</strong></span> to be enabled for
- all <span><strong class="command">master</strong></span> or
- <span><strong class="command">slave</strong></span> zones respectively.
+ <span class="command"><strong>ixfr-from-differences</strong></span> to be enabled for
+ all <span class="command"><strong>master</strong></span> or
+ <span class="command"><strong>slave</strong></span> zones respectively.
It is off by default.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>multi-master</strong></span></span></dt>
+<dd>
+ <p>
This should be set when you have multiple masters for a zone
and the
- addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, <span><strong class="command">named</strong></span> will
+ addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, <span class="command"><strong>named</strong></span> will
not log
- when the serial number on the master is less than what <span><strong class="command">named</strong></span>
+ when the serial number on the master is less than what <span class="command"><strong>named</strong></span>
currently
has. The default is <strong class="userinput"><code>no</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">auto-dnssec</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>auto-dnssec</strong></span></span></dt>
<dd>
-<p>
Zones configured for dynamic DNS may use this
option to allow varying levels of automatic DNSSEC key
management. There are three possible settings:
</p>
-<p>
- <span><strong class="command">auto-dnssec allow;</strong></span> permits
+ <span class="command"><strong>auto-dnssec allow;</strong></span> permits
keys to be updated and the zone fully re-signed
- whenever the user issues the command <span><strong class="command">rndc sign
+ whenever the user issues the command <span class="command"><strong>rndc sign
<em class="replaceable"><code>zonename</code></em></strong></span>.
</p>
-<p>
- <span><strong class="command">auto-dnssec maintain;</strong></span> includes the
+ <span class="command"><strong>auto-dnssec maintain;</strong></span> includes the
above, but also automatically adjusts the zone's DNSSEC
keys on schedule, according to the keys' timing metadata
- (see <a href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
- <a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The command
- <span><strong class="command">rndc sign
+ (see <a class="xref" href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
+ <a class="xref" href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The command
+ <span class="command"><strong>rndc sign
<em class="replaceable"><code>zonename</code></em></strong></span> causes
- <span><strong class="command">named</strong></span> to load keys from the key
+ <span class="command"><strong>named</strong></span> to load keys from the key
repository and sign the zone with all keys that are
active.
- <span><strong class="command">rndc loadkeys
+ <span class="command"><strong>rndc loadkeys
<em class="replaceable"><code>zonename</code></em></strong></span> causes
- <span><strong class="command">named</strong></span> to load keys from the key
+ <span class="command"><strong>named</strong></span> to load keys from the key
repository and schedule key maintenance events to occur
in the future, but it does not sign the full zone
immediately. Note: once keys have been loaded for a
zone the first time, the repository will be searched
for changes periodically, regardless of whether
- <span><strong class="command">rndc loadkeys</strong></span> is used. The recheck
+ <span class="command"><strong>rndc loadkeys</strong></span> is used. The recheck
interval is defined by
- <span><strong class="command">dnssec-loadkeys-interval</strong></span>.)
+ <span class="command"><strong>dnssec-loadkeys-interval</strong></span>.)
</p>
-<p>
- The default setting is <span><strong class="command">auto-dnssec off</strong></span>.
+ The default setting is <span class="command"><strong>auto-dnssec off</strong></span>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">dnssec-enable</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-enable</strong></span></span></dt>
+<dd>
+ <p>
This indicates whether DNSSEC-related resource
- records are to be returned by <span><strong class="command">named</strong></span>.
+ records are to be returned by <span class="command"><strong>named</strong></span>.
If set to <strong class="userinput"><code>no</code></strong>,
- <span><strong class="command">named</strong></span> will not return DNSSEC-related
+ <span class="command"><strong>named</strong></span> will not return DNSSEC-related
resource records unless specifically queried for.
The default is <strong class="userinput"><code>yes</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnssec-validation</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-validation</strong></span></span></dt>
<dd>
-<p>
- Enable DNSSEC validation in <span><strong class="command">named</strong></span>.
- Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
+ Enable DNSSEC validation in <span class="command"><strong>named</strong></span>.
+ Note <span class="command"><strong>dnssec-enable</strong></span> also needs to be
set to <strong class="userinput"><code>yes</code></strong> to be effective.
If set to <strong class="userinput"><code>no</code></strong>, DNSSEC validation
is disabled. If set to <strong class="userinput"><code>auto</code></strong>,
trust-anchor for the DNS root zone is used. If set to
<strong class="userinput"><code>yes</code></strong>, DNSSEC validation is enabled,
but a trust anchor must be manually configured using
- a <span><strong class="command">trusted-keys</strong></span> or
- <span><strong class="command">managed-keys</strong></span> statement. The default
+ a <span class="command"><strong>trusted-keys</strong></span> or
+ <span class="command"><strong>managed-keys</strong></span> statement. The default
is <strong class="userinput"><code>yes</code></strong>.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Whenever the resolver sends out queries to an
EDNS-compliant server, it always sets the DO bit
indicating it can support DNSSEC responses even if
- <span><strong class="command">dnssec-validation</strong></span> is off.
+ <span class="command"><strong>dnssec-validation</strong></span> is off.
</p>
-</div>
-</dd>
-<dt><span class="term"><span><strong class="command">dnssec-accept-expired</strong></span></span></dt>
-<dd><p>
+ </div>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-accept-expired</strong></span></span></dt>
+<dd>
+ <p>
Accept expired signatures when verifying DNSSEC signatures.
The default is <strong class="userinput"><code>no</code></strong>.
Setting this option to <strong class="userinput"><code>yes</code></strong>
- leaves <span><strong class="command">named</strong></span> vulnerable to
+ leaves <span class="command"><strong>named</strong></span> vulnerable to
replay attacks.
- </p></dd>
-<dt><span class="term"><span><strong class="command">querylog</strong></span></span></dt>
-<dd><p>
- Specify whether query logging should be started when <span><strong class="command">named</strong></span>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>querylog</strong></span></span></dt>
+<dd>
+ <p>
+ Specify whether query logging should be started when <span class="command"><strong>named</strong></span>
starts.
- If <span><strong class="command">querylog</strong></span> is not specified,
+ If <span class="command"><strong>querylog</strong></span> is not specified,
then the query logging
- is determined by the presence of the logging category <span><strong class="command">queries</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt>
+ is determined by the presence of the logging category <span class="command"><strong>queries</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-names</strong></span></span></dt>
<dd>
-<p>
This option is used to restrict the character set and syntax
of
certain domain names in master files and/or DNS responses
received
from the network. The default varies according to usage
area. For
- <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>.
- For <span><strong class="command">slave</strong></span> zones the default
- is <span><strong class="command">warn</strong></span>.
- For answers received from the network (<span><strong class="command">response</strong></span>)
- the default is <span><strong class="command">ignore</strong></span>.
+ <span class="command"><strong>master</strong></span> zones the default is <span class="command"><strong>fail</strong></span>.
+ For <span class="command"><strong>slave</strong></span> zones the default
+ is <span class="command"><strong>warn</strong></span>.
+ For answers received from the network (<span class="command"><strong>response</strong></span>)
+ the default is <span class="command"><strong>ignore</strong></span>.
</p>
-<p>
The rules for legal hostnames and mail domains are derived
from RFC 952 and RFC 821 as modified by RFC 1123.
</p>
-<p><span><strong class="command">check-names</strong></span>
+ <p><span class="command"><strong>check-names</strong></span>
applies to the owner names of A, AAAA and MX records.
It also applies to the domain names in the RDATA of NS, SOA,
MX, and SRV records.
name indicated that it is a reverse lookup of a hostname
(the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT).
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">check-dup-records</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-dup-records</strong></span></span></dt>
+<dd>
+ <p>
Check master zones for records that are treated as different
by DNSSEC but are semantically equal in plain DNS. The
- default is to <span><strong class="command">warn</strong></span>. Other possible
- values are <span><strong class="command">fail</strong></span> and
- <span><strong class="command">ignore</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt>
-<dd><p>
+ default is to <span class="command"><strong>warn</strong></span>. Other possible
+ values are <span class="command"><strong>fail</strong></span> and
+ <span class="command"><strong>ignore</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-mx</strong></span></span></dt>
+<dd>
+ <p>
Check whether the MX record appears to refer to a IP address.
- The default is to <span><strong class="command">warn</strong></span>. Other possible
- values are <span><strong class="command">fail</strong></span> and
- <span><strong class="command">ignore</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt>
-<dd><p>
+ The default is to <span class="command"><strong>warn</strong></span>. Other possible
+ values are <span class="command"><strong>fail</strong></span> and
+ <span class="command"><strong>ignore</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-wildcard</strong></span></span></dt>
+<dd>
+ <p>
This option is used to check for non-terminal wildcards.
The use of non-terminal wildcards is almost always as a
result of a failure
to understand the wildcard matching algorithm (RFC 1034).
This option
- affects master zones. The default (<span><strong class="command">yes</strong></span>) is to check
+ affects master zones. The default (<span class="command"><strong>yes</strong></span>) is to check
for non-terminal wildcards and issue a warning.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-integrity</strong></span></span></dt>
<dd>
-<p>
Perform post load zone integrity checks on master
zones. This checks that MX and SRV records refer
to address (A or AAAA) records and that glue
address records exist for delegated zones. For
MX and SRV records only in-zone hostnames are
checked (for out-of-zone hostnames use
- <span><strong class="command">named-checkzone</strong></span>).
+ <span class="command"><strong>named-checkzone</strong></span>).
For NS records only names below top of zone are
checked (for out-of-zone names and glue consistency
- checks use <span><strong class="command">named-checkzone</strong></span>).
- The default is <span><strong class="command">yes</strong></span>.
+ checks use <span class="command"><strong>named-checkzone</strong></span>).
+ The default is <span class="command"><strong>yes</strong></span>.
</p>
-<p>
The use of the SPF record for publishing Sender
Policy Framework is deprecated as the migration
from using TXT records to SPF records was abandoned.
Policy Framework record exists (starts with "v=spf1")
if there is an SPF record. Warnings are emitted if the
TXT record does not exist and can be suppressed with
- <span><strong class="command">check-spf</strong></span>.
+ <span class="command"><strong>check-spf</strong></span>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">check-mx-cname</strong></span></span></dt>
-<dd><p>
- If <span><strong class="command">check-integrity</strong></span> is set then
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-mx-cname</strong></span></span></dt>
+<dd>
+ <p>
+ If <span class="command"><strong>check-integrity</strong></span> is set then
fail, warn or ignore MX records that refer
- to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-srv-cname</strong></span></span></dt>
-<dd><p>
- If <span><strong class="command">check-integrity</strong></span> is set then
+ to CNAMES. The default is to <span class="command"><strong>warn</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-srv-cname</strong></span></span></dt>
+<dd>
+ <p>
+ If <span class="command"><strong>check-integrity</strong></span> is set then
fail, warn or ignore SRV records that refer
- to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
-<dd><p>
+ to CNAMES. The default is to <span class="command"><strong>warn</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-sibling</strong></span></span></dt>
+<dd>
+ <p>
When performing integrity checks, also check that
- sibling glue exists. The default is <span><strong class="command">yes</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-spf</strong></span></span></dt>
-<dd><p>
- If <span><strong class="command">check-integrity</strong></span> is set then
+ sibling glue exists. The default is <span class="command"><strong>yes</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-spf</strong></span></span></dt>
+<dd>
+ <p>
+ If <span class="command"><strong>check-integrity</strong></span> is set then
check that there is a TXT Sender Policy Framework
record present (starts with "v=spf1") if there is an
SPF record present. The default is
- <span><strong class="command">warn</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>warn</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>zero-no-soa-ttl</strong></span></span></dt>
+<dd>
+ <p>
When returning authoritative negative responses to
SOA queries set the TTL of the SOA record returned in
the authority section to zero.
- The default is <span><strong class="command">yes</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">zero-no-soa-ttl-cache</strong></span></span></dt>
-<dd><p>
+ The default is <span class="command"><strong>yes</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>zero-no-soa-ttl-cache</strong></span></span></dt>
+<dd>
+ <p>
When caching a negative response to a SOA query
set the TTL to zero.
- The default is <span><strong class="command">no</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt>
+ The default is <span class="command"><strong>no</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>update-check-ksk</strong></span></span></dt>
<dd>
-<p>
When set to the default value of <code class="literal">yes</code>,
check the KSK bit in each key to determine how the key
should be used when generating RRSIGs for a secure zone.
</p>
-<p>
Ordinarily, zone-signing keys (that is, keys without the
KSK bit set) are used to sign the entire zone, while
key-signing keys (keys with the KSK bit set) are only
However, if this option is set to <code class="literal">no</code>,
then the KSK bit is ignored; KSKs are treated as if they
were ZSKs and are used to sign the entire zone. This is
- similar to the <span><strong class="command">dnssec-signzone -z</strong></span>
+ similar to the <span class="command"><strong>dnssec-signzone -z</strong></span>
command line option.
</p>
-<p>
When this option is set to <code class="literal">yes</code>, there
must be at least two active keys for every algorithm
represented in the DNSKEY RRset: at least one KSK and one
this requirement is not met, this option will be ignored
for that algorithm.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">dnssec-dnskey-kskonly</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-dnskey-kskonly</strong></span></span></dt>
<dd>
-<p>
- When this option and <span><strong class="command">update-check-ksk</strong></span>
+ When this option and <span class="command"><strong>update-check-ksk</strong></span>
are both set to <code class="literal">yes</code>, only key-signing
keys (that is, keys with the KSK bit set) will be used
to sign the DNSKEY RRset at the zone apex. Zone-signing
keys (keys without the KSK bit set) will be used to sign
the remainder of the zone, but not the DNSKEY RRset.
This is similar to the
- <span><strong class="command">dnssec-signzone -x</strong></span> command line option.
+ <span class="command"><strong>dnssec-signzone -x</strong></span> command line option.
</p>
-<p>
- The default is <span><strong class="command">no</strong></span>. If
- <span><strong class="command">update-check-ksk</strong></span> is set to
+ The default is <span class="command"><strong>no</strong></span>. If
+ <span class="command"><strong>update-check-ksk</strong></span> is set to
<code class="literal">no</code>, this option is ignored.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">try-tcp-refresh</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>try-tcp-refresh</strong></span></span></dt>
+<dd>
+ <p>
Try to refresh the zone using TCP if UDP queries fail.
For BIND 8 compatibility, the default is
- <span><strong class="command">yes</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnssec-secure-to-insecure</strong></span></span></dt>
+ <span class="command"><strong>yes</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-secure-to-insecure</strong></span></span></dt>
<dd>
-<p>
Allow a dynamic zone to transition from secure to
insecure (i.e., signed to unsigned) by deleting all
- of the DNSKEY records. The default is <span><strong class="command">no</strong></span>.
- If set to <span><strong class="command">yes</strong></span>, and if the DNSKEY RRset
+ of the DNSKEY records. The default is <span class="command"><strong>no</strong></span>.
+ If set to <span class="command"><strong>yes</strong></span>, and if the DNSKEY RRset
at the zone apex is deleted, all RRSIG and NSEC records
will be removed from the zone as well.
</p>
-<p>
If the zone uses NSEC3, then it is also necessary to
delete the NSEC3PARAM RRset from the zone apex; this will
cause the removal of all corresponding NSEC3 records.
(It is expected that this requirement will be eliminated
in a future release.)
</p>
-<p>
Note that if a zone has been configured with
- <span><strong class="command">auto-dnssec maintain</strong></span> and the
+ <span class="command"><strong>auto-dnssec maintain</strong></span> and the
private keys remain accessible in the key repository,
then the zone will be automatically signed again the
- next time <span><strong class="command">named</strong></span> is started.
+ next time <span class="command"><strong>named</strong></span> is started.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2584558"></a>Forwarding</h4></div></div></div>
-<p>
+<a name="id-1.7.6.22.6"></a>Forwarding</h4></div></div></div>
+
+ <p>
The forwarding facility can be used to create a large site-wide
cache on a few servers, reducing traffic over links to external
name servers. It can also be used to allow queries by servers that
the server is not authoritative and does not have the answer in
its cache.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">forward</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>forward</strong></span></span></dt>
+<dd>
+ <p>
This option is only meaningful if the
forwarders list is not empty. A value of <code class="varname">first</code>,
the default, causes the server to query the forwarders
the answer itself. If <code class="varname">only</code> is
specified, the
server will only query the forwarders.
- </p></dd>
-<dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>forwarders</strong></span></span></dt>
+<dd>
+ <p>
Specifies the IP addresses to be used
for forwarding. The default is the empty list (no
forwarding).
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-<p>
+
+ <p>
Forwarding can also be configured on a per-domain basis, allowing
for the global forwarding options to be overridden in a variety
of ways. You can set particular domains to use different
forwarders,
- or have a different <span><strong class="command">forward only/first</strong></span> behavior,
- or not forward at all, see <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone
- Statement Grammar">the section called “<span><strong class="command">zone</strong></span>
+ or have a different <span class="command"><strong>forward only/first</strong></span> behavior,
+ or not forward at all, see <a class="xref" href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone Statement Grammar">the section called “<span class="command"><strong>zone</strong></span>
Statement Grammar”</a>.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2584617"></a>Dual-stack Servers</h4></div></div></div>
-<p>
+<a name="id-1.7.6.22.7"></a>Dual-stack Servers</h4></div></div></div>
+
+ <p>
Dual-stack servers are used as servers of last resort to work
around
problems in reachability due the lack of support for either IPv4
or IPv6
on the host machine.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">dual-stack-servers</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>dual-stack-servers</strong></span></span></dt>
+<dd>
+ <p>
Specifies host names or addresses of machines with access to
both IPv4 and IPv6 transports. If a hostname is used, the
server must be able
to resolve the name using only the transport it has. If the
machine is dual
- stacked, then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless
+ stacked, then the <span class="command"><strong>dual-stack-servers</strong></span> have no effect unless
access to a transport has been disabled on the command line
- (e.g. <span><strong class="command">named -4</strong></span>).
- </p></dd>
+ (e.g. <span class="command"><strong>named -4</strong></span>).
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="access_control"></a>Access Control</h4></div></div></div>
-<p>
+
+
+ <p>
Access to the server can be restricted based on the IP address
- of the requesting system. See <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a> for
+ of the requesting system. See <a class="xref" href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a> for
details on how to specify IP address lists.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>allow-notify</strong></span></span></dt>
+<dd>
+ <p>
Specifies which hosts are allowed to
notify this server, a slave, of zone changes in addition
to the zone masters.
- <span><strong class="command">allow-notify</strong></span> may also be
+ <span class="command"><strong>allow-notify</strong></span> may also be
specified in the
- <span><strong class="command">zone</strong></span> statement, in which case
+ <span class="command"><strong>zone</strong></span> statement, in which case
it overrides the
- <span><strong class="command">options allow-notify</strong></span>
+ <span class="command"><strong>options allow-notify</strong></span>
statement. It is only meaningful
for a slave zone. If not specified, the default is to
process notify messages
only from a zone's master.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-query</strong></span></span></dt>
<dd>
-<p>
Specifies which hosts are allowed to ask ordinary
- DNS questions. <span><strong class="command">allow-query</strong></span> may
- also be specified in the <span><strong class="command">zone</strong></span>
+ DNS questions. <span class="command"><strong>allow-query</strong></span> may
+ also be specified in the <span class="command"><strong>zone</strong></span>
statement, in which case it overrides the
- <span><strong class="command">options allow-query</strong></span> statement.
+ <span class="command"><strong>options allow-query</strong></span> statement.
If not specified, the default is to allow queries
from all hosts.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
- <span><strong class="command">allow-query-cache</strong></span> is now
+ <span class="command"><strong>allow-query-cache</strong></span> is now
used to specify access to the cache.
</p>
-</div>
-</dd>
-<dt><span class="term"><span><strong class="command">allow-query-on</strong></span></span></dt>
+ </div>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-query-on</strong></span></span></dt>
<dd>
-<p>
Specifies which local addresses can accept ordinary
DNS questions. This makes it possible, for instance,
to allow queries on internal-facing interfaces but
disallow them on external-facing ones, without
necessarily knowing the internal network's addresses.
</p>
-<p>
- Note that <span><strong class="command">allow-query-on</strong></span> is only
+ Note that <span class="command"><strong>allow-query-on</strong></span> is only
checked for queries that are permitted by
- <span><strong class="command">allow-query</strong></span>. A query must be
+ <span class="command"><strong>allow-query</strong></span>. A query must be
allowed by both ACLs, or it will be refused.
</p>
-<p>
- <span><strong class="command">allow-query-on</strong></span> may
- also be specified in the <span><strong class="command">zone</strong></span>
+ <span class="command"><strong>allow-query-on</strong></span> may
+ also be specified in the <span class="command"><strong>zone</strong></span>
statement, in which case it overrides the
- <span><strong class="command">options allow-query-on</strong></span> statement.
+ <span class="command"><strong>options allow-query-on</strong></span> statement.
</p>
-<p>
If not specified, the default is to allow queries
on all addresses.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
- <span><strong class="command">allow-query-cache</strong></span> is
+ <span class="command"><strong>allow-query-cache</strong></span> is
used to specify access to the cache.
</p>
-</div>
-</dd>
-<dt><span class="term"><span><strong class="command">allow-query-cache</strong></span></span></dt>
-<dd><p>
+ </div>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-query-cache</strong></span></span></dt>
+<dd>
+ <p>
Specifies which hosts are allowed to get answers
- from the cache. If <span><strong class="command">allow-query-cache</strong></span>
- is not set then <span><strong class="command">allow-recursion</strong></span>
- is used if set, otherwise <span><strong class="command">allow-query</strong></span>
- is used if set unless <span><strong class="command">recursion no;</strong></span> is
- set in which case <span><strong class="command">none;</strong></span> is used,
- otherwise the default (<span><strong class="command">localnets;</strong></span>
- <span><strong class="command">localhost;</strong></span>) is used.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-query-cache-on</strong></span></span></dt>
-<dd><p>
+ from the cache. If <span class="command"><strong>allow-query-cache</strong></span>
+ is not set then <span class="command"><strong>allow-recursion</strong></span>
+ is used if set, otherwise <span class="command"><strong>allow-query</strong></span>
+ is used if set unless <span class="command"><strong>recursion no;</strong></span> is
+ set in which case <span class="command"><strong>none;</strong></span> is used,
+ otherwise the default (<span class="command"><strong>localnets;</strong></span>
+ <span class="command"><strong>localhost;</strong></span>) is used.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-query-cache-on</strong></span></span></dt>
+<dd>
+ <p>
Specifies which local addresses can give answers
from the cache. If not specified, the default is
to allow cache queries on any address,
- <span><strong class="command">localnets</strong></span> and
- <span><strong class="command">localhost</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-recursion</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>localnets</strong></span> and
+ <span class="command"><strong>localhost</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-recursion</strong></span></span></dt>
+<dd>
+ <p>
Specifies which hosts are allowed to make recursive
queries through this server. If
- <span><strong class="command">allow-recursion</strong></span> is not set
- then <span><strong class="command">allow-query-cache</strong></span> is
- used if set, otherwise <span><strong class="command">allow-query</strong></span>
+ <span class="command"><strong>allow-recursion</strong></span> is not set
+ then <span class="command"><strong>allow-query-cache</strong></span> is
+ used if set, otherwise <span class="command"><strong>allow-query</strong></span>
is used if set, otherwise the default
- (<span><strong class="command">localnets;</strong></span>
- <span><strong class="command">localhost;</strong></span>) is used.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-recursion-on</strong></span></span></dt>
-<dd><p>
+ (<span class="command"><strong>localnets;</strong></span>
+ <span class="command"><strong>localhost;</strong></span>) is used.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-recursion-on</strong></span></span></dt>
+<dd>
+ <p>
Specifies which local addresses can accept recursive
queries. If not specified, the default is to allow
recursive queries on all addresses.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-update</strong></span></span></dt>
+<dd>
+ <p>
Specifies which hosts are allowed to
submit Dynamic DNS updates for master zones. The default is
to deny
updates from all hosts. Note that allowing updates based
on the requestor's IP address is insecure; see
- <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a> for details.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt>
+ <a class="xref" href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a> for details.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-update-forwarding</strong></span></span></dt>
<dd>
-<p>
Specifies which hosts are allowed to
submit Dynamic DNS updates to slave zones to be forwarded to
the
with the
master server, not the slaves.
</p>
-<p>
Note that enabling the update forwarding feature on a slave
server
may expose master servers relying on insecure IP address
based
- access control to attacks; see <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a>
+ access control to attacks; see <a class="xref" href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a>
for more details.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">allow-v6-synthesis</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-v6-synthesis</strong></span></span></dt>
+<dd>
+ <p>
This option was introduced for the smooth transition from
AAAA
to A6 and from "nibble labels" to binary labels.
deprecated,
this option was also deprecated.
It is now ignored with some warning messages.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-transfer</strong></span></span></dt>
+<dd>
+ <p>
Specifies which hosts are allowed to
- receive zone transfers from the server. <span><strong class="command">allow-transfer</strong></span> may
- also be specified in the <span><strong class="command">zone</strong></span>
+ receive zone transfers from the server. <span class="command"><strong>allow-transfer</strong></span> may
+ also be specified in the <span class="command"><strong>zone</strong></span>
statement, in which
- case it overrides the <span><strong class="command">options allow-transfer</strong></span> statement.
+ case it overrides the <span class="command"><strong>options allow-transfer</strong></span> statement.
If not specified, the default is to allow transfers to all
hosts.
- </p></dd>
-<dt><span class="term"><span><strong class="command">blackhole</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>blackhole</strong></span></span></dt>
+<dd>
+ <p>
Specifies a list of addresses that the
server will not accept queries from or use to resolve a
query. Queries
from these addresses will not be responded to. The default
is <strong class="userinput"><code>none</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">filter-aaaa</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>filter-aaaa</strong></span></span></dt>
+<dd>
+ <p>
Specifies a list of addresses to which
- <span><strong class="command">filter-aaaa-on-v4</strong></span>
+ <span class="command"><strong>filter-aaaa-on-v4</strong></span>
is applies. The default is <strong class="userinput"><code>any</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">keep-response-order</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>keep-response-order</strong></span></span></dt>
+<dd>
+ <p>
Specifies a list of addresses to which the server
will send responses to TCP queries in the same order
in which they were received. This disables the
processing of TCP queries in parallel. The default
is <strong class="userinput"><code>none</code></strong>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">no-case-compress</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>no-case-compress</strong></span></span></dt>
<dd>
-<p>
Specifies a list of addresses which require responses
to use case-insensitive compression. This ACL can be
- used when <span><strong class="command">named</strong></span> needs to work with
+ used when <span class="command"><strong>named</strong></span> needs to work with
clients that do not comply with the requirement in RFC
1034 to use case-insensitive name comparisons when
checking for matching domain names.
</p>
-<p>
If left undefined, the ACL defaults to
- <span><strong class="command">none</strong></span>: case-insensitive compression
+ <span class="command"><strong>none</strong></span>: case-insensitive compression
will be used for all clients. If the ACL is defined and
matches a client, then case will be ignored when
compressing domain names in DNS responses sent to that
client.
</p>
-<p>
This can result in slightly smaller responses: if
a response contains the names "example.com" and
"example.COM", case-insensitive compression would treat
match the query, which is required by some clients
due to incorrect use of case-sensitive comparisons.
</p>
-<p>
Case-insensitive compression is <span class="emphasis"><em>always</em></span>
used in AXFR and IXFR responses, regardless of whether
the client matches this ACL.
</p>
-<p>
- There are circumstances in which <span><strong class="command">named</strong></span>
+ There are circumstances in which <span class="command"><strong>named</strong></span>
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
have their case preserved unless the client matches this
ACL.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">resolver-query-timeout</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>resolver-query-timeout</strong></span></span></dt>
+<dd>
+ <p>
The amount of time in seconds that the resolver
will spend attempting to resolve a recursive
query before failing. The default and minimum
<code class="literal">30</code>. Setting it to
<code class="literal">0</code> will result in the default
being used.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2585378"></a>Interfaces</h4></div></div></div>
-<p>
+<a name="id-1.7.6.22.9"></a>Interfaces</h4></div></div></div>
+
+ <p>
The interfaces and ports that the server will answer queries
- from may be specified using the <span><strong class="command">listen-on</strong></span> option. <span><strong class="command">listen-on</strong></span> takes
+ from may be specified using the <span class="command"><strong>listen-on</strong></span> option. <span class="command"><strong>listen-on</strong></span> takes
an optional port and an <code class="varname">address_match_list</code>
of IPv4 addresses. (IPv6 addresses are ignored, with a
logged warning.)
The server will listen on all interfaces allowed by the address
match list. If a port is not specified, port 53 will be used.
</p>
-<p>
- Multiple <span><strong class="command">listen-on</strong></span> statements are
+ Multiple <span class="command"><strong>listen-on</strong></span> statements are
allowed.
For example,
</p>
+
<pre class="programlisting">listen-on { 5.6.7.8; };
listen-on port 1234 { !1.2.3.4; 1.2/16; };
</pre>
-<p>
+
+ <p>
will enable the name server on port 53 for the IP address
5.6.7.8, and on port 1234 of an address on the machine in net
1.2 that is not 1.2.3.4.
</p>
-<p>
- If no <span><strong class="command">listen-on</strong></span> is specified, the
+
+ <p>
+ If no <span class="command"><strong>listen-on</strong></span> is specified, the
server will listen on port 53 on all IPv4 interfaces.
</p>
-<p>
- The <span><strong class="command">listen-on-v6</strong></span> option is used to
+
+ <p>
+ The <span class="command"><strong>listen-on-v6</strong></span> option is used to
specify the interfaces and the ports on which the server will
listen for incoming queries sent using IPv6. If not specified,
the server will listen on port 53 on all IPv6 interfaces.
</p>
-<p>
+
+ <p>
When </p>
<pre class="programlisting">{ any; }</pre>
<p> is
specified
as the <code class="varname">address_match_list</code> for the
- <span><strong class="command">listen-on-v6</strong></span> option,
+ <span class="command"><strong>listen-on-v6</strong></span> option,
the server does not bind a separate socket to each IPv6 interface
address as it does for IPv4 if the operating system has enough API
support for IPv6 (specifically if it conforms to RFC 3493 and RFC
If the system only has incomplete API support for IPv6, however,
the behavior is the same as that for IPv4.
</p>
-<p>
+
+ <p>
A list of particular IPv6 addresses can also be specified, in
which case
the server listens on a separate socket for each specified
address,
regardless of whether the desired API is supported by the system.
- IPv4 addresses specified in <span><strong class="command">listen-on-v6</strong></span>
+ IPv4 addresses specified in <span class="command"><strong>listen-on-v6</strong></span>
will be ignored, with a logged warning.
</p>
-<p>
- Multiple <span><strong class="command">listen-on-v6</strong></span> options can
+
+ <p>
+ Multiple <span class="command"><strong>listen-on-v6</strong></span> options can
be used.
For example,
</p>
+
<pre class="programlisting">listen-on-v6 { any; };
listen-on-v6 port 1234 { !2001:db8::/32; any; };
</pre>
-<p>
+
+ <p>
will enable the name server on port 53 for any IPv6 addresses
(with a single wildcard socket),
and on port 1234 of IPv6 addresses that is not in the prefix
2001:db8::/32 (with separate sockets for each matched address.)
</p>
-<p>
+
+ <p>
To make the server not listen on any IPv6 address, use
</p>
+
<pre class="programlisting">listen-on-v6 { none; };
</pre>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="query_address"></a>Query Address</h4></div></div></div>
-<p>
+
+ <p>
If the server doesn't know the answer to a question, it will
- query other name servers. <span><strong class="command">query-source</strong></span> specifies
+ query other name servers. <span class="command"><strong>query-source</strong></span> specifies
the address and port used for such queries. For queries sent over
- IPv6, there is a separate <span><strong class="command">query-source-v6</strong></span> option.
- If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> (asterisk) or is omitted,
- a wildcard IP address (<span><strong class="command">INADDR_ANY</strong></span>)
+ IPv6, there is a separate <span class="command"><strong>query-source-v6</strong></span> option.
+ If <span class="command"><strong>address</strong></span> is <span class="command"><strong>*</strong></span> (asterisk) or is omitted,
+ a wildcard IP address (<span class="command"><strong>INADDR_ANY</strong></span>)
will be used.
</p>
-<p>
- If <span><strong class="command">port</strong></span> is <span><strong class="command">*</strong></span> or is omitted,
+
+ <p>
+ If <span class="command"><strong>port</strong></span> is <span class="command"><strong>*</strong></span> or is omitted,
a random port number from a pre-configured
range is picked up and will be used for each query.
The port range(s) is that specified in
- the <span><strong class="command">use-v4-udp-ports</strong></span> (for IPv4)
- and <span><strong class="command">use-v6-udp-ports</strong></span> (for IPv6)
+ the <span class="command"><strong>use-v4-udp-ports</strong></span> (for IPv4)
+ and <span class="command"><strong>use-v6-udp-ports</strong></span> (for IPv6)
options, excluding the ranges specified in
- the <span><strong class="command">avoid-v4-udp-ports</strong></span>
- and <span><strong class="command">avoid-v6-udp-ports</strong></span> options, respectively.
+ the <span class="command"><strong>avoid-v4-udp-ports</strong></span>
+ and <span class="command"><strong>avoid-v6-udp-ports</strong></span> options, respectively.
</p>
-<p>
- The defaults of the <span><strong class="command">query-source</strong></span> and
- <span><strong class="command">query-source-v6</strong></span> options
+
+ <p>
+ The defaults of the <span class="command"><strong>query-source</strong></span> and
+ <span class="command"><strong>query-source-v6</strong></span> options
are:
</p>
+
<pre class="programlisting">query-source address * port *;
query-source-v6 address * port *;
</pre>
-<p>
- If <span><strong class="command">use-v4-udp-ports</strong></span> or
- <span><strong class="command">use-v6-udp-ports</strong></span> is unspecified,
- <span><strong class="command">named</strong></span> will check if the operating
+
+ <p>
+ If <span class="command"><strong>use-v4-udp-ports</strong></span> or
+ <span class="command"><strong>use-v6-udp-ports</strong></span> is unspecified,
+ <span class="command"><strong>named</strong></span> will check if the operating
system provides a programming interface to retrieve the
system's default range for ephemeral ports.
If such an interface is available,
- <span><strong class="command">named</strong></span> will use the corresponding system
+ <span class="command"><strong>named</strong></span> will use the corresponding system
default range; otherwise, it will use its own defaults:
</p>
+
<pre class="programlisting">use-v4-udp-ports { range 1024 65535; };
use-v6-udp-ports { range 1024 65535; };
</pre>
-<p>
+
+ <p>
Note: make sure the ranges be sufficiently large for
security. A desirable size depends on various parameters,
but we generally recommend it contain at least 16384 ports
(14 bits of entropy).
Note also that the system's default range when used may be
too small for this purpose, and that the range may even be
- changed while <span><strong class="command">named</strong></span> is running; the new
- range will automatically be applied when <span><strong class="command">named</strong></span>
+ changed while <span class="command"><strong>named</strong></span> is running; the new
+ range will automatically be applied when <span class="command"><strong>named</strong></span>
is reloaded.
It is encouraged to
- configure <span><strong class="command">use-v4-udp-ports</strong></span> and
- <span><strong class="command">use-v6-udp-ports</strong></span> explicitly so that the
+ configure <span class="command"><strong>use-v4-udp-ports</strong></span> and
+ <span class="command"><strong>use-v6-udp-ports</strong></span> explicitly so that the
ranges are sufficiently large and are reasonably
independent from the ranges used by other applications.
</p>
-<p>
+
+ <p>
Note: the operational configuration
- where <span><strong class="command">named</strong></span> runs may prohibit the use
+ where <span class="command"><strong>named</strong></span> runs may prohibit the use
of some ports. For example, UNIX systems will not allow
- <span><strong class="command">named</strong></span> running without a root privilege
+ <span class="command"><strong>named</strong></span> running without a root privilege
to use ports less than 1024.
If such ports are included in the specified (or detected)
set of query ports, the corresponding query attempts will
It is therefore important to configure the set of ports
that can be safely used in the expected operational environment.
</p>
-<p>
- The defaults of the <span><strong class="command">avoid-v4-udp-ports</strong></span> and
- <span><strong class="command">avoid-v6-udp-ports</strong></span> options
+
+ <p>
+ The defaults of the <span class="command"><strong>avoid-v4-udp-ports</strong></span> and
+ <span class="command"><strong>avoid-v6-udp-ports</strong></span> options
are:
</p>
+
<pre class="programlisting">avoid-v4-udp-ports {};
avoid-v6-udp-ports {};
</pre>
-<p>
+
+ <p>
Note: BIND 9.5.0 introduced
- the <span><strong class="command">use-queryport-pool</strong></span>
+ the <span class="command"><strong>use-queryport-pool</strong></span>
option to support a pool of such random ports, but this
option is now obsolete because reusing the same ports in
the pool may not be sufficiently secure.
For the same reason, it is generally strongly discouraged to
specify a particular port for the
- <span><strong class="command">query-source</strong></span> or
- <span><strong class="command">query-source-v6</strong></span> options;
+ <span class="command"><strong>query-source</strong></span> or
+ <span class="command"><strong>query-source-v6</strong></span> options;
it implicitly disables the use of randomized port numbers.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">use-queryport-pool</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>use-queryport-pool</strong></span></span></dt>
+<dd>
+ <p>
This option is obsolete.
- </p></dd>
-<dt><span class="term"><span><strong class="command">queryport-pool-ports</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>queryport-pool-ports</strong></span></span></dt>
+<dd>
+ <p>
This option is obsolete.
- </p></dd>
-<dt><span class="term"><span><strong class="command">queryport-pool-updateinterval</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>queryport-pool-updateinterval</strong></span></span></dt>
+<dd>
+ <p>
This option is obsolete.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
- The address specified in the <span><strong class="command">query-source</strong></span> option
+ The address specified in the <span class="command"><strong>query-source</strong></span> option
is used for both UDP and TCP queries, but the port applies only
to UDP queries. TCP queries always use a random
unprivileged port.
</p>
-</div>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+ </div>
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Solaris 2.5.1 and earlier does not support setting the source
address for TCP sockets.
</p>
-</div>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+ </div>
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
- See also <span><strong class="command">transfer-source</strong></span> and
- <span><strong class="command">notify-source</strong></span>.
+ See also <span class="command"><strong>transfer-source</strong></span> and
+ <span class="command"><strong>notify-source</strong></span>.
</p>
-</div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="zone_transfers"></a>Zone Transfers</h4></div></div></div>
-<p>
+
+ <p>
<acronym class="acronym">BIND</acronym> has mechanisms in place to
facilitate zone transfers
and set limits on the amount of load that transfers place on the
system. The following options apply to zone transfers.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>also-notify</strong></span></span></dt>
<dd>
-<p>
Defines a global list of IP addresses of name servers
that are also sent NOTIFY messages whenever a fresh copy of
the
This helps to ensure that copies of the zones will
quickly converge on stealth servers.
Optionally, a port may be specified with each
- <span><strong class="command">also-notify</strong></span> address to send
+ <span class="command"><strong>also-notify</strong></span> address to send
the notify messages to a port other than the
default of 53.
An optional TSIG key can also be specified with each
address to cause the notify messages to be signed; this
can be useful when sending notifies to multiple views.
In place of explicit addresses, one or more named
- <span><strong class="command">masters</strong></span> lists can be used.
+ <span class="command"><strong>masters</strong></span> lists can be used.
</p>
-<p>
- If an <span><strong class="command">also-notify</strong></span> list
- is given in a <span><strong class="command">zone</strong></span> statement,
+ If an <span class="command"><strong>also-notify</strong></span> list
+ is given in a <span class="command"><strong>zone</strong></span> statement,
it will override
- the <span><strong class="command">options also-notify</strong></span>
- statement. When a <span><strong class="command">zone notify</strong></span>
+ the <span class="command"><strong>options also-notify</strong></span>
+ statement. When a <span class="command"><strong>zone notify</strong></span>
statement
- is set to <span><strong class="command">no</strong></span>, the IP
- addresses in the global <span><strong class="command">also-notify</strong></span> list will
+ is set to <span class="command"><strong>no</strong></span>, the IP
+ addresses in the global <span class="command"><strong>also-notify</strong></span> list will
not be sent NOTIFY messages for that zone. The default is
the empty
list (no global notification list).
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-time-in</strong></span></span></dt>
+<dd>
+ <p>
Inbound zone transfers running longer than
this many minutes will be terminated. The default is 120
minutes
(2 hours). The maximum value is 28 days (40320 minutes).
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-idle-in</strong></span></span></dt>
+<dd>
+ <p>
Inbound zone transfers making no progress
in this many minutes will be terminated. The default is 60
minutes
(1 hour). The maximum value is 28 days (40320 minutes).
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-time-out</strong></span></span></dt>
+<dd>
+ <p>
Outbound zone transfers running longer than
this many minutes will be terminated. The default is 120
minutes
(2 hours). The maximum value is 28 days (40320 minutes).
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-idle-out</strong></span></span></dt>
+<dd>
+ <p>
Outbound zone transfers making no progress
in this many minutes will be terminated. The default is 60
minutes (1
hour). The maximum value is 28 days (40320 minutes).
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify-rate</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-rate</strong></span></span></dt>
+<dd>
+ <p>
The rate at which NOTIFY requests will be sent
during normal zone maintenance operations. (NOTIFY
requests due to initial zone loading are subject
20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
- </p></dd>
-<dt><span class="term"><span><strong class="command">startup-notify-rate</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>startup-notify-rate</strong></span></span></dt>
+<dd>
+ <p>
The rate at which NOTIFY requests will be sent
when the name server is first starting up, or when
zones have been newly added to the nameserver.
The default is 20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
- </p></dd>
-<dt><span class="term"><span><strong class="command">serial-query-rate</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>serial-query-rate</strong></span></span></dt>
+<dd>
+ <p>
Slave servers will periodically query master
servers to find out if zone serial numbers have
changed. Each such query uses a minute amount of
the slave server's network bandwidth. To limit
the amount of bandwidth used, BIND 9 limits the
rate at which queries are sent. The value of the
- <span><strong class="command">serial-query-rate</strong></span> option, an
+ <span class="command"><strong>serial-query-rate</strong></span> option, an
integer, is the maximum number of queries sent
per second. The default is 20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
- </p></dd>
-<dt><span class="term"><span><strong class="command">serial-queries</strong></span></span></dt>
-<dd><p>
- In BIND 8, the <span><strong class="command">serial-queries</strong></span>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>serial-queries</strong></span></span></dt>
+<dd>
+ <p>
+ In BIND 8, the <span class="command"><strong>serial-queries</strong></span>
option
set the maximum number of concurrent serial number queries
allowed to be outstanding at any given time.
BIND 9 does not limit the number of outstanding
- serial queries and ignores the <span><strong class="command">serial-queries</strong></span> option.
+ serial queries and ignores the <span class="command"><strong>serial-queries</strong></span> option.
Instead, it limits the rate at which the queries are sent
- as defined using the <span><strong class="command">serial-query-rate</strong></span> option.
- </p></dd>
-<dt><span class="term"><span><strong class="command">transfer-format</strong></span></span></dt>
-<dd><p>
+ as defined using the <span class="command"><strong>serial-query-rate</strong></span> option.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfer-format</strong></span></span></dt>
+<dd>
+
+ <p>
Zone transfers can be sent using two different formats,
- <span><strong class="command">one-answer</strong></span> and
- <span><strong class="command">many-answers</strong></span>.
- The <span><strong class="command">transfer-format</strong></span> option is used
+ <span class="command"><strong>one-answer</strong></span> and
+ <span class="command"><strong>many-answers</strong></span>.
+ The <span class="command"><strong>transfer-format</strong></span> option is used
on the master server to determine which format it sends.
- <span><strong class="command">one-answer</strong></span> uses one DNS message per
+ <span class="command"><strong>one-answer</strong></span> uses one DNS message per
resource record transferred.
- <span><strong class="command">many-answers</strong></span> packs as many resource
+ <span class="command"><strong>many-answers</strong></span> packs as many resource
records as possible into a message.
- <span><strong class="command">many-answers</strong></span> is more efficient, but is
+ <span class="command"><strong>many-answers</strong></span> is more efficient, but is
only supported by relatively new slave servers,
such as <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym>
8.x and <acronym class="acronym">BIND</acronym> 4.9.5 onwards.
- The <span><strong class="command">many-answers</strong></span> format is also supported by
+ The <span class="command"><strong>many-answers</strong></span> format is also supported by
recent Microsoft Windows nameservers.
- The default is <span><strong class="command">many-answers</strong></span>.
- <span><strong class="command">transfer-format</strong></span> may be overridden on a
- per-server basis by using the <span><strong class="command">server</strong></span>
+ The default is <span class="command"><strong>many-answers</strong></span>.
+ <span class="command"><strong>transfer-format</strong></span> may be overridden on a
+ per-server basis by using the <span class="command"><strong>server</strong></span>
statement.
- </p></dd>
-<dt><span class="term"><span><strong class="command">transfers-in</strong></span></span></dt>
-<dd><p>
+ </p>
+
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfers-in</strong></span></span></dt>
+<dd>
+ <p>
The maximum number of inbound zone transfers
that can be running concurrently. The default value is <code class="literal">10</code>.
- Increasing <span><strong class="command">transfers-in</strong></span> may
+ Increasing <span class="command"><strong>transfers-in</strong></span> may
speed up the convergence
of slave zones, but it also may increase the load on the
local system.
- </p></dd>
-<dt><span class="term"><span><strong class="command">transfers-out</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfers-out</strong></span></span></dt>
+<dd>
+ <p>
The maximum number of outbound zone transfers
that can be running concurrently. Zone transfer requests in
excess
of the limit will be refused. The default value is <code class="literal">10</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">transfers-per-ns</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfers-per-ns</strong></span></span></dt>
+<dd>
+ <p>
The maximum number of inbound zone transfers
that can be concurrently transferring from a given remote
name server.
The default value is <code class="literal">2</code>.
- Increasing <span><strong class="command">transfers-per-ns</strong></span>
+ Increasing <span class="command"><strong>transfers-per-ns</strong></span>
may
speed up the convergence of slave zones, but it also may
increase
- the load on the remote name server. <span><strong class="command">transfers-per-ns</strong></span> may
- be overridden on a per-server basis by using the <span><strong class="command">transfers</strong></span> phrase
- of the <span><strong class="command">server</strong></span> statement.
- </p></dd>
-<dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt>
+ the load on the remote name server. <span class="command"><strong>transfers-per-ns</strong></span> may
+ be overridden on a per-server basis by using the <span class="command"><strong>transfers</strong></span> phrase
+ of the <span class="command"><strong>server</strong></span> statement.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfer-source</strong></span></span></dt>
<dd>
-<p><span><strong class="command">transfer-source</strong></span>
+ <p><span class="command"><strong>transfer-source</strong></span>
determines which local address will be bound to IPv4
TCP connections used to fetch zones transferred
inbound by the server. It also determines the
controlled value which will usually be the address
of the interface "closest to" the remote end. This
address must appear in the remote end's
- <span><strong class="command">allow-transfer</strong></span> option for the
+ <span class="command"><strong>allow-transfer</strong></span> option for the
zone being transferred, if one is specified. This
statement sets the
- <span><strong class="command">transfer-source</strong></span> for all zones,
+ <span class="command"><strong>transfer-source</strong></span> for all zones,
but can be overridden on a per-view or per-zone
basis by including a
- <span><strong class="command">transfer-source</strong></span> statement within
- the <span><strong class="command">view</strong></span> or
- <span><strong class="command">zone</strong></span> block in the configuration
+ <span class="command"><strong>transfer-source</strong></span> statement within
+ the <span class="command"><strong>view</strong></span> or
+ <span class="command"><strong>zone</strong></span> block in the configuration
file.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Solaris 2.5.1 and earlier does not support setting the
source address for TCP sockets.
</p>
-</div>
-</dd>
-<dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt>
-<dd><p>
- The same as <span><strong class="command">transfer-source</strong></span>,
+ </div>
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfer-source-v6</strong></span></span></dt>
+<dd>
+ <p>
+ The same as <span class="command"><strong>transfer-source</strong></span>,
except zone transfers are performed using IPv6.
- </p></dd>
-<dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>alt-transfer-source</strong></span></span></dt>
<dd>
-<p>
An alternate transfer source if the one listed in
- <span><strong class="command">transfer-source</strong></span> fails and
- <span><strong class="command">use-alt-transfer-source</strong></span> is
+ <span class="command"><strong>transfer-source</strong></span> fails and
+ <span class="command"><strong>use-alt-transfer-source</strong></span> is
set.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
If you do not wish the alternate transfer source
to be used, you should set
- <span><strong class="command">use-alt-transfer-source</strong></span>
+ <span class="command"><strong>use-alt-transfer-source</strong></span>
appropriately and you should not depend upon
getting an answer back to the first refresh
query.
</div>
-</dd>
-<dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>alt-transfer-source-v6</strong></span></span></dt>
+<dd>
+ <p>
An alternate transfer source if the one listed in
- <span><strong class="command">transfer-source-v6</strong></span> fails and
- <span><strong class="command">use-alt-transfer-source</strong></span> is
+ <span class="command"><strong>transfer-source-v6</strong></span> fails and
+ <span class="command"><strong>use-alt-transfer-source</strong></span> is
set.
- </p></dd>
-<dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>use-alt-transfer-source</strong></span></span></dt>
+<dd>
+ <p>
Use the alternate transfer sources or not. If views are
- specified this defaults to <span><strong class="command">no</strong></span>
+ specified this defaults to <span class="command"><strong>no</strong></span>
otherwise it defaults to
- <span><strong class="command">yes</strong></span> (for BIND 8
+ <span class="command"><strong>yes</strong></span> (for BIND 8
compatibility).
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-source</strong></span></span></dt>
<dd>
-<p><span><strong class="command">notify-source</strong></span>
+ <p><span class="command"><strong>notify-source</strong></span>
determines which local source address, and
optionally UDP port, will be used to send NOTIFY
messages. This address must appear in the slave
- server's <span><strong class="command">masters</strong></span> zone clause or
- in an <span><strong class="command">allow-notify</strong></span> clause. This
- statement sets the <span><strong class="command">notify-source</strong></span>
+ server's <span class="command"><strong>masters</strong></span> zone clause or
+ in an <span class="command"><strong>allow-notify</strong></span> clause. This
+ statement sets the <span class="command"><strong>notify-source</strong></span>
for all zones, but can be overridden on a per-zone or
per-view basis by including a
- <span><strong class="command">notify-source</strong></span> statement within
- the <span><strong class="command">zone</strong></span> or
- <span><strong class="command">view</strong></span> block in the configuration
+ <span class="command"><strong>notify-source</strong></span> statement within
+ the <span class="command"><strong>zone</strong></span> or
+ <span class="command"><strong>view</strong></span> block in the configuration
file.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Solaris 2.5.1 and earlier does not support setting the
source address for TCP sockets.
</p>
-</div>
-</dd>
-<dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt>
-<dd><p>
- Like <span><strong class="command">notify-source</strong></span>,
+ </div>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-source-v6</strong></span></span></dt>
+<dd>
+ <p>
+ Like <span class="command"><strong>notify-source</strong></span>,
but applies to notify messages sent to IPv6 addresses.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2586533"></a>UDP Port Lists</h4></div></div></div>
-<p>
- <span><strong class="command">use-v4-udp-ports</strong></span>,
- <span><strong class="command">avoid-v4-udp-ports</strong></span>,
- <span><strong class="command">use-v6-udp-ports</strong></span>, and
- <span><strong class="command">avoid-v6-udp-ports</strong></span>
+<a name="id-1.7.6.22.12"></a>UDP Port Lists</h4></div></div></div>
+
+ <p>
+ <span class="command"><strong>use-v4-udp-ports</strong></span>,
+ <span class="command"><strong>avoid-v4-udp-ports</strong></span>,
+ <span class="command"><strong>use-v6-udp-ports</strong></span>, and
+ <span class="command"><strong>avoid-v6-udp-ports</strong></span>
specify a list of IPv4 and IPv6 UDP ports that will be
used or not used as source ports for UDP messages.
- See <a href="Bv9ARM.ch06.html#query_address" title="Query Address">the section called “Query Address”</a> about how the
+ See <a class="xref" href="Bv9ARM.ch06.html#query_address" title="Query Address">the section called “Query Address”</a> about how the
available ports are determined.
For example, with the following configuration
</p>
+
<pre class="programlisting">
use-v6-udp-ports { range 32768 65535; };
avoid-v6-udp-ports { 40000; range 50000 60000; };
</pre>
-<p>
+
+ <p>
UDP ports of IPv6 messages sent
- from <span><strong class="command">named</strong></span> will be in one
+ from <span class="command"><strong>named</strong></span> will be in one
of the following ranges: 32768 to 39999, 40001 to 49999,
and 60001 to 65535.
</p>
-<p>
- <span><strong class="command">avoid-v4-udp-ports</strong></span> and
- <span><strong class="command">avoid-v6-udp-ports</strong></span> can be used
- to prevent <span><strong class="command">named</strong></span> from choosing as its random source port a
+
+ <p>
+ <span class="command"><strong>avoid-v4-udp-ports</strong></span> and
+ <span class="command"><strong>avoid-v6-udp-ports</strong></span> can be used
+ to prevent <span class="command"><strong>named</strong></span> from choosing as its random source port a
port that is blocked by your firewall or a port that is
used by other applications;
if a query went out with a source port blocked by a
answer would not get by the firewall and the name server would
have to query again.
Note: the desired range can also be represented only with
- <span><strong class="command">use-v4-udp-ports</strong></span> and
- <span><strong class="command">use-v6-udp-ports</strong></span>, and the
- <span><strong class="command">avoid-</strong></span> options are redundant in that
+ <span class="command"><strong>use-v4-udp-ports</strong></span> and
+ <span class="command"><strong>use-v6-udp-ports</strong></span>, and the
+ <span class="command"><strong>avoid-</strong></span> options are redundant in that
sense; they are provided for backward compatibility and
to possibly simplify the port specification.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2586729"></a>Operating System Resource Limits</h4></div></div></div>
-<p>
+<a name="id-1.7.6.22.13"></a>Operating System Resource Limits</h4></div></div></div>
+
+
+ <p>
The server's usage of many system resources can be limited.
Scaled values are allowed when specifying resource limits. For
- example, <span><strong class="command">1G</strong></span> can be used instead of
- <span><strong class="command">1073741824</strong></span> to specify a limit of
+ example, <span class="command"><strong>1G</strong></span> can be used instead of
+ <span class="command"><strong>1073741824</strong></span> to specify a limit of
one
- gigabyte. <span><strong class="command">unlimited</strong></span> requests
+ gigabyte. <span class="command"><strong>unlimited</strong></span> requests
unlimited use, or the
- maximum available amount. <span><strong class="command">default</strong></span>
+ maximum available amount. <span class="command"><strong>default</strong></span>
uses the limit
that was in force when the server was started. See the description
- of <span><strong class="command">size_spec</strong></span> in <a href="Bv9ARM.ch06.html#configuration_file_elements" title="Configuration File Elements">the section called “Configuration File Elements”</a>.
+ of <span class="command"><strong>size_spec</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#configuration_file_elements" title="Configuration File Elements">the section called “Configuration File Elements”</a>.
</p>
-<p>
+
+ <p>
The following options set operating system resource limits for
the name server process. Some operating systems don't support
some or
the
unsupported limit is used.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">coresize</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>coresize</strong></span></span></dt>
+<dd>
+ <p>
The maximum size of a core dump. The default
is <code class="literal">default</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">datasize</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>datasize</strong></span></span></dt>
+<dd>
+ <p>
The maximum amount of data memory the server
may use. The default is <code class="literal">default</code>.
This is a hard limit on server memory usage.
to raise an operating system data size limit that is
too small by default. If you wish to limit the amount
of memory used by the server, use the
- <span><strong class="command">max-cache-size</strong></span> and
- <span><strong class="command">recursive-clients</strong></span>
+ <span class="command"><strong>max-cache-size</strong></span> and
+ <span class="command"><strong>recursive-clients</strong></span>
options instead.
- </p></dd>
-<dt><span class="term"><span><strong class="command">files</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>files</strong></span></span></dt>
+<dd>
+ <p>
The maximum number of files the server
may have open concurrently. The default is <code class="literal">unlimited</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">stacksize</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>stacksize</strong></span></span></dt>
+<dd>
+ <p>
The maximum amount of stack memory the server
may use. The default is <code class="literal">default</code>.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="server_resource_limits"></a>Server Resource Limits</h4></div></div></div>
-<p>
+
+
+ <p>
The following options set limits on the server's
resource consumption that are enforced internally by the
server rather than the operating system.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">max-ixfr-log-size</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>max-ixfr-log-size</strong></span></span></dt>
+<dd>
+ <p>
This option is obsolete; it is accepted
and ignored for BIND 8 compatibility. The option
- <span><strong class="command">max-journal-size</strong></span> performs a
+ <span class="command"><strong>max-journal-size</strong></span> performs a
similar function in BIND 9.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-journal-size</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-journal-size</strong></span></span></dt>
+<dd>
+ <p>
Sets a maximum size for each journal file
- (see <a href="Bv9ARM.ch04.html#journal" title="The journal file">the section called “The journal file”</a>). When the journal file
+ (see <a class="xref" href="Bv9ARM.ch04.html#journal" title="The journal file">the section called “The journal file”</a>). When the journal file
approaches
the specified size, some of the oldest transactions in the
journal
<code class="literal">unlimited</code>, which also
means 2 gigabytes.
This may also be set on a per-zone basis.
- </p></dd>
-<dt><span class="term"><span><strong class="command">host-statistics-max</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>host-statistics-max</strong></span></span></dt>
+<dd>
+ <p>
In BIND 8, specifies the maximum number of host statistics
entries to be kept.
Not implemented in BIND 9.
- </p></dd>
-<dt><span class="term"><span><strong class="command">recursive-clients</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>recursive-clients</strong></span></span></dt>
<dd>
-<p>
The maximum number ("hard quota") of simultaneous
recursive lookups the server will perform on behalf
of clients. The default is
client uses a fair
bit of memory (on the order of 20 kilobytes), the
value of the
- <span><strong class="command">recursive-clients</strong></span> option may
+ <span class="command"><strong>recursive-clients</strong></span> option may
have to be decreased on hosts with limited memory.
</p>
-<p>
<code class="option">recursive-clients</code> defines a "hard
quota" limit for pending recursive clients: when more
clients than this are pending, new incoming requests
will not be accepted, and for each incoming request
a previous pending request will also be dropped.
</p>
-<p>
A "soft quota" is also set. When this lower
quota is exceeded, incoming requests are accepted, but
for each one, a pending request will be dropped.
otherwise it is set to 90% of
<code class="option">recursive-clients</code>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">tcp-clients</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>tcp-clients</strong></span></span></dt>
+<dd>
+ <p>
The maximum number of simultaneous client TCP
connections that the server will accept.
The default is <code class="literal">100</code>.
- </p></dd>
+ </p>
+ </dd>
<dt>
-<a name="clients-per-query"></a><span class="term"><span><strong class="command">clients-per-query</strong></span>, </span><span class="term"><span><strong class="command">max-clients-per-query</strong></span></span>
+<a name="clients-per-query"></a><span class="term"><span class="command"><strong>clients-per-query</strong></span>, </span><span class="term"><span class="command"><strong>max-clients-per-query</strong></span></span>
</dt>
<dd>
-<p>These set the
initial value (minimum) and maximum number of recursive
simultaneous clients for any given query
(<qname,qtype,qclass>) that the server will accept
- before dropping additional clients. <span><strong class="command">named</strong></span> will attempt to
+ before dropping additional clients. <span class="command"><strong>named</strong></span> will attempt to
self tune this value and changes will be logged. The
default values are 10 and 100.
</p>
-<p>
This value should reflect how many queries come in for
a given name in the time it takes to resolve that name.
- If the number of queries exceed this value, <span><strong class="command">named</strong></span> will
+ If the number of queries exceed this value, <span class="command"><strong>named</strong></span> will
assume that it is dealing with a non-responsive zone
and will drop additional queries. If it gets a response
after dropping queries, it will raise the estimate. The
estimate will then be lowered in 20 minutes if it has
remained unchanged.
</p>
-<p>
- If <span><strong class="command">clients-per-query</strong></span> is set to zero,
+ If <span class="command"><strong>clients-per-query</strong></span> is set to zero,
then there is no limit on the number of clients per query
and no queries will be dropped.
</p>
-<p>
- If <span><strong class="command">max-clients-per-query</strong></span> is set to zero,
+ If <span class="command"><strong>max-clients-per-query</strong></span> is set to zero,
then there is no upper bound other than imposed by
- <span><strong class="command">recursive-clients</strong></span>.
+ <span class="command"><strong>recursive-clients</strong></span>.
</p>
-</dd>
+ </dd>
<dt>
-<a name="fetches-per-zone"></a><span class="term"><span><strong class="command">fetches-per-zone</strong></span></span>
+<a name="fetches-per-zone"></a><span class="term"><span class="command"><strong>fetches-per-zone</strong></span></span>
</dt>
<dd>
-<p>
The maximum number of simultaneous iterative
queries to any one domain that the server will
permit before blocking new queries for data
would take to resolve them. It should be smaller
than <code class="option">recursive-clients</code>.
</p>
-<p>
When many clients simultaneously query for the
same name and type, the clients will all be attached
to the same fetch, up to the
<code class="option">max-clients-per-query</code> is not
effective as a limit.
</p>
-<p>
Optionally, this value may be followed by the keyword
<code class="literal">drop</code> or <code class="literal">fail</code>,
indicating whether queries which exceed the fetch
or answered with SERVFAIL. The default is
<code class="literal">drop</code>.
</p>
-<p>
- If <span><strong class="command">fetches-per-zone</strong></span> is set to zero,
+ If <span class="command"><strong>fetches-per-zone</strong></span> is set to zero,
then there is no limit on the number of fetches per query
and no queries will be dropped. The default is zero.
</p>
-<p>
The current list of active fetches can be dumped by
- running <span><strong class="command">rndc recursing</strong></span>. The list
+ running <span class="command"><strong>rndc recursing</strong></span>. The list
includes the number of active fetches for each
domain and the number of queries that have been
passed or dropped as a result of the
next time a fetch is sent to that domain, it is
recreated with the counters set to zero.)
</p>
-</dd>
+ </dd>
<dt>
-<a name="fetches-per-server"></a><span class="term"><span><strong class="command">fetches-per-server</strong></span></span>
+<a name="fetches-per-server"></a><span class="term"><span class="command"><strong>fetches-per-server</strong></span></span>
</dt>
<dd>
-<p>
The maximum number of simultaneous iterative
queries that the server will allow to be sent to
a single upstream name server before blocking
would take to resolve them. It should be smaller
than <code class="option">recursive-clients</code>.
</p>
-<p>
Optionally, this value may be followed by the keyword
<code class="literal">drop</code> or <code class="literal">fail</code>,
indicating whether queries will be dropped with no
exceeded the per-server quota. The default is
<code class="literal">fail</code>.
</p>
-<p>
- If <span><strong class="command">fetches-per-server</strong></span> is set to zero,
+ If <span class="command"><strong>fetches-per-server</strong></span> is set to zero,
then there is no limit on the number of fetches per query
and no queries will be dropped. The default is zero.
</p>
-<p>
- The <span><strong class="command">fetches-per-server</strong></span> quota is
+ The <span class="command"><strong>fetches-per-server</strong></span> quota is
dynamically adjusted in response to detected
congestion. As queries are sent to a server
and are either answered or time out, an
exponentially weighted moving average is calculated
of the ratio of timeouts to responses. If the
current average timeout ratio rises above a "high"
- threshold, then <span><strong class="command">fetches-per-server</strong></span>
+ threshold, then <span class="command"><strong>fetches-per-server</strong></span>
is reduced for that server. If the timeout ratio
drops below a "low" threshold, then
- <span><strong class="command">fetches-per-server</strong></span> is increased.
- The <span><strong class="command">fetch-quota-params</strong></span> options
+ <span class="command"><strong>fetches-per-server</strong></span> is increased.
+ The <span class="command"><strong>fetch-quota-params</strong></span> options
can be used to adjust the parameters for this
calculation.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">fetch-quota-params</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>fetch-quota-params</strong></span></span></dt>
<dd>
-<p>
Sets the parameters to use for dynamic resizing of
the <code class="option">fetches-per-server</code> quota in
response to detected congestion.
</p>
-<p>
The first argument is an integer value indicating
how frequently to recalculate the moving average
of the ratio of timeouts to responses for each
the average ratio after every 100 queries have either
been answered or timed out.
</p>
-<p>
The remaining three arguments represent the "low"
threshold (defaulting to a timeout ratio of 0.1),
the "high" threshold (defaulting to a timeout
precision of 1/100: at most two places after
the decimal point are significant.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">reserved-sockets</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>reserved-sockets</strong></span></span></dt>
<dd>
-<p>
The number of file descriptors reserved for TCP, stdio,
etc. This needs to be big enough to cover the number of
- interfaces <span><strong class="command">named</strong></span> listens on, <span><strong class="command">tcp-clients</strong></span> as well as
+ interfaces <span class="command"><strong>named</strong></span> listens on, <span class="command"><strong>tcp-clients</strong></span> as well as
to provide room for outgoing TCP queries and incoming zone
transfers. The default is <code class="literal">512</code>.
The minimum value is <code class="literal">128</code> and the
maximum value is <code class="literal">128</code> less than
maxsockets (-S). This option may be removed in the future.
</p>
-<p>
This option has little effect on Windows.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">max-cache-size</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-cache-size</strong></span></span></dt>
+<dd>
+ <p>
The maximum amount of memory to use for the
server's cache, in bytes or % of total physical memory.
When the amount of data in the cache
memory is not supported values represented as %
fall back to unlimited.
Note that the detection of physical memory is done only
- once at startup, so <span><strong class="command">named</strong></span> will not
+ once at startup, so <span class="command"><strong>named</strong></span> will not
adjust the cache size if the amount of physical memory
is changed during runtime.
- </p></dd>
-<dt><span class="term"><span><strong class="command">tcp-listen-queue</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>tcp-listen-queue</strong></span></span></dt>
+<dd>
+ <p>
The listen queue depth. The default and minimum is 10.
If the kernel supports the accept filter "dataready" this
also controls how
less than 10 will be silently raised. A value of 0 may also
be used; on most platforms this sets the listen queue
length to a system-defined default value.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2587431"></a>Periodic Task Intervals</h4></div></div></div>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">cleaning-interval</strong></span></span></dt>
-<dd><p>
+<a name="id-1.7.6.22.15"></a>Periodic Task Intervals</h4></div></div></div>
+
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>cleaning-interval</strong></span></span></dt>
+<dd>
+ <p>
This interval is effectively obsolete. Previously,
the server would remove expired resource records
- from the cache every <span><strong class="command">cleaning-interval</strong></span> minutes.
+ from the cache every <span class="command"><strong>cleaning-interval</strong></span> minutes.
<acronym class="acronym">BIND</acronym> 9 now manages cache
memory in a more sophisticated manner and does not
rely on the periodic cleaning any more.
Specifying this option therefore has no effect on
the server's behavior.
- </p></dd>
-<dt><span class="term"><span><strong class="command">heartbeat-interval</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>heartbeat-interval</strong></span></span></dt>
+<dd>
+ <p>
The server will perform zone maintenance tasks
- for all zones marked as <span><strong class="command">dialup</strong></span> whenever this
+ for all zones marked as <span class="command"><strong>dialup</strong></span> whenever this
interval expires. The default is 60 minutes. Reasonable
values are up
to 1 day (1440 minutes). The maximum value is 28 days
(40320 minutes).
If set to 0, no zone maintenance for these zones will occur.
- </p></dd>
-<dt><span class="term"><span><strong class="command">interface-interval</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>interface-interval</strong></span></span></dt>
+<dd>
+ <p>
The server will scan the network interface list
- every <span><strong class="command">interface-interval</strong></span>
+ every <span class="command"><strong>interface-interval</strong></span>
minutes. The default
is 60 minutes. The maximum value is 28 days (40320 minutes).
If set to 0, interface scanning will only occur when
server will
begin listening for queries on any newly discovered
interfaces (provided they are allowed by the
- <span><strong class="command">listen-on</strong></span> configuration), and
+ <span class="command"><strong>listen-on</strong></span> configuration), and
will
stop listening on interfaces that have gone away.
- </p></dd>
-<dt><span class="term"><span><strong class="command">statistics-interval</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>statistics-interval</strong></span></span></dt>
<dd>
-<p>
Name server statistics will be logged
- every <span><strong class="command">statistics-interval</strong></span>
+ every <span class="command"><strong>statistics-interval</strong></span>
minutes. The default is
60. The maximum value is 28 days (40320 minutes).
If set to 0, no statistics will be logged.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Not yet implemented in
<acronym class="acronym">BIND</acronym> 9.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="topology"></a>Topology</h4></div></div></div>
-<p>
+
+
+ <p>
All other things being equal, when the server chooses a name
server
to query from a list of name servers, it prefers the one that is
- topologically closest to itself. The <span><strong class="command">topology</strong></span> statement
- takes an <span><strong class="command">address_match_list</strong></span> and
+ topologically closest to itself. The <span class="command"><strong>topology</strong></span> statement
+ takes an <span class="command"><strong>address_match_list</strong></span> and
interprets it
in a special way. Each top-level list element is assigned a
distance.
any non-negated list element, and closer than any negated element.
For example,
</p>
+
<pre class="programlisting">topology {
10/8;
!1.2.3/24;
{ 1.2/16; 3/8; };
};</pre>
-<p>
+
+ <p>
will prefer servers on network 10 the most, followed by hosts
on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the
exception of hosts on network 1.2.3 (netmask 255.255.255.0), which
is preferred least of all.
</p>
-<p>
The default topology is
</p>
+
<pre class="programlisting"> topology { localhost; localnets; };
</pre>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
- The <span><strong class="command">topology</strong></span> option
+ The <span class="command"><strong>topology</strong></span> option
is not implemented in <acronym class="acronym">BIND</acronym> 9.
</p>
-</div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="the_sortlist_statement"></a>The <span><strong class="command">sortlist</strong></span> Statement</h4></div></div></div>
-<p>
+<a name="the_sortlist_statement"></a>The <span class="command"><strong>sortlist</strong></span> Statement</h4></div></div></div>
+
+
+
+ <p>
The response to a DNS query may consist of multiple resource
records (RRs) forming a resource records set (RRset).
The name server will normally return the
RRs within the RRset in an indeterminate order
- (but see the <span><strong class="command">rrset-order</strong></span>
- statement in <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>).
+ (but see the <span class="command"><strong>rrset-order</strong></span>
+ statement in <a class="xref" href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>).
The client resolver code should rearrange the RRs as appropriate,
that is, using any addresses on the local net in preference to
other addresses.
in the server, based on the client's address. This only requires
configuring the name servers, not all the clients.
</p>
-<p>
- The <span><strong class="command">sortlist</strong></span> statement (see below)
+
+ <p>
+ The <span class="command"><strong>sortlist</strong></span> statement (see below)
takes
- an <span><strong class="command">address_match_list</strong></span> and
+ an <span class="command"><strong>address_match_list</strong></span> and
interprets it even
- more specifically than the <span><strong class="command">topology</strong></span>
+ more specifically than the <span class="command"><strong>topology</strong></span>
statement
- does (<a href="Bv9ARM.ch06.html#topology" title="Topology">the section called “Topology”</a>).
- Each top level statement in the <span><strong class="command">sortlist</strong></span> must
- itself be an explicit <span><strong class="command">address_match_list</strong></span> with
+ does (<a class="xref" href="Bv9ARM.ch06.html#topology" title="Topology">the section called “Topology”</a>).
+ Each top level statement in the <span class="command"><strong>sortlist</strong></span> must
+ itself be an explicit <span class="command"><strong>address_match_list</strong></span> with
one or two elements. The first element (which may be an IP
address,
- an IP prefix, an ACL name or a nested <span><strong class="command">address_match_list</strong></span>)
+ an IP prefix, an ACL name or a nested <span class="command"><strong>address_match_list</strong></span>)
of each top level list is checked against the source address of
the query until a match is found.
</p>
-<p>
Once the source address of the query has been matched, if
the top level statement contains only one element, the actual
primitive
address
in the response to move to the beginning of the response. If the
statement is a list of two elements, then the second element is
- treated the same as the <span><strong class="command">address_match_list</strong></span> in
- a <span><strong class="command">topology</strong></span> statement. Each top
+ treated the same as the <span class="command"><strong>address_match_list</strong></span> in
+ a <span class="command"><strong>topology</strong></span> statement. Each top
level element
is assigned a distance and the address in the response with the
minimum
distance is moved to the beginning of the response.
</p>
-<p>
In the following example, any queries received from any of
the addresses of the host itself will get responses preferring
addresses
or the 192.168.5/24 network will only prefer other addresses on
their directly connected networks.
</p>
+
<pre class="programlisting">sortlist {
// IF the local host
// THEN first fit on the following nets
{ { 192.168.4/24; 192.168.5/24; };
};
};</pre>
-<p>
+
+ <p>
The following example will give reasonable behavior for the
local host and hosts on directly connected networks. It is similar
to the behavior of the address sort in <acronym class="acronym">BIND</acronym> 4.9.x. Responses sent
Responses
to other queries will not be sorted.
</p>
+
<pre class="programlisting">sortlist {
{ localhost; localnets; };
{ localnets; };
};
</pre>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="rrset_ordering"></a>RRset Ordering</h4></div></div></div>
-<p>
+
+ <p>
When multiple records are returned in an answer it may be
useful to configure the order of the records placed into the
response.
- The <span><strong class="command">rrset-order</strong></span> statement permits
+ The <span class="command"><strong>rrset-order</strong></span> statement permits
configuration
of the ordering of the records in a multiple record response.
- See also the <span><strong class="command">sortlist</strong></span> statement,
- <a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span><strong class="command">sortlist</strong></span> Statement”</a>.
+ See also the <span class="command"><strong>sortlist</strong></span> statement,
+ <a class="xref" href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span class="command"><strong>sortlist</strong></span> Statement”</a>.
</p>
-<p>
- An <span><strong class="command">order_spec</strong></span> is defined as
+
+ <p>
+ An <span class="command"><strong>order_spec</strong></span> is defined as
follows:
</p>
-<p>
[<span class="optional">class <em class="replaceable"><code>class_name</code></em></span>]
[<span class="optional">type <em class="replaceable"><code>type_name</code></em></span>]
[<span class="optional">name <em class="replaceable"><code>"domain_name"</code></em></span>]
order <em class="replaceable"><code>ordering</code></em>
</p>
-<p>
- If no class is specified, the default is <span><strong class="command">ANY</strong></span>.
- If no type is specified, the default is <span><strong class="command">ANY</strong></span>.
- If no name is specified, the default is "<span><strong class="command">*</strong></span>" (asterisk).
+ If no class is specified, the default is <span class="command"><strong>ANY</strong></span>.
+ If no type is specified, the default is <span class="command"><strong>ANY</strong></span>.
+ If no name is specified, the default is "<span class="command"><strong>*</strong></span>" (asterisk).
</p>
-<p>
- The legal values for <span><strong class="command">ordering</strong></span> are:
+ The legal values for <span class="command"><strong>ordering</strong></span> are:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="0.750in" class="1">
+<col width="3.750in" class="2">
</colgroup>
<tbody>
<tr>
<td>
- <p><span><strong class="command">fixed</strong></span></p>
+ <p><span class="command"><strong>fixed</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">random</strong></span></p>
+ <p><span class="command"><strong>random</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">cyclic</strong></span></p>
+ <p><span class="command"><strong>cyclic</strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
For example:
</p>
+
<pre class="programlisting">rrset-order {
class IN type A name "host.example.com" order random;
order cyclic;
};
</pre>
-<p>
+
+ <p>
will cause any responses for type A records in class IN that
have "<code class="literal">host.example.com</code>" as a
suffix, to always be returned
in random order. All other records are returned in cyclic order.
</p>
-<p>
- If multiple <span><strong class="command">rrset-order</strong></span> statements
+ If multiple <span class="command"><strong>rrset-order</strong></span> statements
appear, they are not combined — the last one applies.
</p>
-<p>
By default, all records are returned in random order.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
In this release of <acronym class="acronym">BIND</acronym> 9, the
- <span><strong class="command">rrset-order</strong></span> statement does not support
+ <span class="command"><strong>rrset-order</strong></span> statement does not support
"fixed" ordering by default. Fixed ordering can be enabled
at compile time by specifying "--enable-fixed-rrset" on
the "configure" command line.
</p>
-</div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="tuning"></a>Tuning</h4></div></div></div>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">lame-ttl</strong></span></span></dt>
-<dd><p>
+
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>lame-ttl</strong></span></span></dt>
+<dd>
+ <p>
Sets the number of seconds to cache a
lame server indication. 0 disables caching. (This is
<span class="bold"><strong>NOT</strong></span> recommended.)
The default is <code class="literal">600</code> (10 minutes) and the
maximum value is
<code class="literal">1800</code> (30 minutes).
- </p></dd>
-<dt><span class="term"><span><strong class="command">servfail-ttl</strong></span></span></dt>
+ </p>
+
+ </dd>
+<dt><span class="term"><span class="command"><strong>servfail-ttl</strong></span></span></dt>
<dd>
-<p>
Sets the number of seconds to cache a
SERVFAIL response due to DNSSEC validation failure or
other general server failure. If set to
query that failed due to DNSSEC validation to be retried
without waiting for the SERVFAIL TTL to expire.
</p>
-<p>
The maximum value is <code class="literal">300</code>
(5 minutes); any higher value will be silently
reduced. The default is <code class="literal">10</code>
seconds.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">max-ncache-ttl</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-ncache-ttl</strong></span></span></dt>
+<dd>
+ <p>
To reduce network traffic and increase performance,
- the server stores negative answers. <span><strong class="command">max-ncache-ttl</strong></span> is
+ the server stores negative answers. <span class="command"><strong>max-ncache-ttl</strong></span> is
used to set a maximum retention time for these answers in
the server
in seconds. The default
- <span><strong class="command">max-ncache-ttl</strong></span> is <code class="literal">10800</code> seconds (3 hours).
- <span><strong class="command">max-ncache-ttl</strong></span> cannot exceed
+ <span class="command"><strong>max-ncache-ttl</strong></span> is <code class="literal">10800</code> seconds (3 hours).
+ <span class="command"><strong>max-ncache-ttl</strong></span> cannot exceed
7 days and will
be silently truncated to 7 days if set to a greater value.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-cache-ttl</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-cache-ttl</strong></span></span></dt>
+<dd>
+ <p>
Sets the maximum time for which the server will
cache ordinary (positive) answers in seconds.
The default is 604800 (one week).
SERVFAIL, because of lost caches of intermediate
RRsets (such as NS and glue AAAA/A records) in the
resolution process.
- </p></dd>
-<dt><span class="term"><span><strong class="command">min-roots</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>min-roots</strong></span></span></dt>
<dd>
-<p>
The minimum number of root servers that
is required for a request for the root servers to be
accepted. The default
is <strong class="userinput"><code>2</code></strong>.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Not implemented in <acronym class="acronym">BIND</acronym> 9.
</p>
-</div>
-</dd>
-<dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt>
+ </div>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-validity-interval</strong></span></span></dt>
<dd>
-<p>
Specifies the number of days into the future when
DNSSEC signatures automatically generated as a
- result of dynamic updates (<a href="Bv9ARM.ch04.html#dynamic_update" title="Dynamic Update">the section called “Dynamic Update”</a>) will expire. There
+ result of dynamic updates (<a class="xref" href="Bv9ARM.ch04.html#dynamic_update" title="Dynamic Update">the section called “Dynamic Update”</a>) will expire. There
is an optional second field which specifies how
long before expiry that the signatures will be
regenerated. If not specified, the signatures will
giving a re-signing interval of 7 1/2 days. The maximum
values are 10 years (3660 days).
</p>
-<p>
The signature inception time is unconditionally
set to one hour before the current time to allow
for a limited amount of clock skew.
</p>
-<p>
- The <span><strong class="command">sig-validity-interval</strong></span>
+ The <span class="command"><strong>sig-validity-interval</strong></span>
should be, at least, several multiples of the SOA
expire interval to allow for reasonable interaction
between the various timer and expiry dates.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">sig-signing-nodes</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-signing-nodes</strong></span></span></dt>
+<dd>
+ <p>
Specify the maximum number of nodes to be
examined in each quantum when signing a zone with
a new DNSKEY. The default is
<code class="literal">100</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">sig-signing-signatures</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-signing-signatures</strong></span></span></dt>
+<dd>
+ <p>
Specify a threshold number of signatures that
will terminate processing a quantum when signing
a zone with a new DNSKEY. The default is
<code class="literal">10</code>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">sig-signing-type</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-signing-type</strong></span></span></dt>
<dd>
-<p>
Specify a private RDATA type to be used when generating
signing state records. The default is
<code class="literal">65534</code>.
</p>
-<p>
It is expected that this parameter may be removed
in a future version once there is a standard type.
</p>
-<p>
Signing state records are used to internally by
- <span><strong class="command">named</strong></span> to track the current state of
+ <span class="command"><strong>named</strong></span> to track the current state of
a zone-signing process, i.e., whether it is still active
or has been completed. The records can be inspected
using the command
- <span><strong class="command">rndc signing -list <em class="replaceable"><code>zone</code></em></strong></span>.
- Once <span><strong class="command">named</strong></span> has finished signing
+ <span class="command"><strong>rndc signing -list <em class="replaceable"><code>zone</code></em></strong></span>.
+ Once <span class="command"><strong>named</strong></span> has finished signing
a zone with a particular key, the signing state
record associated with that key can be removed from
the zone by running
- <span><strong class="command">rndc signing -clear <em class="replaceable"><code>keyid/algorithm</code></em> <em class="replaceable"><code>zone</code></em></strong></span>.
+ <span class="command"><strong>rndc signing -clear <em class="replaceable"><code>keyid/algorithm</code></em> <em class="replaceable"><code>zone</code></em></strong></span>.
To clear all of the completed signing state
records for a zone, use
- <span><strong class="command">rndc signing -clear all <em class="replaceable"><code>zone</code></em></strong></span>.
+ <span class="command"><strong>rndc signing -clear all <em class="replaceable"><code>zone</code></em></strong></span>.
</p>
-</dd>
+ </dd>
<dt>
-<span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span>
+<span class="term"><span class="command"><strong>min-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>max-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>min-retry-time</strong></span>, </span><span class="term"><span class="command"><strong>max-retry-time</strong></span></span>
</dt>
<dd>
-<p>
These options control the server's behavior on refreshing a
zone
(querying for SOA changes) or retrying failed transfers.
little
control over their contents.
</p>
-<p>
These options allow the administrator to set a minimum and
maximum refresh and retry time in seconds per-zone,
per-view, or globally.
and clamp the SOA refresh and retry times to the specified
values.
</p>
-<p>
The following defaults apply.
- <span><strong class="command">min-refresh-time</strong></span> 300 seconds,
- <span><strong class="command">max-refresh-time</strong></span> 2419200 seconds
- (4 weeks), <span><strong class="command">min-retry-time</strong></span> 500 seconds,
- and <span><strong class="command">max-retry-time</strong></span> 1209600 seconds
+ <span class="command"><strong>min-refresh-time</strong></span> 300 seconds,
+ <span class="command"><strong>max-refresh-time</strong></span> 2419200 seconds
+ (4 weeks), <span class="command"><strong>min-retry-time</strong></span> 500 seconds,
+ and <span class="command"><strong>max-retry-time</strong></span> 1209600 seconds
(2 weeks).
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">edns-udp-size</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>edns-udp-size</strong></span></span></dt>
<dd>
-<p>
Sets the maximum advertised EDNS UDP buffer size in
bytes, to control the size of packets received from
authoritative servers in response to recursive queries.
will be silently adjusted to the nearest value within
it). The default value is 4096.
</p>
-<p>
The usual reason for setting
- <span><strong class="command">edns-udp-size</strong></span> to a non-default value
+ <span class="command"><strong>edns-udp-size</strong></span> to a non-default value
is to get UDP answers to pass through broken firewalls
that block fragmented packets and/or block UDP DNS
packets that are greater than 512 bytes.
</p>
-<p>
- When <span><strong class="command">named</strong></span> first queries a remote
+ When <span class="command"><strong>named</strong></span> first queries a remote
server, it will advertise a UDP buffer size of 512, as
this has the greatest chance of success on the first try.
</p>
-<p>
- If the initial response times out, <span><strong class="command">named</strong></span>
+ If the initial response times out, <span class="command"><strong>named</strong></span>
will try again with plain DNS, and if that is successful,
it will be taken as evidence that the server does not
support EDNS. After enough failures using EDNS and
- successes using plain DNS, <span><strong class="command">named</strong></span>
+ successes using plain DNS, <span class="command"><strong>named</strong></span>
will default to plain DNS for future communications
- with that server. (Periodically, <span><strong class="command">named</strong></span>
+ with that server. (Periodically, <span class="command"><strong>named</strong></span>
will send an EDNS query to see if the situation has
improved.)
</p>
-<p>
However, if the initial query is successful with
EDNS advertising a buffer size of 512, then
- <span><strong class="command">named</strong></span> will advertise progressively
+ <span class="command"><strong>named</strong></span> will advertise progressively
larger buffer sizes on successive queries, until
responses begin timing out or
- <span><strong class="command">edns-udp-size</strong></span> is reached.
+ <span class="command"><strong>edns-udp-size</strong></span> is reached.
</p>
-<p>
- The default buffer sizes used by <span><strong class="command">named</strong></span>
+ The default buffer sizes used by <span class="command"><strong>named</strong></span>
are 512, 1232, 1432, and 4096, but never exceeding
- <span><strong class="command">edns-udp-size</strong></span>. (The values 1232 and
+ <span class="command"><strong>edns-udp-size</strong></span>. (The values 1232 and
1432 are chosen to allow for an IPv4/IPv6 encapsulated
UDP message to be sent without fragmentation at the
minimum MTU sizes for Ethernet and IPv6 networks.)
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">max-udp-size</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-udp-size</strong></span></span></dt>
<dd>
-<p>
Sets the maximum EDNS UDP message size
- <span><strong class="command">named</strong></span> will send in bytes.
+ <span class="command"><strong>named</strong></span> will send in bytes.
Valid values are 512 to 4096 (values outside this
range will be silently adjusted to the nearest
value within it). The default value is 4096.
</p>
-<p>
This value applies to responses sent by a server; to
set the advertised buffer size in queries, see
- <span><strong class="command">edns-udp-size</strong></span>.
+ <span class="command"><strong>edns-udp-size</strong></span>.
</p>
-<p>
The usual reason for setting
- <span><strong class="command">max-udp-size</strong></span> to a non-default
+ <span class="command"><strong>max-udp-size</strong></span> to a non-default
value is to get UDP answers to pass through broken
firewalls that block fragmented packets and/or
block UDP packets that are greater than 512 bytes.
This is independent of the advertised receive
- buffer (<span><strong class="command">edns-udp-size</strong></span>).
+ buffer (<span class="command"><strong>edns-udp-size</strong></span>).
</p>
-<p>
Setting this to a low value will encourage additional
TCP traffic to the nameserver.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>masterfile-format</strong></span></span></dt>
<dd>
-<p>Specifies
the file format of zone files (see
- <a href="Bv9ARM.ch06.html#zonefile_format" title="Additional File Formats">the section called “Additional File Formats”</a>).
+ <a class="xref" href="Bv9ARM.ch06.html#zonefile_format" title="Additional File Formats">the section called “Additional File Formats”</a>).
The default value is <code class="constant">text</code>, which is the
standard textual representation, except for slave zones,
in which the default value is <code class="constant">raw</code>.
Files in other formats than <code class="constant">text</code> are
typically expected to be generated by the
- <span><strong class="command">named-compilezone</strong></span> tool, or dumped by
- <span><strong class="command">named</strong></span>.
+ <span class="command"><strong>named-compilezone</strong></span> tool, or dumped by
+ <span class="command"><strong>named</strong></span>.
</p>
-<p>
Note that when a zone file in a different format than
- <code class="constant">text</code> is loaded, <span><strong class="command">named</strong></span>
+ <code class="constant">text</code> is loaded, <span class="command"><strong>named</strong></span>
may omit some of the checks which would be performed for a
file in the <code class="constant">text</code> format. In particular,
- <span><strong class="command">check-names</strong></span> checks do not apply
+ <span class="command"><strong>check-names</strong></span> checks do not apply
for the <code class="constant">raw</code> format. This means
a zone file in the <code class="constant">raw</code> format
must be generated with the same check level as that
- specified in the <span><strong class="command">named</strong></span> configuration
+ specified in the <span class="command"><strong>named</strong></span> configuration
file. Also, <code class="constant">map</code> format files are
loaded directly into memory via memory mapping, with only
minimal checking.
</p>
-<p>
This statement sets the
- <span><strong class="command">masterfile-format</strong></span> for all zones,
+ <span class="command"><strong>masterfile-format</strong></span> for all zones,
but can be overridden on a per-zone or per-view basis
- by including a <span><strong class="command">masterfile-format</strong></span>
- statement within the <span><strong class="command">zone</strong></span> or
- <span><strong class="command">view</strong></span> block in the configuration
+ by including a <span class="command"><strong>masterfile-format</strong></span>
+ statement within the <span class="command"><strong>zone</strong></span> or
+ <span class="command"><strong>view</strong></span> block in the configuration
file.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">masterfile-style</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>masterfile-style</strong></span></span></dt>
<dd>
-<p>
Specifies the formatting of zone files during dump
when the <code class="option">masterfile-format</code> is
<code class="constant">text</code>. (This option is ignored
with any other <code class="option">masterfile-format</code>.)
</p>
-<p>
When set to <code class="constant">relative</code>,
records are printed in a multi-line format with owner
names expressed relative to a shared origin. When set
zone is to be edited by hand. The default is
<code class="constant">relative</code>.
</p>
-</dd>
+ </dd>
<dt>
-<a name="max-recursion-depth"></a><span class="term"><span><strong class="command">max-recursion-depth</strong></span></span>
+<a name="max-recursion-depth"></a><span class="term"><span class="command"><strong>max-recursion-depth</strong></span></span>
</dt>
-<dd><p>
+<dd>
+ <p>
Sets the maximum number of levels of recursion
that are permitted at any one time while servicing
a recursive query. Resolving a name may require
of indirections exceeds this value, the recursive
query is terminated and returns SERVFAIL. The
default is 7.
- </p></dd>
+ </p>
+ </dd>
<dt>
-<a name="max-recursion-queries"></a><span class="term"><span><strong class="command">max-recursion-queries</strong></span></span>
+<a name="max-recursion-queries"></a><span class="term"><span class="command"><strong>max-recursion-queries</strong></span></span>
</dt>
-<dd><p>
+<dd>
+ <p>
Sets the maximum number of iterative queries that
may be sent while servicing a recursive query.
If more queries are sent, the recursive query
look up top level comains such as "com" and "net"
and the DNS root zone are exempt from this limitation.
The default is 75.
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-delay</strong></span></span></dt>
<dd>
-<p>
The delay, in seconds, between sending sets of notify
messages for a zone. The default is five (5) seconds.
</p>
-<p>
The overall rate that NOTIFY messages are sent for all
- zones is controlled by <span><strong class="command">serial-query-rate</strong></span>.
+ zones is controlled by <span class="command"><strong>serial-query-rate</strong></span>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">max-rsa-exponent-size</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-rsa-exponent-size</strong></span></span></dt>
+<dd>
+ <p>
The maximum RSA exponent size, in bits, that will
be accepted when validating. Valid values are 35
to 4096 bits. The default zero (0) is also accepted
and is equivalent to 4096.
- </p></dd>
-<dt><span class="term"><span><strong class="command">prefetch</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>prefetch</strong></span></span></dt>
<dd>
-<p>
When a query is received for cached data which
- is to expire shortly, <span><strong class="command">named</strong></span> can
+ is to expire shortly, <span class="command"><strong>named</strong></span> can
refresh the data from the authoritative server
immediately, ensuring that the cache always has an
answer available.
</p>
-<p>
The <code class="option">prefetch</code> specifies the
"trigger" TTL value at which prefetch of the current
query will take place: when a cache record with a
prefetch to be disabled.
The default trigger TTL is <code class="literal">2</code>.
</p>
-<p>
An optional second argument specifies the "eligibility"
TTL: the smallest <span class="emphasis"><em>original</em></span>
TTL value that will be accepted for a record to be
eligible for prefetching. The eligibility TTL must
be at least six seconds longer than the trigger TTL;
- if it isn't, <span><strong class="command">named</strong></span> will silently
+ if it isn't, <span class="command"><strong>named</strong></span> will silently
adjust it upward.
The default eligibility TTL is <code class="literal">9</code>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">v6-bias</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>v6-bias</strong></span></span></dt>
+<dd>
+ <p>
When determining the next nameserver to try
preference IPv6 nameservers by this many milliseconds.
The default is <code class="literal">50</code> milliseconds.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="builtin"></a>Built-in server information zones</h4></div></div></div>
-<p>
+
+
+ <p>
The server provides some helpful diagnostic information
through a number of built-in zones under the
pseudo-top-level-domain <code class="literal">bind</code> in the
- <span><strong class="command">CHAOS</strong></span> class. These zones are part
+ <span class="command"><strong>CHAOS</strong></span> class. These zones are part
of a
- built-in view (see <a href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called “<span><strong class="command">view</strong></span> Statement Grammar”</a>) of
+ built-in view (see <a class="xref" href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called “<span class="command"><strong>view</strong></span> Statement Grammar”</a>) of
class
- <span><strong class="command">CHAOS</strong></span> which is separate from the
- default view of class <span><strong class="command">IN</strong></span>. Most global
- configuration options (<span><strong class="command">allow-query</strong></span>,
+ <span class="command"><strong>CHAOS</strong></span> which is separate from the
+ default view of class <span class="command"><strong>IN</strong></span>. Most global
+ configuration options (<span class="command"><strong>allow-query</strong></span>,
etc) will apply to this view, but some are locally
- overridden: <span><strong class="command">notify</strong></span>,
- <span><strong class="command">recursion</strong></span> and
- <span><strong class="command">allow-new-zones</strong></span> are
+ overridden: <span class="command"><strong>notify</strong></span>,
+ <span class="command"><strong>recursion</strong></span> and
+ <span class="command"><strong>allow-new-zones</strong></span> are
always set to <strong class="userinput"><code>no</code></strong>, and
- <span><strong class="command">rate-limit</strong></span> is set to allow
+ <span class="command"><strong>rate-limit</strong></span> is set to allow
three responses per second.
</p>
-<p>
If you need to disable these zones, use the options
- below, or hide the built-in <span><strong class="command">CHAOS</strong></span>
+ below, or hide the built-in <span class="command"><strong>CHAOS</strong></span>
view by
- defining an explicit view of class <span><strong class="command">CHAOS</strong></span>
+ defining an explicit view of class <span class="command"><strong>CHAOS</strong></span>
that matches all clients.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">version</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>version</strong></span></span></dt>
+<dd>
+ <p>
The version the server should report
via a query of the name <code class="literal">version.bind</code>
- with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
+ with type <span class="command"><strong>TXT</strong></span>, class <span class="command"><strong>CHAOS</strong></span>.
The default is the real version number of this server.
- Specifying <span><strong class="command">version none</strong></span>
+ Specifying <span class="command"><strong>version none</strong></span>
disables processing of the queries.
- </p></dd>
-<dt><span class="term"><span><strong class="command">hostname</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>hostname</strong></span></span></dt>
+<dd>
+ <p>
The hostname the server should report via a query of
the name <code class="filename">hostname.bind</code>
- with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
+ with type <span class="command"><strong>TXT</strong></span>, class <span class="command"><strong>CHAOS</strong></span>.
This defaults to the hostname of the machine hosting the
name server as
found by the gethostname() function. The primary purpose of such queries
is to
identify which of a group of anycast servers is actually
- answering your queries. Specifying <span><strong class="command">hostname none;</strong></span>
+ answering your queries. Specifying <span class="command"><strong>hostname none;</strong></span>
disables processing of the queries.
- </p></dd>
-<dt><span class="term"><span><strong class="command">server-id</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>server-id</strong></span></span></dt>
+<dd>
+ <p>
The ID the server should report when receiving a Name
Server Identifier (NSID) query, or a query of the name
<code class="filename">ID.SERVER</code> with type
- <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
+ <span class="command"><strong>TXT</strong></span>, class <span class="command"><strong>CHAOS</strong></span>.
The primary purpose of such queries is to
identify which of a group of anycast servers is actually
- answering your queries. Specifying <span><strong class="command">server-id none;</strong></span>
+ answering your queries. Specifying <span class="command"><strong>server-id none;</strong></span>
disables processing of the queries.
- Specifying <span><strong class="command">server-id hostname;</strong></span> will cause <span><strong class="command">named</strong></span> to
+ Specifying <span class="command"><strong>server-id hostname;</strong></span> will cause <span class="command"><strong>named</strong></span> to
use the hostname as found by the gethostname() function.
- The default <span><strong class="command">server-id</strong></span> is <span><strong class="command">none</strong></span>.
- </p></dd>
+ The default <span class="command"><strong>server-id</strong></span> is <span class="command"><strong>none</strong></span>.
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="empty"></a>Built-in Empty Zones</h4></div></div></div>
-<p>
- The <span><strong class="command">named</strong></span> server has some built-in
+
+ <p>
+ The <span class="command"><strong>named</strong></span> server has some built-in
empty zones (SOA and NS records only).
These are for zones that should normally be answered locally
and which queries should not be sent to the Internet's root
IPv6 link local addresses, the IPv6 loopback address and the
IPv6 unknown address.
</p>
-<p>
The server will attempt to determine if a built-in zone
already exists or is active (covered by a forward-only
forwarding declaration) and will not create an empty
zone in that case.
</p>
-<p>
The current list of empty zones is:
</p>
-<div class="itemizedlist"><ul type="disc">
-<li>10.IN-ADDR.ARPA</li>
-<li>16.172.IN-ADDR.ARPA</li>
-<li>17.172.IN-ADDR.ARPA</li>
-<li>18.172.IN-ADDR.ARPA</li>
-<li>19.172.IN-ADDR.ARPA</li>
-<li>20.172.IN-ADDR.ARPA</li>
-<li>21.172.IN-ADDR.ARPA</li>
-<li>22.172.IN-ADDR.ARPA</li>
-<li>23.172.IN-ADDR.ARPA</li>
-<li>24.172.IN-ADDR.ARPA</li>
-<li>25.172.IN-ADDR.ARPA</li>
-<li>26.172.IN-ADDR.ARPA</li>
-<li>27.172.IN-ADDR.ARPA</li>
-<li>28.172.IN-ADDR.ARPA</li>
-<li>29.172.IN-ADDR.ARPA</li>
-<li>30.172.IN-ADDR.ARPA</li>
-<li>31.172.IN-ADDR.ARPA</li>
-<li>168.192.IN-ADDR.ARPA</li>
-<li>64.100.IN-ADDR.ARPA</li>
-<li>65.100.IN-ADDR.ARPA</li>
-<li>66.100.IN-ADDR.ARPA</li>
-<li>67.100.IN-ADDR.ARPA</li>
-<li>68.100.IN-ADDR.ARPA</li>
-<li>69.100.IN-ADDR.ARPA</li>
-<li>70.100.IN-ADDR.ARPA</li>
-<li>71.100.IN-ADDR.ARPA</li>
-<li>72.100.IN-ADDR.ARPA</li>
-<li>73.100.IN-ADDR.ARPA</li>
-<li>74.100.IN-ADDR.ARPA</li>
-<li>75.100.IN-ADDR.ARPA</li>
-<li>76.100.IN-ADDR.ARPA</li>
-<li>77.100.IN-ADDR.ARPA</li>
-<li>78.100.IN-ADDR.ARPA</li>
-<li>79.100.IN-ADDR.ARPA</li>
-<li>80.100.IN-ADDR.ARPA</li>
-<li>81.100.IN-ADDR.ARPA</li>
-<li>82.100.IN-ADDR.ARPA</li>
-<li>83.100.IN-ADDR.ARPA</li>
-<li>84.100.IN-ADDR.ARPA</li>
-<li>85.100.IN-ADDR.ARPA</li>
-<li>86.100.IN-ADDR.ARPA</li>
-<li>87.100.IN-ADDR.ARPA</li>
-<li>88.100.IN-ADDR.ARPA</li>
-<li>89.100.IN-ADDR.ARPA</li>
-<li>90.100.IN-ADDR.ARPA</li>
-<li>91.100.IN-ADDR.ARPA</li>
-<li>92.100.IN-ADDR.ARPA</li>
-<li>93.100.IN-ADDR.ARPA</li>
-<li>94.100.IN-ADDR.ARPA</li>
-<li>95.100.IN-ADDR.ARPA</li>
-<li>96.100.IN-ADDR.ARPA</li>
-<li>97.100.IN-ADDR.ARPA</li>
-<li>98.100.IN-ADDR.ARPA</li>
-<li>99.100.IN-ADDR.ARPA</li>
-<li>100.100.IN-ADDR.ARPA</li>
-<li>101.100.IN-ADDR.ARPA</li>
-<li>102.100.IN-ADDR.ARPA</li>
-<li>103.100.IN-ADDR.ARPA</li>
-<li>104.100.IN-ADDR.ARPA</li>
-<li>105.100.IN-ADDR.ARPA</li>
-<li>106.100.IN-ADDR.ARPA</li>
-<li>107.100.IN-ADDR.ARPA</li>
-<li>108.100.IN-ADDR.ARPA</li>
-<li>109.100.IN-ADDR.ARPA</li>
-<li>110.100.IN-ADDR.ARPA</li>
-<li>111.100.IN-ADDR.ARPA</li>
-<li>112.100.IN-ADDR.ARPA</li>
-<li>113.100.IN-ADDR.ARPA</li>
-<li>114.100.IN-ADDR.ARPA</li>
-<li>115.100.IN-ADDR.ARPA</li>
-<li>116.100.IN-ADDR.ARPA</li>
-<li>117.100.IN-ADDR.ARPA</li>
-<li>118.100.IN-ADDR.ARPA</li>
-<li>119.100.IN-ADDR.ARPA</li>
-<li>120.100.IN-ADDR.ARPA</li>
-<li>121.100.IN-ADDR.ARPA</li>
-<li>122.100.IN-ADDR.ARPA</li>
-<li>123.100.IN-ADDR.ARPA</li>
-<li>124.100.IN-ADDR.ARPA</li>
-<li>125.100.IN-ADDR.ARPA</li>
-<li>126.100.IN-ADDR.ARPA</li>
-<li>127.100.IN-ADDR.ARPA</li>
-<li>0.IN-ADDR.ARPA</li>
-<li>127.IN-ADDR.ARPA</li>
-<li>254.169.IN-ADDR.ARPA</li>
-<li>2.0.192.IN-ADDR.ARPA</li>
-<li>100.51.198.IN-ADDR.ARPA</li>
-<li>113.0.203.IN-ADDR.ARPA</li>
-<li>255.255.255.255.IN-ADDR.ARPA</li>
-<li>0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
-<li>1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
-<li>8.B.D.0.1.0.0.2.IP6.ARPA</li>
-<li>D.F.IP6.ARPA</li>
-<li>8.E.F.IP6.ARPA</li>
-<li>9.E.F.IP6.ARPA</li>
-<li>A.E.F.IP6.ARPA</li>
-<li>B.E.F.IP6.ARPA</li>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">10.IN-ADDR.ARPA</li>
+<li class="listitem">16.172.IN-ADDR.ARPA</li>
+<li class="listitem">17.172.IN-ADDR.ARPA</li>
+<li class="listitem">18.172.IN-ADDR.ARPA</li>
+<li class="listitem">19.172.IN-ADDR.ARPA</li>
+<li class="listitem">20.172.IN-ADDR.ARPA</li>
+<li class="listitem">21.172.IN-ADDR.ARPA</li>
+<li class="listitem">22.172.IN-ADDR.ARPA</li>
+<li class="listitem">23.172.IN-ADDR.ARPA</li>
+<li class="listitem">24.172.IN-ADDR.ARPA</li>
+<li class="listitem">25.172.IN-ADDR.ARPA</li>
+<li class="listitem">26.172.IN-ADDR.ARPA</li>
+<li class="listitem">27.172.IN-ADDR.ARPA</li>
+<li class="listitem">28.172.IN-ADDR.ARPA</li>
+<li class="listitem">29.172.IN-ADDR.ARPA</li>
+<li class="listitem">30.172.IN-ADDR.ARPA</li>
+<li class="listitem">31.172.IN-ADDR.ARPA</li>
+<li class="listitem">168.192.IN-ADDR.ARPA</li>
+<li class="listitem">64.100.IN-ADDR.ARPA</li>
+<li class="listitem">65.100.IN-ADDR.ARPA</li>
+<li class="listitem">66.100.IN-ADDR.ARPA</li>
+<li class="listitem">67.100.IN-ADDR.ARPA</li>
+<li class="listitem">68.100.IN-ADDR.ARPA</li>
+<li class="listitem">69.100.IN-ADDR.ARPA</li>
+<li class="listitem">70.100.IN-ADDR.ARPA</li>
+<li class="listitem">71.100.IN-ADDR.ARPA</li>
+<li class="listitem">72.100.IN-ADDR.ARPA</li>
+<li class="listitem">73.100.IN-ADDR.ARPA</li>
+<li class="listitem">74.100.IN-ADDR.ARPA</li>
+<li class="listitem">75.100.IN-ADDR.ARPA</li>
+<li class="listitem">76.100.IN-ADDR.ARPA</li>
+<li class="listitem">77.100.IN-ADDR.ARPA</li>
+<li class="listitem">78.100.IN-ADDR.ARPA</li>
+<li class="listitem">79.100.IN-ADDR.ARPA</li>
+<li class="listitem">80.100.IN-ADDR.ARPA</li>
+<li class="listitem">81.100.IN-ADDR.ARPA</li>
+<li class="listitem">82.100.IN-ADDR.ARPA</li>
+<li class="listitem">83.100.IN-ADDR.ARPA</li>
+<li class="listitem">84.100.IN-ADDR.ARPA</li>
+<li class="listitem">85.100.IN-ADDR.ARPA</li>
+<li class="listitem">86.100.IN-ADDR.ARPA</li>
+<li class="listitem">87.100.IN-ADDR.ARPA</li>
+<li class="listitem">88.100.IN-ADDR.ARPA</li>
+<li class="listitem">89.100.IN-ADDR.ARPA</li>
+<li class="listitem">90.100.IN-ADDR.ARPA</li>
+<li class="listitem">91.100.IN-ADDR.ARPA</li>
+<li class="listitem">92.100.IN-ADDR.ARPA</li>
+<li class="listitem">93.100.IN-ADDR.ARPA</li>
+<li class="listitem">94.100.IN-ADDR.ARPA</li>
+<li class="listitem">95.100.IN-ADDR.ARPA</li>
+<li class="listitem">96.100.IN-ADDR.ARPA</li>
+<li class="listitem">97.100.IN-ADDR.ARPA</li>
+<li class="listitem">98.100.IN-ADDR.ARPA</li>
+<li class="listitem">99.100.IN-ADDR.ARPA</li>
+<li class="listitem">100.100.IN-ADDR.ARPA</li>
+<li class="listitem">101.100.IN-ADDR.ARPA</li>
+<li class="listitem">102.100.IN-ADDR.ARPA</li>
+<li class="listitem">103.100.IN-ADDR.ARPA</li>
+<li class="listitem">104.100.IN-ADDR.ARPA</li>
+<li class="listitem">105.100.IN-ADDR.ARPA</li>
+<li class="listitem">106.100.IN-ADDR.ARPA</li>
+<li class="listitem">107.100.IN-ADDR.ARPA</li>
+<li class="listitem">108.100.IN-ADDR.ARPA</li>
+<li class="listitem">109.100.IN-ADDR.ARPA</li>
+<li class="listitem">110.100.IN-ADDR.ARPA</li>
+<li class="listitem">111.100.IN-ADDR.ARPA</li>
+<li class="listitem">112.100.IN-ADDR.ARPA</li>
+<li class="listitem">113.100.IN-ADDR.ARPA</li>
+<li class="listitem">114.100.IN-ADDR.ARPA</li>
+<li class="listitem">115.100.IN-ADDR.ARPA</li>
+<li class="listitem">116.100.IN-ADDR.ARPA</li>
+<li class="listitem">117.100.IN-ADDR.ARPA</li>
+<li class="listitem">118.100.IN-ADDR.ARPA</li>
+<li class="listitem">119.100.IN-ADDR.ARPA</li>
+<li class="listitem">120.100.IN-ADDR.ARPA</li>
+<li class="listitem">121.100.IN-ADDR.ARPA</li>
+<li class="listitem">122.100.IN-ADDR.ARPA</li>
+<li class="listitem">123.100.IN-ADDR.ARPA</li>
+<li class="listitem">124.100.IN-ADDR.ARPA</li>
+<li class="listitem">125.100.IN-ADDR.ARPA</li>
+<li class="listitem">126.100.IN-ADDR.ARPA</li>
+<li class="listitem">127.100.IN-ADDR.ARPA</li>
+<li class="listitem">0.IN-ADDR.ARPA</li>
+<li class="listitem">127.IN-ADDR.ARPA</li>
+<li class="listitem">254.169.IN-ADDR.ARPA</li>
+<li class="listitem">2.0.192.IN-ADDR.ARPA</li>
+<li class="listitem">100.51.198.IN-ADDR.ARPA</li>
+<li class="listitem">113.0.203.IN-ADDR.ARPA</li>
+<li class="listitem">255.255.255.255.IN-ADDR.ARPA</li>
+<li class="listitem">0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
+<li class="listitem">1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
+<li class="listitem">8.B.D.0.1.0.0.2.IP6.ARPA</li>
+<li class="listitem">D.F.IP6.ARPA</li>
+<li class="listitem">8.E.F.IP6.ARPA</li>
+<li class="listitem">9.E.F.IP6.ARPA</li>
+<li class="listitem">A.E.F.IP6.ARPA</li>
+<li class="listitem">B.E.F.IP6.ARPA</li>
</ul></div>
<p>
</p>
-<p>
Empty zones are settable at the view level and only apply to
views of class IN. Disabled empty zones are only inherited
from options if there are no disabled empty zones specified
</pre>
<p>
</p>
-<p>
If you are using the address ranges covered here, you should
already have reverse zones covering the addresses you use.
In practice this appears to not be the case with many queries
to be deployed to channel the query load away from the
infrastructure servers.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
The real parent servers for these zones should disable all
empty zone under the parent zone they serve. For the real
root servers, this is all built-in empty zones. This will
enable them to return referrals to deeper in the tree.
</div>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">empty-server</strong></span></span></dt>
-<dd><p>
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>empty-server</strong></span></span></dt>
+<dd>
+ <p>
Specify what server name will appear in the returned
SOA record for empty zones. If none is specified, then
the zone's name will be used.
- </p></dd>
-<dt><span class="term"><span><strong class="command">empty-contact</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>empty-contact</strong></span></span></dt>
+<dd>
+ <p>
Specify what contact name will appear in the returned
SOA record for empty zones. If none is specified, then
"." will be used.
- </p></dd>
-<dt><span class="term"><span><strong class="command">empty-zones-enable</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>empty-zones-enable</strong></span></span></dt>
+<dd>
+ <p>
Enable or disable all empty zones. By default, they
are enabled.
- </p></dd>
-<dt><span class="term"><span><strong class="command">disable-empty-zone</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>disable-empty-zone</strong></span></span></dt>
+<dd>
+ <p>
Disable individual empty zones. By default, none are
disabled. This option can be specified multiple times.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="acache"></a>Additional Section Caching</h4></div></div></div>
-<p>
- The additional section cache, also called <span><strong class="command">acache</strong></span>,
+
+
+ <p>
+ The additional section cache, also called <span class="command"><strong>acache</strong></span>,
is an internal cache to improve the response performance of BIND 9.
When additional section caching is enabled, BIND 9 will
cache an internal short-cut to the additional section content for
each answer RR.
- Note that <span><strong class="command">acache</strong></span> is an internal caching
+ Note that <span class="command"><strong>acache</strong></span> is an internal caching
mechanism of BIND 9, and is not related to the DNS caching
server function.
</p>
-<p>
+
+ <p>
Additional section caching does not change the
response content (except the RRsets ordering of the additional
section, see below), but can improve the response performance
It is particularly effective when BIND 9 acts as an authoritative
server for a zone that has many delegations with many glue RRs.
</p>
-<p>
+
+ <p>
In order to obtain the maximum performance improvement
from additional section caching, setting
- <span><strong class="command">additional-from-cache</strong></span>
- to <span><strong class="command">no</strong></span> is recommended, since the current
- implementation of <span><strong class="command">acache</strong></span>
+ <span class="command"><strong>additional-from-cache</strong></span>
+ to <span class="command"><strong>no</strong></span> is recommended, since the current
+ implementation of <span class="command"><strong>acache</strong></span>
does not short-cut of additional section information from the
DNS cache data.
</p>
-<p>
- One obvious disadvantage of <span><strong class="command">acache</strong></span> is
+
+ <p>
+ One obvious disadvantage of <span class="command"><strong>acache</strong></span> is
that it requires much more
memory for the internal cached data.
Thus, if the response performance does not matter and memory
consumption is much more critical, the
- <span><strong class="command">acache</strong></span> mechanism can be
- disabled by setting <span><strong class="command">acache-enable</strong></span> to
- <span><strong class="command">no</strong></span>.
+ <span class="command"><strong>acache</strong></span> mechanism can be
+ disabled by setting <span class="command"><strong>acache-enable</strong></span> to
+ <span class="command"><strong>no</strong></span>.
It is also possible to specify the upper limit of memory
consumption
- for acache by using <span><strong class="command">max-acache-size</strong></span>.
+ for acache by using <span class="command"><strong>max-acache-size</strong></span>.
</p>
-<p>
+
+ <p>
Additional section caching also has a minor effect on the
RRset ordering in the additional section.
- Without <span><strong class="command">acache</strong></span>,
- <span><strong class="command">cyclic</strong></span> order is effective for the additional
+ Without <span class="command"><strong>acache</strong></span>,
+ <span class="command"><strong>cyclic</strong></span> order is effective for the additional
section as well as the answer and authority sections.
However, additional section caching fixes the ordering when it
first caches an RRset for the additional section, and the same
ordering will be kept in succeeding responses, regardless of the
- setting of <span><strong class="command">rrset-order</strong></span>.
+ setting of <span class="command"><strong>rrset-order</strong></span>.
The effect of this should be minor, however, since an
RRset in the additional section
typically only contains a small number of RRs (and in many cases
it only contains a single RR), in which case the
ordering does not matter much.
</p>
-<p>
+
+ <p>
The following is a summary of options related to
- <span><strong class="command">acache</strong></span>.
- </p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">acache-enable</strong></span></span></dt>
-<dd><p>
- If <span><strong class="command">yes</strong></span>, additional section caching is
- enabled. The default value is <span><strong class="command">no</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">acache-cleaning-interval</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>acache</strong></span>.
+ </p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>acache-enable</strong></span></span></dt>
+<dd>
+ <p>
+ If <span class="command"><strong>yes</strong></span>, additional section caching is
+ enabled. The default value is <span class="command"><strong>no</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>acache-cleaning-interval</strong></span></span></dt>
+<dd>
+ <p>
The server will remove stale cache entries, based on an LRU
based
- algorithm, every <span><strong class="command">acache-cleaning-interval</strong></span> minutes.
+ algorithm, every <span class="command"><strong>acache-cleaning-interval</strong></span> minutes.
The default is 60 minutes.
If set to 0, no periodic cleaning will occur.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-acache-size</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-acache-size</strong></span></span></dt>
+<dd>
+ <p>
The maximum amount of memory in bytes to use for the server's acache.
When the amount of data in the acache reaches this limit,
the server
separately to the
acache of each view.
The default is <code class="literal">16M</code>.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2590197"></a>Content Filtering</h4></div></div></div>
-<p>
+<a name="id-1.7.6.22.23"></a>Content Filtering</h4></div></div></div>
+
+ <p>
<acronym class="acronym">BIND</acronym> 9 provides the ability to filter
out DNS responses from external DNS servers containing
certain types of data in the answer section.
Specifically, it can reject address (A or AAAA) records if
the corresponding IPv4 or IPv6 addresses match the given
<code class="varname">address_match_list</code> of the
- <span><strong class="command">deny-answer-addresses</strong></span> option.
+ <span class="command"><strong>deny-answer-addresses</strong></span> option.
It can also reject CNAME or DNAME records if the "alias"
name (i.e., the CNAME alias or the substituted query name
due to DNAME) matches the
given <code class="varname">namelist</code> of the
- <span><strong class="command">deny-answer-aliases</strong></span> option, where
+ <span class="command"><strong>deny-answer-aliases</strong></span> option, where
"match" means the alias name is a subdomain of one of
the <code class="varname">name_list</code> elements.
If the optional <code class="varname">namelist</code> is specified
- with <span><strong class="command">except-from</strong></span>, records whose query name
+ with <span class="command"><strong>except-from</strong></span>, records whose query name
matches the list will be accepted regardless of the filter
setting.
Likewise, if the alias name is a subdomain of the
- corresponding zone, the <span><strong class="command">deny-answer-aliases</strong></span>
+ corresponding zone, the <span class="command"><strong>deny-answer-aliases</strong></span>
filter will not apply;
for example, even if "example.com" is specified for
- <span><strong class="command">deny-answer-aliases</strong></span>,
+ <span class="command"><strong>deny-answer-aliases</strong></span>,
</p>
<pre class="programlisting">www.example.com. CNAME xxx.example.com.</pre>
-<p>
+
+ <p>
returned by an "example.com" server will be accepted.
</p>
-<p>
+
+ <p>
In the <code class="varname">address_match_list</code> of the
- <span><strong class="command">deny-answer-addresses</strong></span> option, only
+ <span class="command"><strong>deny-answer-addresses</strong></span> option, only
<code class="varname">ip_addr</code>
and <code class="varname">ip_prefix</code>
are meaningful;
any <code class="varname">key_id</code> will be silently ignored.
</p>
-<p>
+
+ <p>
If a response message is rejected due to the filtering,
the entire message is discarded without being cached, and
a SERVFAIL error will be returned to the client.
</p>
-<p>
+
+ <p>
This filtering is intended to prevent "DNS rebinding attacks," in
which an attacker, in response to a query for a domain name the
attacker controls, returns an IP address within your own network or
to get access to an internal node of your local network
that couldn't be externally accessed otherwise.
See the paper available at
- <a href="http://portal.acm.org/citation.cfm?id=1315245.1315298" target="_top">
+ <a class="ulink" href="http://portal.acm.org/citation.cfm?id=1315245.1315298" target="_top">
http://portal.acm.org/citation.cfm?id=1315245.1315298
</a>
for more details about the attacks.
</p>
-<p>
+
+ <p>
For example, if you own a domain named "example.net" and
your internal network uses an IPv4 prefix 192.0.2.0/24,
you might specify the following rules:
</p>
+
<pre class="programlisting">deny-answer-addresses { 192.0.2.0/24; } except-from { "example.net"; };
deny-answer-aliases { "example.net"; };
</pre>
-<p>
+
+ <p>
If an external attacker lets a web browser in your local
network look up an IPv4 address of "attacker.example.com",
the attacker's DNS server would return a response like this:
</p>
+
<pre class="programlisting">attacker.example.com. A 192.0.2.1</pre>
-<p>
+
+ <p>
in the answer section.
Since the rdata of this record (the IPv4 address) matches
the specified prefix 192.0.2.0/24, this response will be
ignored.
</p>
-<p>
+
+ <p>
On the other hand, if the browser looks up a legitimate
internal web server "www.example.net" and the
following response is returned to
the <acronym class="acronym">BIND</acronym> 9 server
</p>
+
<pre class="programlisting">www.example.net. A 192.0.2.2</pre>
-<p>
+
+ <p>
it will be accepted since the owner name "www.example.net"
- matches the <span><strong class="command">except-from</strong></span> element,
+ matches the <span class="command"><strong>except-from</strong></span> element,
"example.net".
</p>
-<p>
+
+ <p>
Note that this is not really an attack on the DNS per se.
In fact, there is nothing wrong for an "external" name to
be mapped to your "internal" IP address or domain name
very sure you have no other choice and the attack is a
real threat for your applications.
</p>
-<p>
+
+ <p>
Care should be particularly taken if you want to use this
option for addresses within 127.0.0.0/8.
These addresses are obviously "internal", but many
Filtering out DNS records containing this address
spuriously can break such applications.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2590459"></a>Response Policy Zone (RPZ) Rewriting</h4></div></div></div>
-<p>
+<a name="id-1.7.6.22.24"></a>Response Policy Zone (RPZ) Rewriting</h4></div></div></div>
+
+ <p>
<acronym class="acronym">BIND</acronym> 9 includes a limited
mechanism to modify DNS responses for requests
analogous to email anti-spam DNS blacklists.
deny the existence of IP addresses for domains (NODATA),
or contain other IP addresses or data.
</p>
-<p>
+
+ <p>
Response policy zones are named in the
- <span><strong class="command">response-policy</strong></span> option for the view or among the
+ <span class="command"><strong>response-policy</strong></span> option for the view or among the
global options if there is no response-policy option for the view.
Response policy zones are ordinary DNS zones containing RRsets
that can be queried normally if allowed.
It is usually best to restrict those queries with something like
- <span><strong class="command">allow-query { localhost; };</strong></span>.
+ <span class="command"><strong>allow-query { localhost; };</strong></span>.
</p>
-<p>
- A <span><strong class="command">response-policy</strong></span> option can support
+
+ <p>
+ A <span class="command"><strong>response-policy</strong></span> option can support
multiple policy zones. To maximize performance, a radix
tree is used to quickly identify response policy zones
containing triggers that match the current query. This
imposes an upper limit of 32 on the number of policy zones
- in a single <span><strong class="command">response-policy</strong></span> option; more
+ in a single <span class="command"><strong>response-policy</strong></span> option; more
than that is a configuration error.
</p>
-<p>
+
+ <p>
Five policy triggers can be encoded in RPZ records.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">RPZ-CLIENT-IP</strong></span></span></dt>
+<div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>RPZ-CLIENT-IP</strong></span></span></dt>
<dd>
-<p>
IP records are triggered by the IP address of the
DNS client.
Client IP address triggers are encoded in records that have
owner names that are subdomains of
- <span><strong class="command">rpz-client-ip</strong></span> relativized to the
+ <span class="command"><strong>rpz-client-ip</strong></span> relativized to the
policy zone origin name
and encode an address or address block.
IPv4 addresses are represented as
B4 is the decimal value of the least significant byte of the
IPv4 address as in IN-ADDR.ARPA.
</p>
-<p>
+
+ <p>
IPv6 addresses are encoded in a format similar
to the standard IPv6 text representation,
<strong class="userinput"><code>prefixlength.W8.W7.W6.W5.W4.W3.W2.W1.rpz-client-ip</code></strong>.
encodings.
The IPv6 prefix length must be between 1 and 128.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">QNAME</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>QNAME</strong></span></span></dt>
+<dd>
+ <p>
QNAME policy records are triggered by query names of
requests and targets of CNAME records resolved to generate
the response.
The owner name of a QNAME policy record is
the query name relativized to the policy zone.
- </p></dd>
-<dt><span class="term"><span><strong class="command">RPZ-IP</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>RPZ-IP</strong></span></span></dt>
+<dd>
+ <p>
IP triggers are IP addresses in an
A or AAAA record in the ANSWER section of a response.
They are encoded like client-IP triggers except as
- subdomains of <span><strong class="command">rpz-ip</strong></span>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">RPZ-NSDNAME</strong></span></span></dt>
-<dd><p>
+ subdomains of <span class="command"><strong>rpz-ip</strong></span>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>RPZ-NSDNAME</strong></span></span></dt>
+<dd>
+ <p>
NSDNAME triggers match names of authoritative servers
for the query name, a parent of the query name, a CNAME for
query name, or a parent of a CNAME.
They are encoded as subdomains of
- <span><strong class="command">rpz-nsdname</strong></span> relativized
+ <span class="command"><strong>rpz-nsdname</strong></span> relativized
to the RPZ origin name.
NSIP triggers match IP addresses in A and
AAAA RRsets for domains that can be checked against NSDNAME
policy records.
- </p></dd>
-<dt><span class="term"><span><strong class="command">RPZ-NSIP</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>RPZ-NSIP</strong></span></span></dt>
+<dd>
+ <p>
NSIP triggers are encoded like IP triggers except as
- subdomains of <span><strong class="command">rpz-nsip</strong></span>.
+ subdomains of <span class="command"><strong>rpz-nsip</strong></span>.
NSDNAME and NSIP triggers are checked only for names with at
- least <span><strong class="command">min-ns-dots</strong></span> dots.
- The default value of <span><strong class="command">min-ns-dots</strong></span> is 1 to
+ least <span class="command"><strong>min-ns-dots</strong></span> dots.
+ The default value of <span class="command"><strong>min-ns-dots</strong></span> is 1 to
exclude top level domains.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
<p>
</p>
-<p>
+
+ <p>
The query response is checked against all response policy zones,
so two or more policy records can be triggered by a response.
Because DNS responses are rewritten according to at most one
policy record, a single record encoding an action (other than
- <span><strong class="command">DISABLED</strong></span> actions) must be chosen.
+ <span class="command"><strong>DISABLED</strong></span> actions) must be chosen.
Triggers or the records that encode them are chosen for the
rewriting in the following order:
</p>
-<div class="orderedlist"><ol type="1">
-<li>Choose the triggered record in the zone that appears
- first in the <span><strong class="command">response-policy</strong></span> option.
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">Choose the triggered record in the zone that appears
+ first in the <span class="command"><strong>response-policy</strong></span> option.
</li>
-<li>Prefer CLIENT-IP to QNAME to IP to NSDNAME to NSIP
+<li class="listitem">Prefer CLIENT-IP to QNAME to IP to NSDNAME to NSIP
triggers in a single zone.
</li>
-<li>Among NSDNAME triggers, prefer the
+<li class="listitem">Among NSDNAME triggers, prefer the
trigger that matches the smallest name under the DNSSEC ordering.
</li>
-<li>Among IP or NSIP triggers, prefer the trigger
+<li class="listitem">Among IP or NSIP triggers, prefer the trigger
with the longest prefix.
</li>
-<li>Among triggers with the same prefix length,
+<li class="listitem">Among triggers with the same prefix length,
prefer the IP or NSIP trigger that matches
the smallest IP address.
</li>
</ol></div>
<p>
</p>
-<p>
+
+ <p>
When the processing of a response is restarted to resolve
DNAME or CNAME records and a policy record set has
not been triggered,
all response policy zones are again consulted for the
DNAME or CNAME names and addresses.
</p>
-<p>
+
+ <p>
RPZ record sets are any types of DNS record except
DNAME or DNSSEC that encode actions or responses to
individual queries.
Any of the policies can be used with any of the triggers.
- For example, while the <span><strong class="command">TCP-only</strong></span> policy is
- commonly used with <span><strong class="command">client-IP</strong></span> triggers,
+ For example, while the <span class="command"><strong>TCP-only</strong></span> policy is
+ commonly used with <span class="command"><strong>client-IP</strong></span> triggers,
it can be used with any type of trigger to force the use of
TCP for responses with owner names in a zone.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">PASSTHRU</strong></span></span></dt>
-<dd><p>
+<div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>PASSTHRU</strong></span></span></dt>
+<dd>
+ <p>
The whitelist policy is specified
- by a CNAME whose target is <span><strong class="command">rpz-passthru</strong></span>.
+ by a CNAME whose target is <span class="command"><strong>rpz-passthru</strong></span>.
It causes the response to not be rewritten
and is most often used to "poke holes" in policies for
CIDR blocks.
- </p></dd>
-<dt><span class="term"><span><strong class="command">DROP</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>DROP</strong></span></span></dt>
+<dd>
+ <p>
The blacklist policy is specified
- by a CNAME whose target is <span><strong class="command">rpz-drop</strong></span>.
+ by a CNAME whose target is <span class="command"><strong>rpz-drop</strong></span>.
It causes the response to be discarded.
Nothing is sent to the DNS client.
- </p></dd>
-<dt><span class="term"><span><strong class="command">TCP-Only</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>TCP-Only</strong></span></span></dt>
+<dd>
+ <p>
The "slip" policy is specified
- by a CNAME whose target is <span><strong class="command">rpz-tcp-only</strong></span>.
+ by a CNAME whose target is <span class="command"><strong>rpz-tcp-only</strong></span>.
It changes UDP responses to short, truncated DNS responses
that require the DNS client to try again with TCP.
It is used to mitigate distributed DNS reflection attacks.
- </p></dd>
-<dt><span class="term"><span><strong class="command">NXDOMAIN</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>NXDOMAIN</strong></span></span></dt>
+<dd>
+ <p>
The domain undefined response is encoded
by a CNAME whose target is the root domain (.)
- </p></dd>
-<dt><span class="term"><span><strong class="command">NODATA</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>NODATA</strong></span></span></dt>
+<dd>
+ <p>
The empty set of resource records is specified by
CNAME whose target is the wildcard top-level
domain (*.).
It rewrites the response to NODATA or ANCOUNT=1.
- </p></dd>
-<dt><span class="term"><span><strong class="command">Local Data</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>Local Data</strong></span></span></dt>
<dd>
-<p>
A set of ordinary DNS records can be used to answer queries.
Queries for record types not the set are answered with
NODATA.
</p>
-<p>
+
+ <p>
A special form of local data is a CNAME whose target is a
wildcard such as *.example.com.
It is used as if were an ordinary CNAME after the astrisk (*)
The purpose for this special form is query logging in the
walled garden's authority DNS server.
</p>
-</dd>
+ </dd>
</dl></div>
<p>
</p>
-<p>
+
+ <p>
All of the actions specified in all of the individual records
in a policy zone
- can be overridden with a <span><strong class="command">policy</strong></span> clause in the
- <span><strong class="command">response-policy</strong></span> option.
+ can be overridden with a <span class="command"><strong>policy</strong></span> clause in the
+ <span class="command"><strong>response-policy</strong></span> option.
An organization using a policy zone provided by another
organization might use this mechanism to redirect domains
to its own walled garden.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">GIVEN</strong></span></span></dt>
-<dd><p>The placeholder policy says "do not override but
+<div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>GIVEN</strong></span></span></dt>
+<dd>
+ <p>The placeholder policy says "do not override but
perform the action specified in the zone."
- </p></dd>
-<dt><span class="term"><span><strong class="command">DISABLED</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>DISABLED</strong></span></span></dt>
+<dd>
+ <p>
The testing override policy causes policy zone records to do
nothing but log what they would have done if the
policy zone were not disabled.
Disabled policy zones should appear first,
because they will often not be logged
if a higher precedence trigger is found first.
- </p></dd>
+ </p>
+ </dd>
<dt>
-<span class="term"><span><strong class="command">PASSTHRU</strong></span>, </span><span class="term"><span><strong class="command">DROP</strong></span>, </span><span class="term"><span><strong class="command">TCP-Only</strong></span>, </span><span class="term"><span><strong class="command">NXDOMAIN</strong></span>, </span><span class="term"><span><strong class="command">NODATA</strong></span></span>
+<span class="term"><span class="command"><strong>PASSTHRU</strong></span>, </span><span class="term"><span class="command"><strong>DROP</strong></span>, </span><span class="term"><span class="command"><strong>TCP-Only</strong></span>, </span><span class="term"><span class="command"><strong>NXDOMAIN</strong></span>, </span><span class="term"><span class="command"><strong>NODATA</strong></span></span>
</dt>
-<dd><p>
+<dd>
+ <p>
override with the corresponding per-record policy.
- </p></dd>
-<dt><span class="term"><span><strong class="command">CNAME domain</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>CNAME domain</strong></span></span></dt>
+<dd>
+ <p>
causes all RPZ policy records to act as if they were
"cname domain" records.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
<p>
</p>
-<p>
+
+ <p>
By default, the actions encoded in a response policy zone
are applied only to queries that ask for recursion (RD=1).
That default can be changed for a single policy zone or
all response policy zones in a view
- with a <span><strong class="command">recursive-only no</strong></span> clause.
+ with a <span class="command"><strong>recursive-only no</strong></span> clause.
This feature is useful for serving the same zone files
both inside and outside an RFC 1918 cloud and using RPZ to
delete answers that would otherwise contain RFC 1918 values
on the externally visible name server or view.
</p>
-<p>
+
+ <p>
Also by default, RPZ actions are applied only to DNS requests
that either do not request DNSSEC metadata (DO=0) or when no
DNSSEC records are available for request name in the original
zone (not the response policy zone). This default can be
changed for all response policy zones in a view with a
- <span><strong class="command">break-dnssec yes</strong></span> clause. In that case, RPZ
+ <span class="command"><strong>break-dnssec yes</strong></span> clause. In that case, RPZ
actions are applied regardless of DNSSEC. The name of the
clause option reflects the fact that results rewritten by RPZ
actions cannot verify.
</p>
-<p>
+
+ <p>
No DNS records are needed for a QNAME or Client-IP trigger.
The name or IP address itself is sufficient,
so in principle the query name need not be recursively resolved.
policy triggers are considered. Because listed domains often
have slow authoritative servers, this default behavior can cost
significant time.
- The <span><strong class="command">qname-wait-recurse no</strong></span> option
+ The <span class="command"><strong>qname-wait-recurse no</strong></span> option
overrides that default behavior when recursion cannot
change a non-error response.
The option does not affect QNAME or client-IP triggers
after other zones containing IP, NSIP and NSDNAME triggers, because
those may depend on the A, AAAA, and NS records that would be
found during recursive resolution. It also does not affect
- DNSSEC requests (DO=1) unless <span><strong class="command">break-dnssec yes</strong></span>
+ DNSSEC requests (DO=1) unless <span class="command"><strong>break-dnssec yes</strong></span>
is in use, because the response would depend on whether or not
RRSIG records were found during resolution.
Using this option can cause error responses such as SERVFAIL to
appear to be rewritten, since no recursion is being done to
discover problems at the authoritative server.
</p>
-<p>
+
+ <p>
The TTL of a record modified by RPZ policies is set from the
TTL of the relevant record in policy zone. It is then limited
to a maximum value.
- The <span><strong class="command">max-policy-ttl</strong></span> clause changes the
+ The <span class="command"><strong>max-policy-ttl</strong></span> clause changes the
maximum seconds from its default of 5.
</p>
-<p>
+
+ <p>
For example, you might use this option statement
</p>
<pre class="programlisting"> response-policy { zone "badlist"; };</pre>
-<p>
and this zone statement
</p>
<pre class="programlisting"> zone "badlist" {type master; file "master/badlist"; allow-query {none;}; };</pre>
-<p>
with this zone file
</p>
<pre class="programlisting">$TTL 1H
*.example.com CNAME rpz-tcp-only.
</pre>
-<p>
RPZ can affect server performance.
Each configured response policy zone requires the server to
perform one to four additional database lookups before a
A server with four response policy zones with QNAME and IP
triggers might have a maximum QPS rate about 50% lower.
</p>
-<p>
+
+ <p>
Responses rewritten by RPZ are counted in the
- <span><strong class="command">RPZRewrites</strong></span> statistics.
+ <span class="command"><strong>RPZRewrites</strong></span> statistics.
</p>
-<p>
- The <span><strong class="command">log</strong></span> clause can be used to optionally
+
+ <p>
+ The <span class="command"><strong>log</strong></span> clause can be used to optionally
turn off rewrite logging for a particular response policy
zone. By default, all rewrites are logged.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2591243"></a>Response Rate Limiting</h4></div></div></div>
-<p>
+<a name="id-1.7.6.22.25"></a>Response Rate Limiting</h4></div></div></div>
+
+ <p>
Excessive almost identical UDP <span class="emphasis"><em>responses</em></span>
can be controlled by configuring a
- <span><strong class="command">rate-limit</strong></span> clause in an
- <span><strong class="command">options</strong></span> or <span><strong class="command">view</strong></span> statement.
+ <span class="command"><strong>rate-limit</strong></span> clause in an
+ <span class="command"><strong>options</strong></span> or <span class="command"><strong>view</strong></span> statement.
This mechanism keeps authoritative BIND 9 from being used
in amplifying reflection denial of service (DoS) attacks.
Short truncated (TC=1) responses can be sent to provide
Legitimate clients react to dropped or truncated response
by retrying with UDP or with TCP respectively.
</p>
-<p>
+
+ <p>
This mechanism is intended for authoritative DNS servers.
It can be used on recursive servers but can slow
applications such as SMTP servers (mail receivers) and
same domains.
When possible, closing "open" recursive servers is better.
</p>
-<p>
+
+ <p>
Response rate limiting uses a "credit" or "token bucket" scheme.
Each combination of identical response and client
has a conceptual account that earns a specified number
while the account is negative.
Responses are tracked within a rolling window of time
which defaults to 15 seconds, but can be configured with
- the <span><strong class="command">window</strong></span> option to any value from
+ the <span class="command"><strong>window</strong></span> option to any value from
1 to 3600 seconds (1 hour).
The account cannot become more positive than
the per-second limit
- or more negative than <span><strong class="command">window</strong></span>
+ or more negative than <span class="command"><strong>window</strong></span>
times the per-second limit.
When the specified number of credits for a class of
responses is set to 0, those responses are not rate limited.
</p>
-<p>
+
+ <p>
The notions of "identical response" and "DNS client"
for rate limiting are not simplistic.
All responses to an address block are counted as if to a
single client.
The prefix lengths of addresses blocks are
- specified with <span><strong class="command">ipv4-prefix-length</strong></span> (default 24)
- and <span><strong class="command">ipv6-prefix-length</strong></span> (default 56).
+ specified with <span class="command"><strong>ipv4-prefix-length</strong></span> (default 24)
+ and <span class="command"><strong>ipv6-prefix-length</strong></span> (default 56).
</p>
-<p>
+
+ <p>
All non-empty responses for a valid domain name (qname)
and record type (qtype) are identical and have a limit specified
- with <span><strong class="command">responses-per-second</strong></span>
+ with <span class="command"><strong>responses-per-second</strong></span>
(default 0 or no limit).
All empty (NODATA) responses for a valid domain,
regardless of query type, are identical.
Responses in the NODATA class are limited by
- <span><strong class="command">nodata-per-second</strong></span>
- (default <span><strong class="command">responses-per-second</strong></span>).
+ <span class="command"><strong>nodata-per-second</strong></span>
+ (default <span class="command"><strong>responses-per-second</strong></span>).
Requests for any and all undefined subdomains of a given
valid domain result in NXDOMAIN errors, and are identical
regardless of query type.
- They are limited by <span><strong class="command">nxdomains-per-second</strong></span>
- (default <span><strong class="command">responses-per-second</strong></span>).
+ They are limited by <span class="command"><strong>nxdomains-per-second</strong></span>
+ (default <span class="command"><strong>responses-per-second</strong></span>).
This controls some attacks using random names, but
can be relaxed or turned off (set to 0)
on servers that expect many legitimate
NXDOMAIN responses, such as from anti-spam blacklists.
Referrals or delegations to the server of a given
domain are identical and are limited by
- <span><strong class="command">referrals-per-second</strong></span>
- (default <span><strong class="command">responses-per-second</strong></span>).
+ <span class="command"><strong>referrals-per-second</strong></span>
+ (default <span class="command"><strong>responses-per-second</strong></span>).
</p>
-<p>
+
+ <p>
Responses generated from local wildcards are counted and limited
as if they were for the parent domain name.
This controls flooding using random.wild.example.com.
</p>
-<p>
+
+ <p>
All requests that result in DNS errors other
than NXDOMAIN, such as SERVFAIL and FORMERR, are identical
regardless of requested name (qname) or record type (qtype).
This controls attacks using invalid requests or distant,
broken authoritative servers.
By default the limit on errors is the same as the
- <span><strong class="command">responses-per-second</strong></span> value,
+ <span class="command"><strong>responses-per-second</strong></span> value,
but it can be set separately with
- <span><strong class="command">errors-per-second</strong></span>.
+ <span class="command"><strong>errors-per-second</strong></span>.
</p>
-<p>
+
+ <p>
Many attacks using DNS involve UDP requests with forged source
addresses.
Rate limiting prevents the use of BIND 9 to flood a network
but could let a third party block responses to legitimate requests.
There is a mechanism that can answer some legitimate
requests from a client whose address is being forged in a flood.
- Setting <span><strong class="command">slip</strong></span> to 2 (its default) causes every
+ Setting <span class="command"><strong>slip</strong></span> to 2 (its default) causes every
other UDP request to be answered with a small truncated (TC=1)
response.
The small size and reduced frequency, and so lack of
amplification, of "slipped" responses make them unattractive
for reflection DoS attacks.
- <span><strong class="command">slip</strong></span> must be between 0 and 10.
+ <span class="command"><strong>slip</strong></span> must be between 0 and 10.
A value of 0 does not "slip":
no truncated responses are sent due to rate limiting,
all responses are dropped.
values between 2 and 10 cause every n'th response to slip.
Some error responses including REFUSED and SERVFAIL
cannot be replaced with truncated responses and are instead
- leaked at the <span><strong class="command">slip</strong></span> rate.
+ leaked at the <span class="command"><strong>slip</strong></span> rate.
</p>
-<p>
+
+ <p>
(NOTE: Dropped responses from an authoritative server may
reduce the difficulty of a third party successfully forging
a response to a recursive resolver. The best security
to validate the responses. When this is not an option,
operators who are more concerned with response integrity
than with flood mitigation may consider setting
- <span><strong class="command">slip</strong></span> to 1, causing all rate-limited
+ <span class="command"><strong>slip</strong></span> to 1, causing all rate-limited
responses to be truncated rather than dropped. This reduces
the effectiveness of rate-limiting against reflection attacks.)
</p>
-<p>
+
+ <p>
When the approximate query per second rate exceeds
- the <span><strong class="command">qps-scale</strong></span> value,
- then the <span><strong class="command">responses-per-second</strong></span>,
- <span><strong class="command">errors-per-second</strong></span>,
- <span><strong class="command">nxdomains-per-second</strong></span> and
- <span><strong class="command">all-per-second</strong></span> values are reduced by the
- ratio of the current rate to the <span><strong class="command">qps-scale</strong></span> value.
+ the <span class="command"><strong>qps-scale</strong></span> value,
+ then the <span class="command"><strong>responses-per-second</strong></span>,
+ <span class="command"><strong>errors-per-second</strong></span>,
+ <span class="command"><strong>nxdomains-per-second</strong></span> and
+ <span class="command"><strong>all-per-second</strong></span> values are reduced by the
+ ratio of the current rate to the <span class="command"><strong>qps-scale</strong></span> value.
This feature can tighten defenses during attacks.
For example, with
- <span><strong class="command">qps-scale 250; responses-per-second 20;</strong></span> and
+ <span class="command"><strong>qps-scale 250; responses-per-second 20;</strong></span> and
a total query rate of 1000 queries/second for all queries from
all DNS clients including via TCP,
then the effective responses/second limit changes to
Responses sent via TCP are not limited
but are counted to compute the query per second rate.
</p>
-<p>
- The optional <span><strong class="command">domain</strong></span> clause specifies
+
+ <p>
+ The optional <span class="command"><strong>domain</strong></span> clause specifies
the namespace to which rate limits will apply. It
is possible to use different rate limits for different names
- by specifying multiple <span><strong class="command">rate-limit</strong></span> blocks
- with different <span><strong class="command">domain</strong></span> clauses.
- The <span><strong class="command">rate-limit</strong></span> statement's
- <span><strong class="command">domain</strong></span> most closely matches the query
+ by specifying multiple <span class="command"><strong>rate-limit</strong></span> blocks
+ with different <span class="command"><strong>domain</strong></span> clauses.
+ The <span class="command"><strong>rate-limit</strong></span> statement's
+ <span class="command"><strong>domain</strong></span> most closely matches the query
name will be the one applied to a given query.
</p>
-<p>
+
+ <p>
Rate limiters for different name spaces maintain
separate counters: If, for example, there is a
- <span><strong class="command">rate-limit</strong></span> statement for "com" and
+ <span class="command"><strong>rate-limit</strong></span> statement for "com" and
another for "example.com", queries matching "example.com"
will not be debited against the rate limiter for "com".
</p>
-<p>
- If a <span><strong class="command">rate-limit</strong></span> statement does not specify a
- <span><strong class="command">domain</strong></span>, then it applies to the root domain
+
+ <p>
+ If a <span class="command"><strong>rate-limit</strong></span> statement does not specify a
+ <span class="command"><strong>domain</strong></span>, then it applies to the root domain
(".") and thus affects the entire DNS namespace, except those
- portions covered by other <span><strong class="command">rate-limit</strong></span>
+ portions covered by other <span class="command"><strong>rate-limit</strong></span>
statements.
</p>
-<p>
+
+ <p>
Communities of DNS clients can be given their own parameters or no
rate limiting by putting
- <span><strong class="command">rate-limit</strong></span> statements in <span><strong class="command">view</strong></span>
- statements instead of the global <span><strong class="command">option</strong></span>
+ <span class="command"><strong>rate-limit</strong></span> statements in <span class="command"><strong>view</strong></span>
+ statements instead of the global <span class="command"><strong>option</strong></span>
statement.
- A <span><strong class="command">rate-limit</strong></span> statement in a view replaces,
- rather than supplementing, a <span><strong class="command">rate-limit</strong></span>
+ A <span class="command"><strong>rate-limit</strong></span> statement in a view replaces,
+ rather than supplementing, a <span class="command"><strong>rate-limit</strong></span>
statement among the main options.
DNS clients within a view can be exempted from rate limits
- with the <span><strong class="command">exempt-clients</strong></span> clause.
+ with the <span class="command"><strong>exempt-clients</strong></span> clause.
</p>
-<p>
+
+ <p>
UDP responses of all kinds can be limited with the
- <span><strong class="command">all-per-second</strong></span> phrase. This rate
+ <span class="command"><strong>all-per-second</strong></span> phrase. This rate
limiting is unlike the rate limiting provided by
- <span><strong class="command">responses-per-second</strong></span>,
- <span><strong class="command">errors-per-second</strong></span>, and
- <span><strong class="command">nxdomains-per-second</strong></span> on a DNS server
+ <span class="command"><strong>responses-per-second</strong></span>,
+ <span class="command"><strong>errors-per-second</strong></span>, and
+ <span class="command"><strong>nxdomains-per-second</strong></span> on a DNS server
which are often invisible to the victim of a DNS
reflection attack. Unless the forged requests of the
attack are the same as the legitimate requests of the
victim, the victim's requests are not affected. Responses
- affected by an <span><strong class="command">all-per-second</strong></span> limit
- are always dropped; the <span><strong class="command">slip</strong></span> value
- has no effect. An <span><strong class="command">all-per-second</strong></span>
+ affected by an <span class="command"><strong>all-per-second</strong></span> limit
+ are always dropped; the <span class="command"><strong>slip</strong></span> value
+ has no effect. An <span class="command"><strong>all-per-second</strong></span>
limit should be at least 4 times as large as the other
limits, because single DNS clients often send bursts
of legitimate requests. For example, the receipt of a
server for NS, PTR, A, and AAAA records as the incoming
SMTP/TCP/IP connection is considered. The SMTP server
can need additional NS, A, AAAA, MX, TXT, and SPF records
- as it considers the STMP <span><strong class="command">Mail From</strong></span>
+ as it considers the STMP <span class="command"><strong>Mail From</strong></span>
command. Web browsers often repeatedly resolve the
same names that are repeated in HTML <IMG> tags
- in a page. <span><strong class="command">all-per-second</strong></span> is similar
+ in a page. <span class="command"><strong>all-per-second</strong></span> is similar
to the rate limiting offered by firewalls but often
inferior. Attacks that justify ignoring the contents
of DNS responses are likely to be attacks on the DNS
or parsing DNS requests, but that rate limiting must
be done before the DNS server sees the requests.
</p>
-<p>
+
+ <p>
The maximum size of the table used to track requests and
- rate limit responses is set with <span><strong class="command">max-table-size</strong></span>.
+ rate limit responses is set with <span class="command"><strong>max-table-size</strong></span>.
Each entry in the table is between 40 and 80 bytes.
The table needs approximately as many entries as the number
of requests received per second.
The default is 20,000.
To reduce the cold start of growing the table,
- <span><strong class="command">min-table-size</strong></span> (default 500)
+ <span class="command"><strong>min-table-size</strong></span> (default 500)
can set the minimum table size.
- Enable <span><strong class="command">rate-limit</strong></span> category logging to monitor
+ Enable <span class="command"><strong>rate-limit</strong></span> category logging to monitor
expansions of the table and inform
choices for the initial and maximum table size.
</p>
-<p>
- Use <span><strong class="command">log-only yes</strong></span> to test rate limiting parameters
+
+ <p>
+ Use <span class="command"><strong>log-only yes</strong></span> to test rate limiting parameters
without actually dropping any requests.
</p>
-<p>
+
+ <p>
Responses dropped by rate limits are included in the
- <span><strong class="command">RateDropped</strong></span> and <span><strong class="command">QryDropped</strong></span>
+ <span class="command"><strong>RateDropped</strong></span> and <span class="command"><strong>QryDropped</strong></span>
statistics.
Responses that truncated by rate limits are included in
- <span><strong class="command">RateSlipped</strong></span> and <span><strong class="command">RespTruncated</strong></span>.
+ <span class="command"><strong>RateSlipped</strong></span> and <span class="command"><strong>RespTruncated</strong></span>.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"></div>
-<p>
Named supports NXDOMAIN redirection via two methods:
</p>
-<div class="itemizedlist"><ul type="disc">
-<li>Redirect zone <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone
- Statement Grammar">the section called “<span><strong class="command">zone</strong></span>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">Redirect zone <a class="xref" href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone Statement Grammar">the section called “<span class="command"><strong>zone</strong></span>
Statement Grammar”</a>
</li>
-<li>Redirect namespace</li>
+<li class="listitem">Redirect namespace</li>
</ul></div>
<p>
</p>
-<p>
With both methods when named gets a NXDOMAIN response
it examines a seperate namespace to see if the NXDOMAIN
response should be replaced with a alternative response.
</p>
-<p>
- With a redirect zone (<span><strong class="command">zone "." { type redirect; };</strong></span>), the
+ With a redirect zone (<span class="command"><strong>zone "." { type redirect; };</strong></span>), the
data used to replace the NXDOMAIN is held in a single
zone which is not part of the normal namespace. All the
redirect information is contained in the zone; there are
no delegations.
</p>
-<p>
- With a redirect namespace (<span><strong class="command">option { nxdomain-redirect
+ With a redirect namespace (<span class="command"><strong>option { nxdomain-redirect
<suffix> };</strong></span>) the data used to replace the
NXDOMAIN is part of the normal namespace and is looked up by
appending the specified suffix to the original query name.
the replacement data or a NXDOMAIN indicating that there
is no replacement.
</p>
-<p>
If both a redirect zone and a redirect namespace are configured,
the redirect zone is tried first.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="server_statement_grammar"></a><span><strong class="command">server</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">server</strong></span> <em class="replaceable"><code>ip_addr[/prefixlen]</code></em> {
+<a name="server_statement_grammar"></a><span class="command"><strong>server</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>server</strong></span> <em class="replaceable"><code>ip_addr[/prefixlen]</code></em> {
[<span class="optional"> bogus <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> queryport-pool-updateinterval <em class="replaceable"><code>number</code></em>; </span>]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="server_statement_definition_and_usage"></a><span><strong class="command">server</strong></span> Statement Definition and
+<a name="server_statement_definition_and_usage"></a><span class="command"><strong>server</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">server</strong></span> statement defines
+
+
+ <p>
+ The <span class="command"><strong>server</strong></span> statement defines
characteristics
to be associated with a remote name server. If a prefix length is
specified, then a range of servers is covered. Only the most
server clause applies regardless of the order in
<code class="filename">named.conf</code>.
</p>
-<p>
- The <span><strong class="command">server</strong></span> statement can occur at
+
+ <p>
+ The <span class="command"><strong>server</strong></span> statement can occur at
the top level of the
- configuration file or inside a <span><strong class="command">view</strong></span>
+ configuration file or inside a <span class="command"><strong>view</strong></span>
statement.
- If a <span><strong class="command">view</strong></span> statement contains
- one or more <span><strong class="command">server</strong></span> statements, only
+ If a <span class="command"><strong>view</strong></span> statement contains
+ one or more <span class="command"><strong>server</strong></span> statements, only
those
apply to the view and any top-level ones are ignored.
- If a view contains no <span><strong class="command">server</strong></span>
+ If a view contains no <span class="command"><strong>server</strong></span>
statements,
- any top-level <span><strong class="command">server</strong></span> statements are
+ any top-level <span class="command"><strong>server</strong></span> statements are
used as
defaults.
</p>
-<p>
+
+ <p>
If you discover that a remote server is giving out bad data,
marking it as bogus will prevent further queries to it. The
default
- value of <span><strong class="command">bogus</strong></span> is <span><strong class="command">no</strong></span>.
+ value of <span class="command"><strong>bogus</strong></span> is <span class="command"><strong>no</strong></span>.
</p>
-<p>
- The <span><strong class="command">provide-ixfr</strong></span> clause determines
+ The <span class="command"><strong>provide-ixfr</strong></span> clause determines
whether
the local server, acting as master, will respond with an
incremental
zone transfer when the given remote server, a slave, requests it.
- If set to <span><strong class="command">yes</strong></span>, incremental transfer
+ If set to <span class="command"><strong>yes</strong></span>, incremental transfer
will be provided
- whenever possible. If set to <span><strong class="command">no</strong></span>,
+ whenever possible. If set to <span class="command"><strong>no</strong></span>,
all transfers
to the remote server will be non-incremental. If not set, the
value
- of the <span><strong class="command">provide-ixfr</strong></span> option in the
+ of the <span class="command"><strong>provide-ixfr</strong></span> option in the
view or
global options block is used as a default.
</p>
-<p>
- The <span><strong class="command">request-ixfr</strong></span> clause determines
+
+ <p>
+ The <span class="command"><strong>request-ixfr</strong></span> clause determines
whether
the local server, acting as a slave, will request incremental zone
transfers from the given remote server, a master. If not set, the
- value of the <span><strong class="command">request-ixfr</strong></span> option in
+ value of the <span class="command"><strong>request-ixfr</strong></span> option in
the view or global options block is used as a default. It may
also be set in the zone block and, if set there, it will
override the global or view setting for that zone.
</p>
-<p>
+
+ <p>
IXFR requests to servers that do not support IXFR will
automatically
fall back to AXFR. Therefore, there is no need to manually list
which servers support IXFR and which ones do not; the global
default
- of <span><strong class="command">yes</strong></span> should always work.
- The purpose of the <span><strong class="command">provide-ixfr</strong></span> and
- <span><strong class="command">request-ixfr</strong></span> clauses is
+ of <span class="command"><strong>yes</strong></span> should always work.
+ The purpose of the <span class="command"><strong>provide-ixfr</strong></span> and
+ <span class="command"><strong>request-ixfr</strong></span> clauses is
to make it possible to disable the use of IXFR even when both
master
and slave claim to support it, for example if one of the servers
is buggy and crashes or corrupts data when IXFR is used.
</p>
-<p>
- The <span><strong class="command">request-expire</strong></span> clause determines
+
+ <p>
+ The <span class="command"><strong>request-expire</strong></span> clause determines
whether the local server, when acting as a slave, will
request the EDNS EXPIRE value. The EDNS EXPIRE value
indicates the remaining time before the zone data will
secondary server; when transferring from the primary, the
expiration timer is set from the EXPIRE field of the SOA
record instead.
- The default is <span><strong class="command">yes</strong></span>.
+ The default is <span class="command"><strong>yes</strong></span>.
</p>
-<p>
- The <span><strong class="command">edns</strong></span> clause determines whether
+
+ <p>
+ The <span class="command"><strong>edns</strong></span> clause determines whether
the local server will attempt to use EDNS when communicating
- with the remote server. The default is <span><strong class="command">yes</strong></span>.
+ with the remote server. The default is <span class="command"><strong>yes</strong></span>.
</p>
-<p>
- The <span><strong class="command">edns-udp-size</strong></span> option sets the
- EDNS UDP size that is advertised by <span><strong class="command">named</strong></span>
+
+ <p>
+ The <span class="command"><strong>edns-udp-size</strong></span> option sets the
+ EDNS UDP size that is advertised by <span class="command"><strong>named</strong></span>
when querying the remote server. Valid values are 512
to 4096 bytes (values outside this range will be silently
adjusted to the nearest value within it). This option
for example, when there is a firewall at the remote
site that is blocking large replies. (Note: Currently,
this sets a single UDP size for all packets sent to the
- server; <span><strong class="command">named</strong></span> will not deviate from
+ server; <span class="command"><strong>named</strong></span> will not deviate from
this value. This differs from the behavior of
- <span><strong class="command">edns-udp-size</strong></span> in <span><strong class="command">options</strong></span>
- or <span><strong class="command">view</strong></span> statements, where it specifies
- a maximum value. The <span><strong class="command">server</strong></span> statement
+ <span class="command"><strong>edns-udp-size</strong></span> in <span class="command"><strong>options</strong></span>
+ or <span class="command"><strong>view</strong></span> statements, where it specifies
+ a maximum value. The <span class="command"><strong>server</strong></span> statement
behavior may be brought into conformance with the
- <span><strong class="command">options/view</strong></span> behavior in future releases.)
+ <span class="command"><strong>options/view</strong></span> behavior in future releases.)
</p>
-<p>
- The <span><strong class="command">edns-version</strong></span> option sets the
+
+ <p>
+ The <span class="command"><strong>edns-version</strong></span> option sets the
maximum EDNS VERSION that will be sent to the server(s)
by the resolver. The actual EDNS version sent is still
subject to normal EDNS version negotiation rules (see
adjusted. This option will not be needed until higher
EDNS versions than 0 are in use.
</p>
-<p>
- The <span><strong class="command">max-udp-size</strong></span> option sets the
- maximum EDNS UDP message size <span><strong class="command">named</strong></span>
+
+ <p>
+ The <span class="command"><strong>max-udp-size</strong></span> option sets the
+ maximum EDNS UDP message size <span class="command"><strong>named</strong></span>
will send. Valid values are 512 to 4096 bytes (values
outside this range will be silently adjusted). This
option is useful when you know that there is a firewall
- that is blocking large replies from <span><strong class="command">named</strong></span>.
+ that is blocking large replies from <span class="command"><strong>named</strong></span>.
</p>
-<p>
- The <span><strong class="command">tcp-only</strong></span> option sets the transport
+
+ <p>
+ The <span class="command"><strong>tcp-only</strong></span> option sets the transport
protocol to TCP. The default is to use the UDP transport
and to fallback on TCP only when a truncated response
is received.
</p>
-<p>
- The server supports two zone transfer methods. The first, <span><strong class="command">one-answer</strong></span>,
- uses one DNS message per resource record transferred. <span><strong class="command">many-answers</strong></span> packs
- as many resource records as possible into a message. <span><strong class="command">many-answers</strong></span> is
+
+ <p>
+ The server supports two zone transfer methods. The first, <span class="command"><strong>one-answer</strong></span>,
+ uses one DNS message per resource record transferred. <span class="command"><strong>many-answers</strong></span> packs
+ as many resource records as possible into a message. <span class="command"><strong>many-answers</strong></span> is
more efficient, but is only known to be understood by <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym>
8.x, and patched versions of <acronym class="acronym">BIND</acronym>
4.9.5. You can specify which method
- to use for a server with the <span><strong class="command">transfer-format</strong></span> option.
- If <span><strong class="command">transfer-format</strong></span> is not
- specified, the <span><strong class="command">transfer-format</strong></span>
+ to use for a server with the <span class="command"><strong>transfer-format</strong></span> option.
+ If <span class="command"><strong>transfer-format</strong></span> is not
+ specified, the <span class="command"><strong>transfer-format</strong></span>
specified
- by the <span><strong class="command">options</strong></span> statement will be
+ by the <span class="command"><strong>options</strong></span> statement will be
used.
</p>
-<p><span><strong class="command">transfers</strong></span>
+
+ <p><span class="command"><strong>transfers</strong></span>
is used to limit the number of concurrent inbound zone
transfers from the specified server. If no
- <span><strong class="command">transfers</strong></span> clause is specified, the
+ <span class="command"><strong>transfers</strong></span> clause is specified, the
limit is set according to the
- <span><strong class="command">transfers-per-ns</strong></span> option.
+ <span class="command"><strong>transfers-per-ns</strong></span> option.
</p>
-<p>
- The <span><strong class="command">keys</strong></span> clause identifies a
- <span><strong class="command">key_id</strong></span> defined by the <span><strong class="command">key</strong></span> statement,
- to be used for transaction security (TSIG, <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>)
+
+ <p>
+ The <span class="command"><strong>keys</strong></span> clause identifies a
+ <span class="command"><strong>key_id</strong></span> defined by the <span class="command"><strong>key</strong></span> statement,
+ to be used for transaction security (TSIG, <a class="xref" href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>)
when talking to the remote server.
When a request is sent to the remote server, a request signature
will be generated using the key specified here and appended to the
required
to be signed by this key.
</p>
-<p>
+
+ <p>
Only a single key per server is currently supported.
</p>
-<p>
- The <span><strong class="command">transfer-source</strong></span> and
- <span><strong class="command">transfer-source-v6</strong></span> clauses specify
+
+ <p>
+ The <span class="command"><strong>transfer-source</strong></span> and
+ <span class="command"><strong>transfer-source-v6</strong></span> clauses specify
the IPv4 and IPv6 source
address to be used for zone transfer with the remote server,
respectively.
- For an IPv4 remote server, only <span><strong class="command">transfer-source</strong></span> can
+ For an IPv4 remote server, only <span class="command"><strong>transfer-source</strong></span> can
be specified.
Similarly, for an IPv6 remote server, only
- <span><strong class="command">transfer-source-v6</strong></span> can be
+ <span class="command"><strong>transfer-source-v6</strong></span> can be
specified.
For more details, see the description of
- <span><strong class="command">transfer-source</strong></span> and
- <span><strong class="command">transfer-source-v6</strong></span> in
- <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ <span class="command"><strong>transfer-source</strong></span> and
+ <span class="command"><strong>transfer-source-v6</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
</p>
-<p>
- The <span><strong class="command">notify-source</strong></span> and
- <span><strong class="command">notify-source-v6</strong></span> clauses specify the
+
+ <p>
+ The <span class="command"><strong>notify-source</strong></span> and
+ <span class="command"><strong>notify-source-v6</strong></span> clauses specify the
IPv4 and IPv6 source address to be used for notify
messages sent to remote servers, respectively. For an
- IPv4 remote server, only <span><strong class="command">notify-source</strong></span>
+ IPv4 remote server, only <span class="command"><strong>notify-source</strong></span>
can be specified. Similarly, for an IPv6 remote server,
- only <span><strong class="command">notify-source-v6</strong></span> can be specified.
+ only <span class="command"><strong>notify-source-v6</strong></span> can be specified.
</p>
-<p>
- The <span><strong class="command">query-source</strong></span> and
- <span><strong class="command">query-source-v6</strong></span> clauses specify the
+
+ <p>
+ The <span class="command"><strong>query-source</strong></span> and
+ <span class="command"><strong>query-source-v6</strong></span> clauses specify the
IPv4 and IPv6 source address to be used for queries
sent to remote servers, respectively. For an IPv4
- remote server, only <span><strong class="command">query-source</strong></span> can
+ remote server, only <span class="command"><strong>query-source</strong></span> can
be specified. Similarly, for an IPv6 remote server,
- only <span><strong class="command">query-source-v6</strong></span> can be specified.
+ only <span class="command"><strong>query-source-v6</strong></span> can be specified.
</p>
-<p>
- The <span><strong class="command">request-nsid</strong></span> clause determines
+
+ <p>
+ The <span class="command"><strong>request-nsid</strong></span> clause determines
whether the local server will add a NSID EDNS option
to requests sent to the server. This overrides
- <span><strong class="command">request-nsid</strong></span> set at the view or
+ <span class="command"><strong>request-nsid</strong></span> set at the view or
option level.
</p>
-<p>
- The <span><strong class="command">send-cookie</strong></span> clause determines
+
+ <p>
+ The <span class="command"><strong>send-cookie</strong></span> clause determines
whether the local server will add a COOKIE EDNS option
to requests sent to the server. This overrides
- <span><strong class="command">send-cookie</strong></span> set at the view or
- option level. The <span><strong class="command">named</strong></span> server may
+ <span class="command"><strong>send-cookie</strong></span> set at the view or
+ option level. The <span class="command"><strong>named</strong></span> server may
determine that COOKIE is not supported by the remote server
and not add a COOKIE EDNS option to requests.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="statschannels"></a><span><strong class="command">statistics-channels</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">statistics-channels</strong></span> {
+<a name="statschannels"></a><span class="command"><strong>statistics-channels</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>statistics-channels</strong></span> {
[ inet ( ip_addr | * ) [ port ip_port ]
[ allow { <em class="replaceable"><code> address_match_list </code></em> } ]; ]
[ inet ...; ]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2592781"></a><span><strong class="command">statistics-channels</strong></span> Statement Definition and
+<a name="id-1.7.6.26"></a><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">statistics-channels</strong></span> statement
+
+
+ <p>
+ The <span class="command"><strong>statistics-channels</strong></span> statement
declares communication channels to be used by system
administrators to get access to statistics information of
the name server.
</p>
-<p>
+
+ <p>
This statement intends to be flexible to support multiple
communication protocols in the future, but currently only
HTTP access is supported.
It requires that BIND 9 be compiled with libxml2 and/or
json-c (also known as libjson0); the
- <span><strong class="command">statistics-channels</strong></span> statement is
+ <span class="command"><strong>statistics-channels</strong></span> statement is
still accepted even if it is built without the library,
but any HTTP access will fail with an error.
</p>
-<p>
- An <span><strong class="command">inet</strong></span> control channel is a TCP socket
- listening at the specified <span><strong class="command">ip_port</strong></span> on the
- specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6
- address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code>
+
+ <p>
+ An <span class="command"><strong>inet</strong></span> control channel is a TCP socket
+ listening at the specified <span class="command"><strong>ip_port</strong></span> on the
+ specified <span class="command"><strong>ip_addr</strong></span>, which can be an IPv4 or IPv6
+ address. An <span class="command"><strong>ip_addr</strong></span> of <code class="literal">*</code>
(asterisk) is
interpreted as the IPv4 wildcard address; connections will be
accepted on any of the system's IPv4 addresses.
To listen on the IPv6 wildcard address,
- use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>.
+ use an <span class="command"><strong>ip_addr</strong></span> of <code class="literal">::</code>.
</p>
-<p>
+
+ <p>
If no port is specified, port 80 is used for HTTP channels.
The asterisk "<code class="literal">*</code>" cannot be used for
- <span><strong class="command">ip_port</strong></span>.
+ <span class="command"><strong>ip_port</strong></span>.
</p>
-<p>
+
+ <p>
The attempt of opening a statistics channel is
- restricted by the optional <span><strong class="command">allow</strong></span> clause.
+ restricted by the optional <span class="command"><strong>allow</strong></span> clause.
Connections to the statistics channel are permitted based on the
- <span><strong class="command">address_match_list</strong></span>.
- If no <span><strong class="command">allow</strong></span> clause is present,
- <span><strong class="command">named</strong></span> accepts connection
+ <span class="command"><strong>address_match_list</strong></span>.
+ If no <span class="command"><strong>allow</strong></span> clause is present,
+ <span class="command"><strong>named</strong></span> accepts connection
attempts from any address; since the statistics may
contain sensitive internal information, it is highly
recommended to restrict the source of connection requests
appropriately.
</p>
-<p>
- If no <span><strong class="command">statistics-channels</strong></span> statement is present,
- <span><strong class="command">named</strong></span> will not open any communication channels.
+
+ <p>
+ If no <span class="command"><strong>statistics-channels</strong></span> statement is present,
+ <span class="command"><strong>named</strong></span> will not open any communication channels.
</p>
-<p>
+
+ <p>
The statistics are available in various formats and views
depending on the URI used to access them. For example, if
the statistics channel is configured to listen on 127.0.0.1
port 8888, then the statistics are accessible in XML format at
- <a href="http://127.0.0.1:8888/" target="_top">http://127.0.0.1:8888/</a> or
- <a href="http://127.0.0.1:8888/xml" target="_top">http://127.0.0.1:8888/xml</a>. A CSS file is
+ <a class="ulink" href="http://127.0.0.1:8888/" target="_top">http://127.0.0.1:8888/</a> or
+ <a class="ulink" href="http://127.0.0.1:8888/xml" target="_top">http://127.0.0.1:8888/xml</a>. A CSS file is
included which can format the XML statistics into tables
when viewed with a stylesheet-capable browser, and into
charts and graphs using the Google Charts API when using a
javascript-capable browser.
</p>
-<p>
+
+ <p>
Applications that depend on a particular XML schema
can request
- <a href="http://127.0.0.1:8888/xml/v2" target="_top">http://127.0.0.1:8888/xml/v2</a> for version 2
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v2" target="_top">http://127.0.0.1:8888/xml/v2</a> for version 2
of the statistics XML schema or
- <a href="http://127.0.0.1:8888/xml/v3" target="_top">http://127.0.0.1:8888/xml/v3</a> for version 3.
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3" target="_top">http://127.0.0.1:8888/xml/v3</a> for version 3.
If the requested schema is supported by the server, then
it will respond; if not, it will return a "page not found"
error.
</p>
-<p>
+
+ <p>
Broken-out subsets of the statistics can be viewed at
- <a href="http://127.0.0.1:8888/xml/v3/status" target="_top">http://127.0.0.1:8888/xml/v3/status</a>
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3/status" target="_top">http://127.0.0.1:8888/xml/v3/status</a>
(server uptime and last reconfiguration time),
- <a href="http://127.0.0.1:8888/xml/v3/server" target="_top">http://127.0.0.1:8888/xml/v3/server</a>
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3/server" target="_top">http://127.0.0.1:8888/xml/v3/server</a>
(server and resolver statistics),
- <a href="http://127.0.0.1:8888/xml/v3/zones" target="_top">http://127.0.0.1:8888/xml/v3/zones</a>
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3/zones" target="_top">http://127.0.0.1:8888/xml/v3/zones</a>
(zone statistics),
- <a href="http://127.0.0.1:8888/xml/v3/net" target="_top">http://127.0.0.1:8888/xml/v3/net</a>
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3/net" target="_top">http://127.0.0.1:8888/xml/v3/net</a>
(network status and socket statistics),
- <a href="http://127.0.0.1:8888/xml/v3/mem" target="_top">http://127.0.0.1:8888/xml/v3/mem</a>
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3/mem" target="_top">http://127.0.0.1:8888/xml/v3/mem</a>
(memory manager statistics),
- <a href="http://127.0.0.1:8888/xml/v3/tasks" target="_top">http://127.0.0.1:8888/xml/v3/tasks</a>
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3/tasks" target="_top">http://127.0.0.1:8888/xml/v3/tasks</a>
(task manager statistics), and
- <a href="http://127.0.0.1:8888/xml/v3/traffic" target="_top">http://127.0.0.1:8888/xml/v3/traffic</a>
+ <a class="ulink" href="http://127.0.0.1:8888/xml/v3/traffic" target="_top">http://127.0.0.1:8888/xml/v3/traffic</a>
(traffic sizes).
</p>
-<p>
+
+ <p>
The full set of statistics can also be read in JSON format at
- <a href="http://127.0.0.1:8888/json" target="_top">http://127.0.0.1:8888/json</a>,
+ <a class="ulink" href="http://127.0.0.1:8888/json" target="_top">http://127.0.0.1:8888/json</a>,
with the broken-out subsets at
- <a href="http://127.0.0.1:8888/json/v1/status" target="_top">http://127.0.0.1:8888/json/v1/status</a>
+ <a class="ulink" href="http://127.0.0.1:8888/json/v1/status" target="_top">http://127.0.0.1:8888/json/v1/status</a>
(server uptime and last reconfiguration time),
- <a href="http://127.0.0.1:8888/json/v1/server" target="_top">http://127.0.0.1:8888/json/v1/server</a>
+ <a class="ulink" href="http://127.0.0.1:8888/json/v1/server" target="_top">http://127.0.0.1:8888/json/v1/server</a>
(server and resolver statistics),
- <a href="http://127.0.0.1:8888/json/v1/zones" target="_top">http://127.0.0.1:8888/json/v1/zones</a>
+ <a class="ulink" href="http://127.0.0.1:8888/json/v1/zones" target="_top">http://127.0.0.1:8888/json/v1/zones</a>
(zone statistics),
- <a href="http://127.0.0.1:8888/json/v1/net" target="_top">http://127.0.0.1:8888/json/v1/net</a>
+ <a class="ulink" href="http://127.0.0.1:8888/json/v1/net" target="_top">http://127.0.0.1:8888/json/v1/net</a>
(network status and socket statistics),
- <a href="http://127.0.0.1:8888/json/v1/mem" target="_top">http://127.0.0.1:8888/json/v1/mem</a>
+ <a class="ulink" href="http://127.0.0.1:8888/json/v1/mem" target="_top">http://127.0.0.1:8888/json/v1/mem</a>
(memory manager statistics),
- <a href="http://127.0.0.1:8888/json/v1/tasks" target="_top">http://127.0.0.1:8888/json/v1/tasks</a>
+ <a class="ulink" href="http://127.0.0.1:8888/json/v1/tasks" target="_top">http://127.0.0.1:8888/json/v1/tasks</a>
(task manager statistics), and
- <a href="http://127.0.0.1:8888/json/v1/traffic" target="_top">http://127.0.0.1:8888/json/v1/traffic</a>
+ <a class="ulink" href="http://127.0.0.1:8888/json/v1/traffic" target="_top">http://127.0.0.1:8888/json/v1/traffic</a>
(traffic sizes).
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="trusted-keys"></a><span><strong class="command">trusted-keys</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">trusted-keys</strong></span> {
+<a name="trusted-keys"></a><span class="command"><strong>trusted-keys</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>trusted-keys</strong></span> {
<em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ;
[<span class="optional"> <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; [<span class="optional">...</span>]</span>]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2593147"></a><span><strong class="command">trusted-keys</strong></span> Statement Definition
+<a name="id-1.7.6.28"></a><span class="command"><strong>trusted-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">trusted-keys</strong></span> statement defines
- DNSSEC security roots. DNSSEC is described in <a href="Bv9ARM.ch04.html#DNSSEC" title="DNSSEC">the section called “DNSSEC”</a>. A security root is defined when the
+
+ <p>
+ The <span class="command"><strong>trusted-keys</strong></span> statement defines
+ DNSSEC security roots. DNSSEC is described in <a class="xref" href="Bv9ARM.ch04.html#DNSSEC" title="DNSSEC">the section called “DNSSEC”</a>. A security root is defined when the
public key for a non-authoritative zone is known, but
cannot be securely obtained through DNS, either because
it is the DNS root zone or because its parent zone is
proven secure. The resolver attempts DNSSEC validation
on all DNS data in subdomains of a security root.
</p>
-<p>
All keys (and corresponding zones) listed in
- <span><strong class="command">trusted-keys</strong></span> are deemed to exist regardless
+ <span class="command"><strong>trusted-keys</strong></span> are deemed to exist regardless
of what parent zones say. Similarly for all keys listed in
- <span><strong class="command">trusted-keys</strong></span> only those keys are
+ <span class="command"><strong>trusted-keys</strong></span> only those keys are
used to validate the DNSKEY RRset. The parent's DS RRset
will not be used.
</p>
-<p>
- The <span><strong class="command">trusted-keys</strong></span> statement can contain
+ The <span class="command"><strong>trusted-keys</strong></span> statement can contain
multiple key entries, each consisting of the key's
domain name, flags, protocol, algorithm, and the Base-64
representation of the key data.
in the key data, so the configuration may be split up into
multiple lines.
</p>
-<p>
- <span><strong class="command">trusted-keys</strong></span> may be set at the top level
+ <span class="command"><strong>trusted-keys</strong></span> may be set at the top level
of <code class="filename">named.conf</code> or within a view. If it is
set in both places, they are additive: keys defined at the top
level are inherited by all views, but keys defined in a view
are only used within that view.
</p>
-<p>
Validation below specified names can be temporarily disabled
- by using <span><strong class="command">rndc nta</strong></span>.
+ by using <span class="command"><strong>rndc nta</strong></span>.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2593269"></a><span><strong class="command">managed-keys</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">managed-keys</strong></span> {
+<a name="id-1.7.6.29"></a><span class="command"><strong>managed-keys</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>managed-keys</strong></span> {
<em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ;
[<span class="optional"> <em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ; [<span class="optional">...</span>]</span>]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="managed-keys"></a><span><strong class="command">managed-keys</strong></span> Statement Definition
+<a name="managed-keys"></a><span class="command"><strong>managed-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">managed-keys</strong></span> statement, like
- <span><strong class="command">trusted-keys</strong></span>, defines DNSSEC
+
+ <p>
+ The <span class="command"><strong>managed-keys</strong></span> statement, like
+ <span class="command"><strong>trusted-keys</strong></span>, defines DNSSEC
security roots. The difference is that
- <span><strong class="command">managed-keys</strong></span> can be kept up to date
+ <span class="command"><strong>managed-keys</strong></span> can be kept up to date
automatically, without intervention from the resolver
operator.
</p>
-<p>
Suppose, for example, that a zone's key-signing
key was compromised, and the zone owner had to revoke and
replace the key. A resolver which had the old key in a
- <span><strong class="command">trusted-keys</strong></span> statement would be
+ <span class="command"><strong>trusted-keys</strong></span> statement would be
unable to validate this zone any longer; it would
reply with a SERVFAIL response code. This would
continue until the resolver operator had updated the
- <span><strong class="command">trusted-keys</strong></span> statement with the new key.
+ <span class="command"><strong>trusted-keys</strong></span> statement with the new key.
</p>
-<p>
If, however, the zone were listed in a
- <span><strong class="command">managed-keys</strong></span> statement instead, then the
+ <span class="command"><strong>managed-keys</strong></span> statement instead, then the
zone owner could add a "stand-by" key to the zone in advance.
- <span><strong class="command">named</strong></span> would store the stand-by key, and
- when the original key was revoked, <span><strong class="command">named</strong></span>
+ <span class="command"><strong>named</strong></span> would store the stand-by key, and
+ when the original key was revoked, <span class="command"><strong>named</strong></span>
would be able to transition smoothly to the new key. It would
also recognize that the old key had been revoked, and cease
using that key to validate answers, minimizing the damage that
the compromised key could do.
</p>
-<p>
- A <span><strong class="command">managed-keys</strong></span> statement contains a list of
+ A <span class="command"><strong>managed-keys</strong></span> statement contains a list of
the keys to be managed, along with information about how the
keys are to be initialized for the first time. The only
initialization method currently supported (as of
<acronym class="acronym">BIND</acronym> 9.7.0) is <code class="literal">initial-key</code>.
- This means the <span><strong class="command">managed-keys</strong></span> statement must
+ This means the <span class="command"><strong>managed-keys</strong></span> statement must
contain a copy of the initializing key. (Future releases may
allow keys to be initialized by other methods, eliminating this
requirement.)
</p>
-<p>
- Consequently, a <span><strong class="command">managed-keys</strong></span> statement
- appears similar to a <span><strong class="command">trusted-keys</strong></span>, differing
+ Consequently, a <span class="command"><strong>managed-keys</strong></span> statement
+ appears similar to a <span class="command"><strong>trusted-keys</strong></span>, differing
in the presence of the second field, containing the keyword
<code class="literal">initial-key</code>. The difference is, whereas the
- keys listed in a <span><strong class="command">trusted-keys</strong></span> continue to be
+ keys listed in a <span class="command"><strong>trusted-keys</strong></span> continue to be
trusted until they are removed from
<code class="filename">named.conf</code>, an initializing key listed
- in a <span><strong class="command">managed-keys</strong></span> statement is only trusted
+ in a <span class="command"><strong>managed-keys</strong></span> statement is only trusted
<span class="emphasis"><em>once</em></span>: for as long as it takes to load the
managed key database and start the RFC 5011 key maintenance
process.
</p>
-<p>
- The first time <span><strong class="command">named</strong></span> runs with a managed key
+ The first time <span class="command"><strong>named</strong></span> runs with a managed key
configured in <code class="filename">named.conf</code>, it fetches the
DNSKEY RRset directly from the zone apex, and validates it
- using the key specified in the <span><strong class="command">managed-keys</strong></span>
+ using the key specified in the <span class="command"><strong>managed-keys</strong></span>
statement. If the DNSKEY RRset is validly signed, then it is
used as the basis for a new managed keys database.
</p>
-<p>
- From that point on, whenever <span><strong class="command">named</strong></span> runs, it
- sees the <span><strong class="command">managed-keys</strong></span> statement, checks to
+ From that point on, whenever <span class="command"><strong>named</strong></span> runs, it
+ sees the <span class="command"><strong>managed-keys</strong></span> statement, checks to
make sure RFC 5011 key maintenance has already been initialized
for the specified domain, and if so, it simply moves on. The
- key specified in the <span><strong class="command">managed-keys</strong></span> is not
+ key specified in the <span class="command"><strong>managed-keys</strong></span> is not
used to validate answers; it has been superseded by the key or
keys stored in the managed keys database.
</p>
-<p>
- The next time <span><strong class="command">named</strong></span> runs after a name
+ The next time <span class="command"><strong>named</strong></span> runs after a name
has been <span class="emphasis"><em>removed</em></span> from the
- <span><strong class="command">managed-keys</strong></span> statement, the corresponding
+ <span class="command"><strong>managed-keys</strong></span> statement, the corresponding
zone will be removed from the managed keys database,
and RFC 5011 key maintenance will no longer be used for that
domain.
</p>
-<p>
- <span><strong class="command">named</strong></span> only maintains a single managed keys
- database; consequently, unlike <span><strong class="command">trusted-keys</strong></span>,
- <span><strong class="command">managed-keys</strong></span> may only be set at the top
+ <span class="command"><strong>named</strong></span> only maintains a single managed keys
+ database; consequently, unlike <span class="command"><strong>trusted-keys</strong></span>,
+ <span class="command"><strong>managed-keys</strong></span> may only be set at the top
level of <code class="filename">named.conf</code>, not within a view.
</p>
-<p>
In the current implementation, the managed keys database is
stored as a master-format zone file called
<code class="filename">managed-keys.bind</code>. When the key database
<code class="filename">managed-keys.bind.jnl</code>. They are committed
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
+ seconds. So, whenever <span class="command"><strong>named</strong></span> is using
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>.)
+ <span class="command"><strong>named</strong></span>.)
</p>
-<p>
- If the <span><strong class="command">dnssec-validation</strong></span> option is
- set to <strong class="userinput"><code>auto</code></strong>, <span><strong class="command">named</strong></span>
+ If the <span class="command"><strong>dnssec-validation</strong></span> option is
+ set to <strong class="userinput"><code>auto</code></strong>, <span class="command"><strong>named</strong></span>
will automatically initialize a managed key for the
- root zone. Similarly, if the <span><strong class="command">dnssec-lookaside</strong></span>
+ root zone. Similarly, if the <span class="command"><strong>dnssec-lookaside</strong></span>
option is set to <strong class="userinput"><code>auto</code></strong>,
- <span><strong class="command">named</strong></span> will automatically initialize
+ <span class="command"><strong>named</strong></span> will automatically initialize
a managed key for the zone <code class="literal">dlv.isc.org</code>.
In both cases, the key that is used to initialize the key
- maintenance process is built into <span><strong class="command">named</strong></span>,
- and can be overridden from <span><strong class="command">bindkeys-file</strong></span>.
+ maintenance process is built into <span class="command"><strong>named</strong></span>,
+ and can be overridden from <span class="command"><strong>bindkeys-file</strong></span>.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="view_statement_grammar"></a><span><strong class="command">view</strong></span> Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">view</strong></span> <em class="replaceable"><code>view_name</code></em>
+<a name="view_statement_grammar"></a><span class="command"><strong>view</strong></span> Statement Grammar</h3></div></div></div>
+
+
+<pre class="programlisting"><span class="command"><strong>view</strong></span> <em class="replaceable"><code>view_name</code></em>
[<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
match-clients { <em class="replaceable"><code>address_match_list</code></em> };
match-destinations { <em class="replaceable"><code>address_match_list</code></em> };
[<span class="optional"> <em class="replaceable"><code>zone_statement</code></em>; ...</span>]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2593704"></a><span><strong class="command">view</strong></span> Statement Definition and Usage</h3></div></div></div>
-<p>
- The <span><strong class="command">view</strong></span> statement is a powerful
+<a name="id-1.7.6.32"></a><span class="command"><strong>view</strong></span> Statement Definition and Usage</h3></div></div></div>
+
+
+ <p>
+ The <span class="command"><strong>view</strong></span> statement is a powerful
feature
of <acronym class="acronym">BIND</acronym> 9 that lets a name server
answer a DNS query differently
implementing
split DNS setups without having to run multiple servers.
</p>
-<p>
- Each <span><strong class="command">view</strong></span> statement defines a view
+
+ <p>
+ Each <span class="command"><strong>view</strong></span> statement defines a view
of the
DNS namespace that will be seen by a subset of clients. A client
matches
a view if its source IP address matches the
<code class="varname">address_match_list</code> of the view's
- <span><strong class="command">match-clients</strong></span> clause and its
+ <span class="command"><strong>match-clients</strong></span> clause and its
destination IP address matches
the <code class="varname">address_match_list</code> of the
view's
- <span><strong class="command">match-destinations</strong></span> clause. If not
+ <span class="command"><strong>match-destinations</strong></span> clause. If not
specified, both
- <span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span>
+ <span class="command"><strong>match-clients</strong></span> and <span class="command"><strong>match-destinations</strong></span>
default to matching all addresses. In addition to checking IP
addresses
- <span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span>
- can also take <span><strong class="command">keys</strong></span> which provide an
+ <span class="command"><strong>match-clients</strong></span> and <span class="command"><strong>match-destinations</strong></span>
+ can also take <span class="command"><strong>keys</strong></span> which provide an
mechanism for the
client to select the view. A view can also be specified
- as <span><strong class="command">match-recursive-only</strong></span>, which
+ as <span class="command"><strong>match-recursive-only</strong></span>, which
means that only recursive
requests from matching clients will match that view.
- The order of the <span><strong class="command">view</strong></span> statements is
+ The order of the <span class="command"><strong>view</strong></span> statements is
significant —
a client request will be resolved in the context of the first
- <span><strong class="command">view</strong></span> that it matches.
+ <span class="command"><strong>view</strong></span> that it matches.
</p>
-<p>
- Zones defined within a <span><strong class="command">view</strong></span>
+
+ <p>
+ Zones defined within a <span class="command"><strong>view</strong></span>
statement will
- only be accessible to clients that match the <span><strong class="command">view</strong></span>.
+ only be accessible to clients that match the <span class="command"><strong>view</strong></span>.
By defining a zone of the same name in multiple views, different
zone data can be given to different clients, for example,
"internal"
and "external" clients in a split DNS setup.
</p>
-<p>
- Many of the options given in the <span><strong class="command">options</strong></span> statement
- can also be used within a <span><strong class="command">view</strong></span>
+
+ <p>
+ Many of the options given in the <span class="command"><strong>options</strong></span> statement
+ can also be used within a <span class="command"><strong>view</strong></span>
statement, and then
apply only when resolving queries with that view. When no
view-specific
- value is given, the value in the <span><strong class="command">options</strong></span> statement
+ value is given, the value in the <span class="command"><strong>options</strong></span> statement
is used as a default. Also, zone options can have default values
specified
- in the <span><strong class="command">view</strong></span> statement; these
+ in the <span class="command"><strong>view</strong></span> statement; these
view-specific defaults
- take precedence over those in the <span><strong class="command">options</strong></span> statement.
+ take precedence over those in the <span class="command"><strong>options</strong></span> statement.
</p>
-<p>
+
+ <p>
Views are class specific. If no class is given, class IN
is assumed. Note that all non-IN views must contain a hint zone,
since only the IN class has compiled-in default hints.
</p>
-<p>
- If there are no <span><strong class="command">view</strong></span> statements in
+
+ <p>
+ If there are no <span class="command"><strong>view</strong></span> statements in
the config
file, a default view that matches any client is automatically
created
- in class IN. Any <span><strong class="command">zone</strong></span> statements
+ in class IN. Any <span class="command"><strong>zone</strong></span> statements
specified on
the top level of the configuration file are considered to be part
of
- this default view, and the <span><strong class="command">options</strong></span>
+ this default view, and the <span class="command"><strong>options</strong></span>
statement will
- apply to the default view. If any explicit <span><strong class="command">view</strong></span>
- statements are present, all <span><strong class="command">zone</strong></span>
+ apply to the default view. If any explicit <span class="command"><strong>view</strong></span>
+ statements are present, all <span class="command"><strong>zone</strong></span>
statements must
- occur inside <span><strong class="command">view</strong></span> statements.
+ occur inside <span class="command"><strong>view</strong></span> statements.
</p>
-<p>
+
+ <p>
Here is an example of a typical split DNS setup implemented
- using <span><strong class="command">view</strong></span> statements:
+ using <span class="command"><strong>view</strong></span> statements:
</p>
+
<pre class="programlisting">view "internal" {
// This should match our internal networks.
match-clients { 10.0.0.0/8; };
};
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="zone_statement_grammar"></a><span><strong class="command">zone</strong></span>
+<a name="zone_statement_grammar"></a><span class="command"><strong>zone</strong></span>
Statement Grammar</h3></div></div></div>
-<pre class="programlisting"><span><strong class="command">zone</strong></span> <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
+
+
+<pre class="programlisting"><span class="command"><strong>zone</strong></span> <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type master;
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
};
</pre>
-</div>
-<div class="sect2" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2595733"></a><span><strong class="command">zone</strong></span> Statement Definition and Usage</h3></div></div></div>
-<div class="sect3" lang="en">
+<a name="id-1.7.6.34"></a><span class="command"><strong>zone</strong></span> Statement Definition and Usage</h3></div></div></div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2595740"></a>Zone Types</h4></div></div></div>
-<p>
- The <span><strong class="command">type</strong></span> keyword is required
- for the <span><strong class="command">zone</strong></span> configuration unless
- it is an <span><strong class="command">in-view</strong></span> configuration. Its
+<a name="id-1.7.6.34.3"></a>Zone Types</h4></div></div></div>
+ The <span class="command"><strong>type</strong></span> keyword is required
+ for the <span class="command"><strong>zone</strong></span> configuration unless
+ it is an <span class="command"><strong>in-view</strong></span> configuration. Its
acceptable values include: <code class="varname">delegation-only</code>,
<code class="varname">forward</code>, <code class="varname">hint</code>,
<code class="varname">master</code>, <code class="varname">redirect</code>,
<code class="varname">slave</code>, <code class="varname">static-stub</code>,
and <code class="varname">stub</code>.
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col class="1">
+<col width="4.017in" class="2">
</colgroup>
<tbody>
<tr>
<td>
<p>
A slave zone is a replica of a master
- zone. The <span><strong class="command">masters</strong></span> list
+ zone. The <span class="command"><strong>masters</strong></span> list
specifies one or more IP addresses
of master servers that the slave contacts to update
its copy of the zone.
</p>
<p>
Zone data is configured via the
- <span><strong class="command">server-addresses</strong></span> and
- <span><strong class="command">server-names</strong></span> zone options.
+ <span class="command"><strong>server-addresses</strong></span> and
+ <span class="command"><strong>server-names</strong></span> zone options.
</p>
<p>
The zone data is maintained in the form of NS
and (if necessary) glue A or AAAA RRs
internally, which can be seen by dumping zone
- databases by <span><strong class="command">rndc dumpdb -all</strong></span>.
+ databases by <span class="command"><strong>rndc dumpdb -all</strong></span>.
The configured RRs are considered local configuration
parameters rather than public data.
Non recursive queries (i.e., those with the RD
<td>
<p>
A "forward zone" is a way to configure
- forwarding on a per-domain basis. A <span><strong class="command">zone</strong></span> statement
- of type <span><strong class="command">forward</strong></span> can
- contain a <span><strong class="command">forward</strong></span>
- and/or <span><strong class="command">forwarders</strong></span>
+ forwarding on a per-domain basis. A <span class="command"><strong>zone</strong></span> statement
+ of type <span class="command"><strong>forward</strong></span> can
+ contain a <span class="command"><strong>forward</strong></span>
+ and/or <span class="command"><strong>forwarders</strong></span>
statement,
which will apply to queries within the domain given by
the zone
- name. If no <span><strong class="command">forwarders</strong></span>
+ name. If no <span class="command"><strong>forwarders</strong></span>
statement is present or
- an empty list for <span><strong class="command">forwarders</strong></span> is given, then no
+ an empty list for <span class="command"><strong>forwarders</strong></span> is given, then no
forwarding will be done for the domain, canceling the
effects of
- any forwarders in the <span><strong class="command">options</strong></span> statement. Thus
+ any forwarders in the <span class="command"><strong>options</strong></span> statement. Thus
if you want to use this type of zone to change the
behavior of the
- global <span><strong class="command">forward</strong></span> option
+ global <span class="command"><strong>forward</strong></span> option
(that is, "forward first"
to, then "forward only", or vice versa, but want to
use the same
queries when normal resolution would result in
NXDOMAIN being returned.
Only one redirect zone is supported
- per view. <span><strong class="command">allow-query</strong></span> can be
+ per view. <span class="command"><strong>allow-query</strong></span> can be
used to restrict which clients see these answers.
</p>
<p>
zone lookup table with normal master and slave
zones. Consequently, it is not currently possible
to use
- <span><strong class="command">rndc reload
+ <span class="command"><strong>rndc reload
<em class="replaceable"><code>zonename</code></em></strong></span>
to reload a redirect zone. However, when using
- <span><strong class="command">rndc reload</strong></span> without specifying
+ <span class="command"><strong>rndc reload</strong></span> without specifying
a zone name, redirect zones will be reloaded along
with other zones.
</p>
effect on answers received from forwarders.
</p>
<p>
- See caveats in <a href="Bv9ARM.ch06.html#root_delegation_only"><span><strong class="command">root-delegation-only</strong></span></a>.
+ See caveats in <a class="xref" href="Bv9ARM.ch06.html#root_delegation_only"><span class="command"><strong>root-delegation-only</strong></span></a>.
</p>
</td>
</tr>
</tbody>
-</table></div>
-</div>
-<div class="sect3" lang="en">
+</table>
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2596458"></a>Class</h4></div></div></div>
-<p>
+<a name="id-1.7.6.34.4"></a>Class</h4></div></div></div>
+
+ <p>
The zone's name may optionally be followed by a class. If
a class is not specified, class <code class="literal">IN</code> (for <code class="varname">Internet</code>),
is assumed. This is correct for the vast majority of cases.
</p>
-<p>
The <code class="literal">hesiod</code> class is
named for an information service from MIT's Project Athena. It
is
<code class="literal">HS</code> is
a synonym for hesiod.
</p>
-<p>
Another MIT development is Chaosnet, a LAN protocol created
in the mid-1970s. Zone data for it can be specified with the <code class="literal">CHAOS</code> class.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2596491"></a>Zone Options</h4></div></div></div>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
-<dd><p>
+<a name="id-1.7.6.34.5"></a>Zone Options</h4></div></div></div>
+
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>allow-notify</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">allow-notify</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>allow-notify</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-query</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">allow-query</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-query-on</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>allow-query</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-query-on</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">allow-query-on</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt>
-<dd><p>
- See the description of <span><strong class="command">allow-transfer</strong></span>
- in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt>
-<dd><p>
- See the description of <span><strong class="command">allow-update</strong></span>
- in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">update-policy</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>allow-query-on</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-transfer</strong></span></span></dt>
+<dd>
+ <p>
+ See the description of <span class="command"><strong>allow-transfer</strong></span>
+ in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-update</strong></span></span></dt>
+<dd>
+ <p>
+ See the description of <span class="command"><strong>allow-update</strong></span>
+ in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>update-policy</strong></span></span></dt>
+<dd>
+ <p>
Specifies a "Simple Secure Update" policy. See
- <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt>
-<dd><p>
- See the description of <span><strong class="command">allow-update-forwarding</strong></span>
- in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt>
-<dd><p>
- Only meaningful if <span><strong class="command">notify</strong></span>
+ <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>allow-update-forwarding</strong></span></span></dt>
+<dd>
+ <p>
+ See the description of <span class="command"><strong>allow-update-forwarding</strong></span>
+ in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>also-notify</strong></span></span></dt>
+<dd>
+ <p>
+ Only meaningful if <span class="command"><strong>notify</strong></span>
is
active for this zone. The set of machines that will
receive a
(other than
the primary master) for the zone plus any IP addresses
specified
- with <span><strong class="command">also-notify</strong></span>. A port
+ with <span class="command"><strong>also-notify</strong></span>. A port
may be specified
- with each <span><strong class="command">also-notify</strong></span>
+ with each <span class="command"><strong>also-notify</strong></span>
address to send the notify
messages to a port other than the default of 53.
A TSIG key may also be specified to cause the
<code class="literal">NOTIFY</code> to be signed by the
given key.
- <span><strong class="command">also-notify</strong></span> is not
+ <span class="command"><strong>also-notify</strong></span> is not
meaningful for stub zones.
The default is the empty list.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-names</strong></span></span></dt>
+<dd>
+ <p>
This option is used to restrict the character set and
syntax of
certain domain names in master files and/or DNS responses
received from the
- network. The default varies according to zone type. For <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>. For <span><strong class="command">slave</strong></span>
- zones the default is <span><strong class="command">warn</strong></span>.
- It is not implemented for <span><strong class="command">hint</strong></span> zones.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt>
-<dd><p>
+ network. The default varies according to zone type. For <span class="command"><strong>master</strong></span> zones the default is <span class="command"><strong>fail</strong></span>. For <span class="command"><strong>slave</strong></span>
+ zones the default is <span class="command"><strong>warn</strong></span>.
+ It is not implemented for <span class="command"><strong>hint</strong></span> zones.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-mx</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">check-mx</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-spf</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>check-mx</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-spf</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">check-spf</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>check-spf</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-wildcard</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">check-wildcard</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>check-wildcard</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-integrity</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">check-integrity</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>check-integrity</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>check-sibling</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">check-sibling</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>check-sibling</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>zero-no-soa-ttl</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">zero-no-soa-ttl</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>zero-no-soa-ttl</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>update-check-ksk</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">update-check-ksk</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnssec-loadkeys-interval</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>update-check-ksk</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-loadkeys-interval</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">dnssec-loadkeys-interval</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ <span class="command"><strong>dnssec-loadkeys-interval</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnssec-update-mode</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-update-mode</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">dnssec-update-mode</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ <span class="command"><strong>dnssec-update-mode</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnssec-dnskey-kskonly</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-dnskey-kskonly</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">dnssec-dnskey-kskonly</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">try-tcp-refresh</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>dnssec-dnskey-kskonly</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>try-tcp-refresh</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">try-tcp-refresh</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">database</strong></span></span></dt>
+ <span class="command"><strong>try-tcp-refresh</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>database</strong></span></span></dt>
<dd>
-<p>
Specify the type of database to be used for storing the
- zone data. The string following the <span><strong class="command">database</strong></span> keyword
+ zone data. The string following the <span class="command"><strong>database</strong></span> keyword
is interpreted as a list of whitespace-delimited words.
The first word
identifies the database type, and any subsequent words are
specific
to the database type.
</p>
-<p>
The default is <strong class="userinput"><code>"rbt"</code></strong>, BIND 9's
native in-memory
red-black-tree database. This database does not take
arguments.
</p>
-<p>
Other values are possible if additional database drivers
have been linked into the server. Some sample drivers are
included
with the distribution but none are linked in by default.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dialup</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">dialup</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">delegation-only</strong></span></span></dt>
+ <span class="command"><strong>dialup</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>delegation-only</strong></span></span></dt>
<dd>
-<p>
The flag only applies to forward, hint and stub
zones. If set to <strong class="userinput"><code>yes</code></strong>,
then the zone will also be treated as if it is
also a delegation-only type zone.
</p>
-<p>
- See caveats in <a href="Bv9ARM.ch06.html#root_delegation_only"><span><strong class="command">root-delegation-only</strong></span></a>.
+ See caveats in <a class="xref" href="Bv9ARM.ch06.html#root_delegation_only"><span class="command"><strong>root-delegation-only</strong></span></a>.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">forward</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>forward</strong></span></span></dt>
+<dd>
+ <p>
Only meaningful if the zone has a forwarders
- list. The <span><strong class="command">only</strong></span> value causes
+ list. The <span class="command"><strong>only</strong></span> value causes
the lookup to fail
- after trying the forwarders and getting no answer, while <span><strong class="command">first</strong></span> would
+ after trying the forwarders and getting no answer, while <span class="command"><strong>first</strong></span> would
allow a normal lookup to be tried.
- </p></dd>
-<dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>forwarders</strong></span></span></dt>
+<dd>
+ <p>
Used to override the list of global forwarders.
- If it is not specified in a zone of type <span><strong class="command">forward</strong></span>,
+ If it is not specified in a zone of type <span class="command"><strong>forward</strong></span>,
no forwarding is done for the zone and the global options are
not used.
- </p></dd>
-<dt><span class="term"><span><strong class="command">ixfr-base</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>ixfr-base</strong></span></span></dt>
+<dd>
+ <p>
Was used in <acronym class="acronym">BIND</acronym> 8 to
specify the name
of the transaction log (journal) file for dynamic update
file by appending "<code class="filename">.jnl</code>"
to the name of the
zone file.
- </p></dd>
-<dt><span class="term"><span><strong class="command">ixfr-tmp-file</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>ixfr-tmp-file</strong></span></span></dt>
+<dd>
+ <p>
Was an undocumented option in <acronym class="acronym">BIND</acronym> 8.
Ignored in <acronym class="acronym">BIND</acronym> 9.
- </p></dd>
-<dt><span class="term"><span><strong class="command">journal</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>journal</strong></span></span></dt>
+<dd>
+ <p>
Allow the default journal's filename to be overridden.
The default is the zone's filename with "<code class="filename">.jnl</code>" appended.
- This is applicable to <span><strong class="command">master</strong></span> and <span><strong class="command">slave</strong></span> zones.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-journal-size</strong></span></span></dt>
-<dd><p>
+ This is applicable to <span class="command"><strong>master</strong></span> and <span class="command"><strong>slave</strong></span> zones.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-journal-size</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">max-journal-size</strong></span> in <a href="Bv9ARM.ch06.html#server_resource_limits" title="Server Resource Limits">the section called “Server Resource Limits”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>max-journal-size</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#server_resource_limits" title="Server Resource Limits">the section called “Server Resource Limits”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-time-in</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">max-transfer-time-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>max-transfer-time-in</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-idle-in</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">max-transfer-idle-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>max-transfer-idle-in</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-time-out</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">max-transfer-time-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>max-transfer-time-out</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-transfer-idle-out</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">max-transfer-idle-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>max-transfer-idle-out</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">notify</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>notify</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-delay</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">notify-delay</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify-to-soa</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>notify-delay</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-to-soa</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">notify-to-soa</strong></span> in
- <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">pubkey</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>notify-to-soa</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>pubkey</strong></span></span></dt>
+<dd>
+ <p>
In <acronym class="acronym">BIND</acronym> 8, this option was
intended for specifying
a public zone key for verification of signatures in DNSSEC
signed
zones when they are loaded from disk. <acronym class="acronym">BIND</acronym> 9 does not verify signatures
on load and ignores the option.
- </p></dd>
-<dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>zone-statistics</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">zone-statistics</strong></span> in
- <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ <span class="command"><strong>zone-statistics</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">server-addresses</strong></span></span></dt>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>server-addresses</strong></span></span></dt>
<dd>
-<p>
Only meaningful for static-stub zones.
This is a list of IP addresses to which queries
should be sent in recursive resolution for the
configure the apex NS RR with associated glue A or
AAAA RRs.
</p>
-<p>
For example, if "example.com" is configured as a
static-stub zone with 192.0.2.1 and 2001:db8::1234
- in a <span><strong class="command">server-addresses</strong></span> option,
+ in a <span class="command"><strong>server-addresses</strong></span> option,
the following RRs will be internally configured.
</p>
<pre class="programlisting">example.com. NS example.com.
example.com. A 192.0.2.1
example.com. AAAA 2001:db8::1234</pre>
-<p>
These records are internally used to resolve
names under the static-stub zone.
For instance, if the server receives a query for
will initiate recursive resolution and send
queries to 192.0.2.1 and/or 2001:db8::1234.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">server-names</strong></span></span></dt>
+ </dd>
+<dt><span class="term"><span class="command"><strong>server-names</strong></span></span></dt>
<dd>
-<p>
Only meaningful for static-stub zones.
This is a list of domain names of nameservers that
act as authoritative servers of the static-stub
zone.
These names will be resolved to IP addresses when
- <span><strong class="command">named</strong></span> needs to send queries to
+ <span class="command"><strong>named</strong></span> needs to send queries to
these servers.
To make this supplemental resolution successful,
these names must not be a subdomain of the origin
That is, when "example.net" is the origin of a
static-stub zone, "ns.example" and
"master.example.com" can be specified in the
- <span><strong class="command">server-names</strong></span> option, but
+ <span class="command"><strong>server-names</strong></span> option, but
"ns.example.net" cannot, and will be rejected by
the configuration parser.
</p>
-<p>
A non empty list for this option will internally
configure the apex NS RR with the specified names.
For example, if "example.com" is configured as a
static-stub zone with "ns1.example.net" and
"ns2.example.net"
- in a <span><strong class="command">server-names</strong></span> option,
+ in a <span class="command"><strong>server-names</strong></span> option,
the following RRs will be internally configured.
</p>
<pre class="programlisting">example.com. NS ns1.example.net.
example.com. NS ns2.example.net.
</pre>
-<p>
These records are internally used to resolve
names under the static-stub zone.
For instance, if the server receives a query for
"ns2.example.net" to IP addresses, and then send
queries to (one or more of) these addresses.
</p>
-</dd>
-<dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt>
-<dd><p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-validity-interval</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">sig-validity-interval</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">sig-signing-nodes</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>sig-validity-interval</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-signing-nodes</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">sig-signing-nodes</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">sig-signing-signatures</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>sig-signing-nodes</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-signing-signatures</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">sig-signing-signatures</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">sig-signing-type</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>sig-signing-signatures</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>sig-signing-type</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">sig-signing-type</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>sig-signing-type</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfer-source</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>transfer-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>transfer-source-v6</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>transfer-source-v6</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>alt-transfer-source</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>alt-transfer-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>alt-transfer-source-v6</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">alt-transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>alt-transfer-source-v6</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>use-alt-transfer-source</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">use-alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>use-alt-transfer-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-source</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">notify-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt>
-<dd><p>
+ <span class="command"><strong>notify-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>notify-source-v6</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">notify-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
- </p></dd>
+ <span class="command"><strong>notify-source-v6</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
+ </p>
+ </dd>
<dt>
-<span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span>
+<span class="term"><span class="command"><strong>min-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>max-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>min-retry-time</strong></span>, </span><span class="term"><span class="command"><strong>max-retry-time</strong></span></span>
</dt>
-<dd><p>
- See the description in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
-<dd><p>
+<dd>
+ <p>
+ See the description in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>ixfr-from-differences</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">ixfr-from-differences</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- (Note that the <span><strong class="command">ixfr-from-differences</strong></span>
+ <span class="command"><strong>ixfr-from-differences</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ (Note that the <span class="command"><strong>ixfr-from-differences</strong></span>
<strong class="userinput"><code>master</code></strong> and
<strong class="userinput"><code>slave</code></strong> choices are not
available at the zone level.)
- </p></dd>
-<dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>key-directory</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">key-directory</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ <span class="command"><strong>key-directory</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">auto-dnssec</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>auto-dnssec</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">auto-dnssec</strong></span> in
- <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ <span class="command"><strong>auto-dnssec</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">serial-update-method</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>serial-update-method</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">serial-update-method</strong></span> in
- <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ <span class="command"><strong>serial-update-method</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">inline-signing</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>inline-signing</strong></span></span></dt>
+<dd>
+ <p>
If <code class="literal">yes</code>, this enables
"bump in the wire" signing of a zone, where a
unsigned zone is transferred in or loaded from
disk and a signed version of the zone is served,
with possibly, a different serial number. This
behaviour is disabled by default.
- </p></dd>
-<dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt>
-<dd><p>
- See the description of <span><strong class="command">multi-master</strong></span> in
- <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt>
-<dd><p>
- See the description of <span><strong class="command">masterfile-format</strong></span>
- in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">max-zone-ttl</strong></span></span></dt>
-<dd><p>
- See the description of <span><strong class="command">max-zone-ttl</strong></span>
- in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>multi-master</strong></span></span></dt>
+<dd>
+ <p>
+ See the description of <span class="command"><strong>multi-master</strong></span> in
+ <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>masterfile-format</strong></span></span></dt>
+<dd>
+ <p>
+ See the description of <span class="command"><strong>masterfile-format</strong></span>
+ in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>max-zone-ttl</strong></span></span></dt>
+<dd>
+ <p>
+ See the description of <span class="command"><strong>max-zone-ttl</strong></span>
+ in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>.
- </p></dd>
-<dt><span class="term"><span><strong class="command">dnssec-secure-to-insecure</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>dnssec-secure-to-insecure</strong></span></span></dt>
+<dd>
+ <p>
See the description of
- <span><strong class="command">dnssec-secure-to-insecure</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
- </p></dd>
+ <span class="command"><strong>dnssec-secure-to-insecure</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="dynamic_update_policies"></a>Dynamic Update Policies</h4></div></div></div>
-<p><acronym class="acronym">BIND</acronym> 9 supports two alternative
+
+ <p><acronym class="acronym">BIND</acronym> 9 supports two alternative
methods of granting clients the right to perform
dynamic updates to a zone, configured by the
- <span><strong class="command">allow-update</strong></span> and
- <span><strong class="command">update-policy</strong></span> option, respectively.
+ <span class="command"><strong>allow-update</strong></span> and
+ <span class="command"><strong>update-policy</strong></span> option, respectively.
</p>
-<p>
- The <span><strong class="command">allow-update</strong></span> clause works the
+ The <span class="command"><strong>allow-update</strong></span> clause works the
same way as in previous versions of <acronym class="acronym">BIND</acronym>.
It grants given clients the permission to update any
record of any name in the zone.
</p>
-<p>
- The <span><strong class="command">update-policy</strong></span> clause
+ The <span class="command"><strong>update-policy</strong></span> clause
allows more fine-grained control over what updates are
allowed. A set of rules is specified, where each rule
either grants or denies permissions for one or more
it includes either a TSIG or SIG(0) record), the
identity of the signer can be determined.
</p>
-<p>
- Rules are specified in the <span><strong class="command">update-policy</strong></span>
+ Rules are specified in the <span class="command"><strong>update-policy</strong></span>
zone option, and are only meaningful for master zones.
- When the <span><strong class="command">update-policy</strong></span> statement
+ When the <span class="command"><strong>update-policy</strong></span> statement
is present, it is a configuration error for the
- <span><strong class="command">allow-update</strong></span> statement to be
- present. The <span><strong class="command">update-policy</strong></span> statement
+ <span class="command"><strong>allow-update</strong></span> statement to be
+ present. The <span class="command"><strong>update-policy</strong></span> statement
only examines the signer of a message; the source
address is not relevant.
</p>
-<p>
- There is a pre-defined <span><strong class="command">update-policy</strong></span>
+ There is a pre-defined <span class="command"><strong>update-policy</strong></span>
rule which can be switched on with the command
- <span><strong class="command">update-policy local;</strong></span>.
+ <span class="command"><strong>update-policy local;</strong></span>.
Switching on this rule in a zone causes
- <span><strong class="command">named</strong></span> to generate a TSIG session
+ <span class="command"><strong>named</strong></span> to generate a TSIG session
key and place it in a file, and to allow that key
to update the zone. (By default, the file is
<code class="filename">/var/run/named/session.key</code>, the key
name is "local-ddns" and the key algorithm is HMAC-SHA256,
but these values are configurable with the
- <span><strong class="command">session-keyfile</strong></span>,
- <span><strong class="command">session-keyname</strong></span> and
- <span><strong class="command">session-keyalg</strong></span> options, respectively).
+ <span class="command"><strong>session-keyfile</strong></span>,
+ <span class="command"><strong>session-keyname</strong></span> and
+ <span class="command"><strong>session-keyalg</strong></span> options, respectively).
</p>
-<p>
A client running on the local system, and with appropriate
permissions, may read that file and use the key to sign update
requests. The zone's update policy will be set to allow that
key to change any record within the zone. Assuming the
key name is "local-ddns", this policy is equivalent to:
</p>
-<pre class="programlisting">update-policy { grant local-ddns zonesub any; };
+
+ <pre class="programlisting">update-policy { grant local-ddns zonesub any; };
</pre>
-<p>
- The command <span><strong class="command">nsupdate -l</strong></span> sends update
+
+ <p>
+ The command <span class="command"><strong>nsupdate -l</strong></span> sends update
requests to localhost, and signs them using the session key.
</p>
-<p>
+
+ <p>
Other rule definitions look like this:
</p>
+
<pre class="programlisting">
-( <span><strong class="command">grant</strong></span> | <span><strong class="command">deny</strong></span> ) <em class="replaceable"><code>identity</code></em> <em class="replaceable"><code>nametype</code></em> [<span class="optional"> <em class="replaceable"><code>name</code></em> </span>] [<span class="optional"> <em class="replaceable"><code>types</code></em> </span>]
+( <span class="command"><strong>grant</strong></span> | <span class="command"><strong>deny</strong></span> ) <em class="replaceable"><code>identity</code></em> <em class="replaceable"><code>nametype</code></em> [<span class="optional"> <em class="replaceable"><code>name</code></em> </span>] [<span class="optional"> <em class="replaceable"><code>types</code></em> </span>]
</pre>
-<p>
+
+ <p>
Each rule grants or denies privileges. Once a message has
successfully matched a rule, the operation is immediately
granted or denied and no further rules are examined. A rule
field, and the type matches the types specified in the type
field.
</p>
-<p>
No signer is required for <em class="replaceable"><code>tcp-self</code></em>
or <em class="replaceable"><code>6to4-self</code></em> however the standard
reverse mapping / prefix conversion must match the identity
field.
</p>
-<p>
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
The <em class="replaceable"><code>identity</code></em> field must
contain a fully-qualified domain name.
</p>
-<p>
For nametypes <code class="varname">krb5-self</code>,
<code class="varname">ms-self</code>, <code class="varname">krb5-subdomain</code>,
and <code class="varname">ms-subdomain</code> the
<em class="replaceable"><code>identity</code></em> field specifies
the Windows or Kerberos realm of the machine belongs to.
</p>
-<p>
The <em class="replaceable"><code>nametype</code></em> field has 13
values:
<code class="varname">name</code>, <code class="varname">subdomain</code>,
<code class="varname">tcp-self</code>, <code class="varname">6to4-self</code>,
<code class="varname">zonesub</code>, and <code class="varname">external</code>.
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="0.819in" class="1">
+<col width="3.681in" class="2">
</colgroup>
<tbody>
<tr>
This rule is similar to subdomain, except that
it matches when the name being updated is a
subdomain of the zone in which the
- <span><strong class="command">update-policy</strong></span> statement
+ <span class="command"><strong>update-policy</strong></span> statement
appears. This obviates the need to type the zone
name twice, and enables the use of a standard
- <span><strong class="command">update-policy</strong></span> statement in
+ <span class="command"><strong>update-policy</strong></span> statement in
multiple zones without modification.
</p>
<p>
</td>
<td>
<p>
- This rule allows <span><strong class="command">named</strong></span>
+ This rule allows <span class="command"><strong>named</strong></span>
to defer the decision of whether to allow a
given update to an external daemon.
</p>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+
+ <p>
In all cases, the <em class="replaceable"><code>name</code></em>
field must specify a fully-qualified domain name.
</p>
-<p>
+
+ <p>
If no types are explicitly specified, this rule matches
all types except RRSIG, NS, SOA, NSEC and NSEC3. Types
may be specified by name, including "ANY" (ANY matches
all records associated with a name, the rules are
checked for each existing record type.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2599377"></a>Multiple views</h4></div></div></div>
-<p>
+<a name="id-1.7.6.34.7"></a>Multiple views</h4></div></div></div>
+
+ <p>
When multiple views are in use, a zone may be
referenced by more than one of them. Often, the views
will contain different zones with the same name, allowing
different clients to receive different answers for the same
queries. At times, however, it is desirable for multiple
views to contain identical zones. The
- <span><strong class="command">in-view</strong></span> zone option provides an efficient
+ <span class="command"><strong>in-view</strong></span> zone option provides an efficient
way to do this: it allows a view to reference a zone that
was defined in a previously configured view. Example:
</p>
-<pre class="programlisting">
+
<pre class="programlisting">
view internal {
match-clients { 10/8; };
};
};
</pre>
-<p>
- An <span><strong class="command">in-view</strong></span> option cannot refer to a view
+ An <span class="command"><strong>in-view</strong></span> option cannot refer to a view
that is configured later in the configuration file.
</p>
-<p>
- A <span><strong class="command">zone</strong></span> statement which uses the
- <span><strong class="command">in-view</strong></span> option may not use any other
- options with the exception of <span><strong class="command">forward</strong></span>
- and <span><strong class="command">forwarders</strong></span>. (These options control
+ A <span class="command"><strong>zone</strong></span> statement which uses the
+ <span class="command"><strong>in-view</strong></span> option may not use any other
+ options with the exception of <span class="command"><strong>forward</strong></span>
+ and <span class="command"><strong>forwarders</strong></span>. (These options control
the behavior of the containing view, rather than changing
the zone object itself.)
</p>
-<p>
Zone level acls (e.g. allow-query, allow-transfer) and
other configuration details of the zone are all set
in the view the referenced zone is defined in. Care
need to be taken to ensure that acls are wide enough
for all views referencing the zone.
</p>
-<p>
- An <span><strong class="command">in-view</strong></span> zone cannot be used as a
+ An <span class="command"><strong>in-view</strong></span> zone cannot be used as a
response policy zone.
</p>
-<p>
- An <span><strong class="command">in-view</strong></span> zone is not intended to reference
- a <span><strong class="command">forward</strong></span> zone.
+ An <span class="command"><strong>in-view</strong></span> zone is not intended to reference
+ a <span class="command"><strong>forward</strong></span> zone.
</p>
-</div>
-</div>
-</div>
-<div class="sect1" lang="en">
+ </div>
+
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2599438"></a>Zone File</h2></div></div></div>
-<div class="sect2" lang="en">
+<a name="id-1.7.7"></a>Zone File</h2></div></div></div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="types_of_resource_records_and_when_to_use_them"></a>Types of Resource Records and When to Use Them</h3></div></div></div>
-<p>
+
+ <p>
This section, largely borrowed from RFC 1034, describes the
concept of a Resource Record (RR) and explains when each is used.
Since the publication of RFC 1034, several new RRs have been
identified
and implemented in the DNS. These are also included.
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2599457"></a>Resource Records</h4></div></div></div>
-<p>
+<a name="id-1.7.7.3.4"></a>Resource Records</h4></div></div></div>
+
+
+ <p>
A domain name identifies a node. Each node has a set of
resource information, which may be empty. The set of resource
information associated with a particular name is composed of
need not be preserved by name servers, resolvers, or other
parts of the DNS. However, sorting of multiple RRs is
permitted for optimization purposes, for example, to specify
- that a particular nearby server be tried first. See <a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span><strong class="command">sortlist</strong></span> Statement”</a> and <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>.
+ that a particular nearby server be tried first. See <a class="xref" href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span class="command"><strong>sortlist</strong></span> Statement”</a> and <a class="xref" href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>.
</p>
-<p>
+
+ <p>
The components of a Resource Record are:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.000in" class="1">
+<col width="3.500in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
The following are <span class="emphasis"><em>types</em></span> of valid RRs:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="0.875in" class="1">
+<col width="3.625in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
The following <span class="emphasis"><em>classes</em></span> of resource records
are currently valid in the DNS:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+<table border="1">
<colgroup>
-<col>
-<col>
+<col width="0.875in" class="1">
+<col width="3.625in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+
+ <p>
The owner name is often implicit, rather than forming an
integral
part of the RR. For example, many name servers internally form
that
fits the needs of the resource being described.
</p>
-<p>
The meaning of the TTL field is a time limit on how long an
RR can be kept in a cache. This limit does not apply to
authoritative
following
the change.
</p>
-<p>
The data in the RDATA section of RRs is carried as a combination
of binary strings and domain names. The domain names are
frequently
used as "pointers" to other data in the DNS.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2602045"></a>Textual expression of RRs</h4></div></div></div>
-<p>
+<a name="id-1.7.7.3.5"></a>Textual expression of RRs</h4></div></div></div>
+
+ <p>
RRs are represented in binary form in the packets of the DNS
protocol, and are usually represented in highly encoded form
when
possible
using parentheses.
</p>
-<p>
The start of the line gives the owner of the RR. If a line
begins with a blank, then the owner is assumed to be the same as
that of the previous RR. Blank lines are often included for
readability.
</p>
-<p>
Following the owner, we list the TTL, type, and class of the
RR. Class and type use the mnemonics defined above, and TTL is
an integer before the type field. In order to avoid ambiguity
values
are often omitted from examples in the interests of clarity.
</p>
-<p>
The resource data or RDATA section of the RR are given using
knowledge of the typical representation for the data.
</p>
-<p>
For example, we might show the RRs carried in a message as:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+<table border="1">
<colgroup>
-<col>
-<col>
-<col>
+<col width="1.381in" class="1">
+<col width="1.020in" class="2">
+<col width="2.099in" class="3">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
The MX RRs have an RDATA section which consists of a 16-bit
number followed by a domain name. The address RRs use a
standard
IP address format to contain a 32-bit internet address.
</p>
-<p>
The above example shows six RRs, with two RRs at each of three
domain names.
</p>
-<p>
Similarly we might see:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+<table border="1">
<colgroup>
-<col>
-<col>
-<col>
+<col width="1.491in" class="1">
+<col width="1.067in" class="2">
+<col width="2.067in" class="3">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
This example shows two addresses for
<code class="literal">XX.LCS.MIT.EDU</code>, each of a different class.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2602566"></a>Discussion of MX Records</h3></div></div></div>
-<p>
+<a name="id-1.7.7.4"></a>Discussion of MX Records</h3></div></div></div>
+
+
+ <p>
As described above, domain servers store information as a
series of resource records, each of which contains a particular
piece of information about a given domain name (which is usually,
and stored with some additional type information to help systems
determine when the RR is relevant.
</p>
-<p>
+
+ <p>
MX records are used to control delivery of email. The data
specified in the record is a priority and a domain name. The
priority
It <span class="emphasis"><em>must</em></span> have an associated address record
(A or AAAA) — CNAME is not sufficient.
</p>
-<p>
For a given domain, if there is both a CNAME record and an
MX record, the MX record is in error, and will be ignored.
Instead,
pointed to by the CNAME.
For example:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
-<col>
-<col>
-<col>
+<col width="1.708in" class="1">
+<col width="0.444in" class="2">
+<col width="0.444in" class="3">
+<col width="0.976in" class="4">
+<col width="1.553in" class="5">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
+</table>
+ </div>
<p>
Mail delivery will be attempted to <code class="literal">mail.example.com</code> and
<code class="literal">mail2.example.com</code> (in
any order), and if neither of those succeed, delivery to <code class="literal">mail.backup.org</code> will
be attempted.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="Setting_TTLs"></a>Setting TTLs</h3></div></div></div>
-<p>
+
+ <p>
The time-to-live of the RR field is a 32-bit integer represented
in units of seconds, and is primarily used by resolvers when they
cache RRs. The TTL describes how long a RR can be cached before it
currently
used in a zone file.
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="0.750in" class="1">
+<col width="4.375in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+ <p>
All of these TTLs default to units of seconds, though units
can be explicitly specified, for example, <code class="literal">1h30m</code>.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2603113"></a>Inverse Mapping in IPv4</h3></div></div></div>
-<p>
+<a name="id-1.7.7.6"></a>Inverse Mapping in IPv4</h3></div></div></div>
+
+ <p>
Reverse name resolution (that is, translation from IP address
to name) is achieved by means of the <span class="emphasis"><em>in-addr.arpa</em></span> domain
and PTR records. Entries in the in-addr.arpa domain are made in
PTR records if the machine has more than one name. For example,
in the [<span class="optional">example.com</span>] domain:
</p>
-<div class="informaltable"><table border="1">
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.125in" class="1">
+<col width="4.000in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+</table>
+ </div>
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
- The <span><strong class="command">$ORIGIN</strong></span> lines in the examples
+ The <span class="command"><strong>$ORIGIN</strong></span> lines in the examples
are for providing context to the examples only — they do not
necessarily
appear in the actual usage. They are only used here to indicate
that the example is relative to the listed origin.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2603308"></a>Other Zone File Directives</h3></div></div></div>
-<p>
+<a name="id-1.7.7.7"></a>Other Zone File Directives</h3></div></div></div>
+
+ <p>
The Master File Format was initially defined in RFC 1035 and
has subsequently been extended. While the Master File Format
itself
same
class.
</p>
-<p>
- Master File Directives include <span><strong class="command">$ORIGIN</strong></span>, <span><strong class="command">$INCLUDE</strong></span>,
- and <span><strong class="command">$TTL.</strong></span>
+ Master File Directives include <span class="command"><strong>$ORIGIN</strong></span>, <span class="command"><strong>$INCLUDE</strong></span>,
+ and <span class="command"><strong>$TTL.</strong></span>
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2603331"></a>The <span><strong class="command">@</strong></span> (at-sign)</h4></div></div></div>
-<p>
+<a name="id-1.7.7.7.5"></a>The <span class="command"><strong>@</strong></span> (at-sign)</h4></div></div></div>
+
+ <p>
When used in the label (or name) field, the asperand or
at-sign (@) symbol represents the current origin.
At the start of the zone file, it is the
<<code class="varname">zone_name</code>> (followed by
trailing dot).
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2603347"></a>The <span><strong class="command">$ORIGIN</strong></span> Directive</h4></div></div></div>
-<p>
- Syntax: <span><strong class="command">$ORIGIN</strong></span>
+<a name="id-1.7.7.7.6"></a>The <span class="command"><strong>$ORIGIN</strong></span> Directive</h4></div></div></div>
+
+ <p>
+ Syntax: <span class="command"><strong>$ORIGIN</strong></span>
<em class="replaceable"><code>domain-name</code></em>
[<span class="optional"><em class="replaceable"><code>comment</code></em></span>]
</p>
-<p><span><strong class="command">$ORIGIN</strong></span>
+ <p><span class="command"><strong>$ORIGIN</strong></span>
sets the domain name that will be appended to any
unqualified records. When a zone is first read in there
- is an implicit <span><strong class="command">$ORIGIN</strong></span>
- <<code class="varname">zone_name</code>><span><strong class="command">.</strong></span>
+ is an implicit <span class="command"><strong>$ORIGIN</strong></span>
+ <<code class="varname">zone_name</code>><span class="command"><strong>.</strong></span>
(followed by trailing dot).
- The current <span><strong class="command">$ORIGIN</strong></span> is appended to
- the domain specified in the <span><strong class="command">$ORIGIN</strong></span>
+ The current <span class="command"><strong>$ORIGIN</strong></span> is appended to
+ the domain specified in the <span class="command"><strong>$ORIGIN</strong></span>
argument if it is not absolute.
</p>
+
<pre class="programlisting">
$ORIGIN example.com.
WWW CNAME MAIN-SERVER
</pre>
-<p>
+
+ <p>
is equivalent to
</p>
+
<pre class="programlisting">
WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
</pre>
-</div>
-<div class="sect3" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2603476"></a>The <span><strong class="command">$INCLUDE</strong></span> Directive</h4></div></div></div>
-<p>
- Syntax: <span><strong class="command">$INCLUDE</strong></span>
+<a name="id-1.7.7.7.7"></a>The <span class="command"><strong>$INCLUDE</strong></span> Directive</h4></div></div></div>
+
+ <p>
+ Syntax: <span class="command"><strong>$INCLUDE</strong></span>
<em class="replaceable"><code>filename</code></em>
[<span class="optional">
<em class="replaceable"><code>origin</code></em> </span>]
[<span class="optional"> <em class="replaceable"><code>comment</code></em> </span>]
</p>
-<p>
Read and process the file <code class="filename">filename</code> as
- if it were included into the file at this point. If <span><strong class="command">origin</strong></span> is
- specified the file is processed with <span><strong class="command">$ORIGIN</strong></span> set
- to that value, otherwise the current <span><strong class="command">$ORIGIN</strong></span> is
+ if it were included into the file at this point. If <span class="command"><strong>origin</strong></span> is
+ specified the file is processed with <span class="command"><strong>$ORIGIN</strong></span> set
+ to that value, otherwise the current <span class="command"><strong>$ORIGIN</strong></span> is
used.
</p>
-<p>
The origin and the current domain name
- revert to the values they had prior to the <span><strong class="command">$INCLUDE</strong></span> once
+ revert to the values they had prior to the <span class="command"><strong>$INCLUDE</strong></span> once
the file has been read.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
RFC 1035 specifies that the current origin should be restored
after
- an <span><strong class="command">$INCLUDE</strong></span>, but it is silent
+ an <span class="command"><strong>$INCLUDE</strong></span>, but it is silent
on whether the current
domain name should also be restored. BIND 9 restores both of
them.
This could be construed as a deviation from RFC 1035, a
feature, or both.
</p>
-</div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2603545"></a>The <span><strong class="command">$TTL</strong></span> Directive</h4></div></div></div>
-<p>
- Syntax: <span><strong class="command">$TTL</strong></span>
+<a name="id-1.7.7.7.8"></a>The <span class="command"><strong>$TTL</strong></span> Directive</h4></div></div></div>
+
+ <p>
+ Syntax: <span class="command"><strong>$TTL</strong></span>
<em class="replaceable"><code>default-ttl</code></em>
[<span class="optional">
<em class="replaceable"><code>comment</code></em> </span>]
</p>
-<p>
Set the default Time To Live (TTL) for subsequent records
with undefined TTLs. Valid TTLs are of the range 0-2147483647
seconds.
</p>
-<p><span><strong class="command">$TTL</strong></span>
+ <p><span class="command"><strong>$TTL</strong></span>
is defined in RFC 2308.
</p>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2603581"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</h3></div></div></div>
-<p>
- Syntax: <span><strong class="command">$GENERATE</strong></span>
+<a name="id-1.7.7.8"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</h3></div></div></div>
+
+ <p>
+ Syntax: <span class="command"><strong>$GENERATE</strong></span>
<em class="replaceable"><code>range</code></em>
<em class="replaceable"><code>lhs</code></em>
[<span class="optional"><em class="replaceable"><code>ttl</code></em></span>]
<em class="replaceable"><code>rhs</code></em>
[<span class="optional"><em class="replaceable"><code>comment</code></em></span>]
</p>
-<p><span><strong class="command">$GENERATE</strong></span>
+ <p><span class="command"><strong>$GENERATE</strong></span>
is used to create a series of resource records that only
differ from each other by an
- iterator. <span><strong class="command">$GENERATE</strong></span> can be used to
+ iterator. <span class="command"><strong>$GENERATE</strong></span> can be used to
easily generate the sets of records required to support
sub /24 reverse delegations described in RFC 2317:
Classless IN-ADDR.ARPA delegation.
</p>
+
<pre class="programlisting">$ORIGIN 0.0.192.IN-ADDR.ARPA.
$GENERATE 1-2 @ NS SERVER$.EXAMPLE.
$GENERATE 1-127 $ CNAME $.0</pre>
-<p>
+
+ <p>
is equivalent to
</p>
+
<pre class="programlisting">0.0.0.192.IN-ADDR.ARPA. NS SERVER1.EXAMPLE.
0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE.
1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA.
...
127.0.0.192.IN-ADDR.ARPA. CNAME 127.0.0.0.192.IN-ADDR.ARPA.
</pre>
-<p>
+
+ <p>
Generate a set of A and MX records. Note the MX's right hand
side is a quoted string. The quotes will be stripped when the
right hand side is processed.
</p>
+
<pre class="programlisting">
$ORIGIN EXAMPLE.
$GENERATE 1-127 HOST-$ A 1.2.3.$
$GENERATE 1-127 HOST-$ MX "0 ."</pre>
-<p>
+
+ <p>
is equivalent to
</p>
+
<pre class="programlisting">HOST-1.EXAMPLE. A 1.2.3.1
HOST-1.EXAMPLE. MX 0 .
HOST-2.EXAMPLE. A 1.2.3.2
HOST-127.EXAMPLE. A 1.2.3.127
HOST-127.EXAMPLE. MX 0 .
</pre>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="0.875in" class="1">
+<col width="4.250in" class="2">
</colgroup>
<tbody>
<tr>
<td>
- <p><span><strong class="command">range</strong></span></p>
+ <p><span class="command"><strong>range</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">lhs</strong></span></p>
+ <p><span class="command"><strong>lhs</strong></span></p>
</td>
<td>
<p>This
describes the owner name of the resource records
- to be created. Any single <span><strong class="command">$</strong></span>
+ to be created. Any single <span class="command"><strong>$</strong></span>
(dollar sign)
- symbols within the <span><strong class="command">lhs</strong></span> string
+ symbols within the <span class="command"><strong>lhs</strong></span> string
are replaced by the iterator value.
To get a $ in the output, you need to escape the
- <span><strong class="command">$</strong></span> using a backslash
- <span><strong class="command">\</strong></span>,
- e.g. <span><strong class="command">\$</strong></span>. The
- <span><strong class="command">$</strong></span> may optionally be followed
+ <span class="command"><strong>$</strong></span> using a backslash
+ <span class="command"><strong>\</strong></span>,
+ e.g. <span class="command"><strong>\$</strong></span>. The
+ <span class="command"><strong>$</strong></span> may optionally be followed
by modifiers which change the offset from the
iterator, field width and base.
Modifiers are introduced by a
- <span><strong class="command">{</strong></span> (left brace) immediately following the
- <span><strong class="command">$</strong></span> as
- <span><strong class="command">${offset[,width[,base]]}</strong></span>.
- For example, <span><strong class="command">${-20,3,d}</strong></span>
+ <span class="command"><strong>{</strong></span> (left brace) immediately following the
+ <span class="command"><strong>$</strong></span> as
+ <span class="command"><strong>${offset[,width[,base]]}</strong></span>.
+ For example, <span class="command"><strong>${-20,3,d}</strong></span>
subtracts 20 from the current value, prints the
result as a decimal in a zero-padded field of
width 3.
Available output forms are decimal
- (<span><strong class="command">d</strong></span>), octal
- (<span><strong class="command">o</strong></span>), hexadecimal
- (<span><strong class="command">x</strong></span> or <span><strong class="command">X</strong></span>
+ (<span class="command"><strong>d</strong></span>), octal
+ (<span class="command"><strong>o</strong></span>), hexadecimal
+ (<span class="command"><strong>x</strong></span> or <span class="command"><strong>X</strong></span>
for uppercase) and nibble
- (<span><strong class="command">n</strong></span> or <span><strong class="command">N</strong></span>\
+ (<span class="command"><strong>n</strong></span> or <span class="command"><strong>N</strong></span>\
for uppercase). The default modifier is
- <span><strong class="command">${0,0,d}</strong></span>. If the
- <span><strong class="command">lhs</strong></span> is not absolute, the
- current <span><strong class="command">$ORIGIN</strong></span> is appended
+ <span class="command"><strong>${0,0,d}</strong></span>. If the
+ <span class="command"><strong>lhs</strong></span> is not absolute, the
+ current <span class="command"><strong>$ORIGIN</strong></span> is appended
to the name.
</p>
<p>
</p>
<p>
For compatibility with earlier versions,
- <span><strong class="command">$$</strong></span> is still recognized as
+ <span class="command"><strong>$$</strong></span> is still recognized as
indicating a literal $ in the output.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">ttl</strong></span></p>
+ <p><span class="command"><strong>ttl</strong></span></p>
</td>
<td>
<p>
not specified this will be inherited using the
normal TTL inheritance rules.
</p>
- <p><span><strong class="command">class</strong></span>
- and <span><strong class="command">ttl</strong></span> can be
+ <p><span class="command"><strong>class</strong></span>
+ and <span class="command"><strong>ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">class</strong></span></p>
+ <p><span class="command"><strong>class</strong></span></p>
</td>
<td>
<p>
This must match the zone class if it is
specified.
</p>
- <p><span><strong class="command">class</strong></span>
- and <span><strong class="command">ttl</strong></span> can be
+ <p><span class="command"><strong>class</strong></span>
+ and <span class="command"><strong>ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command">type</strong></span></p>
+ <p><span class="command"><strong>type</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">rhs</strong></span></p>
+ <p><span class="command"><strong>rhs</strong></span></p>
</td>
<td>
<p>
- <span><strong class="command">rhs</strong></span>, optionally, quoted string.
+ <span class="command"><strong>rhs</strong></span>, optionally, quoted string.
</p>
</td>
</tr>
</tbody>
-</table></div>
-<p>
- The <span><strong class="command">$GENERATE</strong></span> directive is a <acronym class="acronym">BIND</acronym> extension
+</table>
+ </div>
+ <p>
+ The <span class="command"><strong>$GENERATE</strong></span> directive is a <acronym class="acronym">BIND</acronym> extension
and not part of the standard zone file format.
</p>
-<p>
BIND 8 does not support the optional TTL and CLASS fields.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="zonefile_format"></a>Additional File Formats</h3></div></div></div>
-<p>
+
+ <p>
In addition to the standard textual format, BIND 9
supports the ability to read or dump to zone files in
other formats.
</p>
-<p>
The <code class="constant">raw</code> format is
a binary representation of zone data in a manner similar
to that used in zone transfers. Since it does not require
parsing text, load time is significantly reduced.
</p>
-<p>
An even faster alternative is the <code class="constant">map</code>
format, which is an image of a <acronym class="acronym">BIND</acronym> 9
in-memory zone database; it is capable of being loaded
- directly into memory via the <span><strong class="command">mmap()</strong></span>
+ directly into memory via the <span class="command"><strong>mmap()</strong></span>
function; the zone can begin serving queries almost
immediately.
</p>
-<p>
For a primary server, a zone file in
<code class="constant">raw</code> or <code class="constant">map</code>
format is expected to be generated from a textual zone
- file by the <span><strong class="command">named-compilezone</strong></span> command.
+ file by the <span class="command"><strong>named-compilezone</strong></span> command.
For a secondary server or for a dynamic zone, it is automatically
generated (if this format is specified by the
- <span><strong class="command">masterfile-format</strong></span> option) when
- <span><strong class="command">named</strong></span> dumps the zone contents after
+ <span class="command"><strong>masterfile-format</strong></span> option) when
+ <span class="command"><strong>named</strong></span> dumps the zone contents after
zone transfer or when applying prior updates.
</p>
-<p>
If a zone file in a binary format needs manual modification,
it first must be converted to a textual form by the
- <span><strong class="command">named-compilezone</strong></span> command. All
+ <span class="command"><strong>named-compilezone</strong></span> command. All
necessary modification should go to the text file, which
should then be converted to the binary form by the
- <span><strong class="command">named-compilezone</strong></span> command again.
+ <span class="command"><strong>named-compilezone</strong></span> command again.
</p>
-<p>
- Note that <span><strong class="command">map</strong></span> format is extremely
+ Note that <span class="command"><strong>map</strong></span> format is extremely
architecture-specific. A <code class="constant">map</code>
file <span class="emphasis"><em>cannot</em></span> be used on a system
with different pointer size, endianness or data alignment
portable backup of such a file, conversion to
<code class="constant">text</code> format is recommended.
</p>
-</div>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="statistics"></a>BIND9 Statistics</h2></div></div></div>
-<p>
+
+ <p>
<acronym class="acronym">BIND</acronym> 9 maintains lots of statistics
information and provides several interfaces for users to
get access to the statistics.
are meaningful in <acronym class="acronym">BIND</acronym> 9,
and other information that is considered useful.
</p>
-<p>
+
+ <p>
The statistics information is categorized into the following
sections.
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="3.300in" class="1">
+<col width="2.625in" class="2">
</colgroup>
<tbody>
<tr>
</td>
</tr>
</tbody>
-</table></div>
-<p>
+</table>
+ </div>
+
+ <p>
A subset of Name Server Statistics is collected and shown
per zone for which the server has the authority when
- <span><strong class="command">zone-statistics</strong></span> is set to
+ <span class="command"><strong>zone-statistics</strong></span> is set to
<strong class="userinput"><code>full</code></strong> (or <strong class="userinput"><code>yes</code></strong>
for backward compatibility. See the description of
- <span><strong class="command">zone-statistics</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
- Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and
+ <span class="command"><strong>zone-statistics</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span class="command"><strong>options</strong></span> Statement Definition and
Usage”</a>
for further details.
</p>
-<p>
+
+ <p>
These statistics counters are shown with their zone and
view names. The view name is omitted when the server is
not configured with explicit views.</p>
-<p>
+
+ <p>
There are currently two user interfaces to get access to the
statistics.
One is in the plain text format dumped to the file specified
- by the <span><strong class="command">statistics-file</strong></span> configuration option.
+ by the <span class="command"><strong>statistics-file</strong></span> configuration option.
The other is remotely accessible via a statistics channel
- when the <span><strong class="command">statistics-channels</strong></span> statement
+ when the <span class="command"><strong>statistics-channels</strong></span> statement
is specified in the configuration file
- (see <a href="Bv9ARM.ch06.html#statschannels" title="statistics-channels Statement Grammar">the section called “<span><strong class="command">statistics-channels</strong></span> Statement Grammar”</a>.)
+ (see <a class="xref" href="Bv9ARM.ch06.html#statschannels" title="statistics-channels Statement Grammar">the section called “<span class="command"><strong>statistics-channels</strong></span> Statement Grammar”</a>.)
</p>
-<div class="sect3" lang="en">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="statsfile"></a>The Statistics File</h4></div></div></div>
-<p>
+
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="statsfile"></a>The Statistics File</h3></div></div></div>
+
+ <p>
The text format statistics dump begins with a line, like:
</p>
-<p>
- <span><strong class="command">+++ Statistics Dump +++ (973798949)</strong></span>
+ <span class="command"><strong>+++ Statistics Dump +++ (973798949)</strong></span>
</p>
-<p>
The number in parentheses is a standard
Unix-style timestamp, measured as seconds since January 1, 1970.
as described above.
Each section begins with a line, like:
</p>
-<p>
- <span><strong class="command">++ Name Server Statistics ++</strong></span>
+
+ <p>
+ <span class="command"><strong>++ Name Server Statistics ++</strong></span>
</p>
-<p>
+
+ <p>
Each section consists of lines, each containing the statistics
counter value followed by its textual description.
See below for available counters.
For brevity, counters that have a value of 0 are not shown
in the statistics file.
</p>
-<p>
+
+ <p>
The statistics dump ends with the line where the
number is identical to the number in the beginning line; for example:
</p>
-<p>
- <span><strong class="command">--- Statistics Dump --- (973798949)</strong></span>
+ <span class="command"><strong>--- Statistics Dump --- (973798949)</strong></span>
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="statistics_counters"></a>Statistics Counters</h3></div></div></div>
-<p>
+
+ <p>
The following tables summarize statistics counters that
<acronym class="acronym">BIND</acronym> 9 provides.
For each row of the tables, the leftmost column is the
it gives the corresponding counter name of the
<acronym class="acronym">BIND</acronym> 8 statistics, if applicable.
</p>
-<div class="sect3" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2604727"></a>Name Server Statistics Counters</h4></div></div></div>
-<div class="informaltable"><table border="1">
+<a name="id-1.7.8.10.4"></a>Name Server Statistics Counters</h4></div></div></div>
+
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
-<col>
+<col width="1.150in" class="1">
+<col width="1.150in" class="2">
+<col width="3.350in" class="3">
</colgroup>
<tbody>
<tr>
</tr>
<tr>
<td>
- <p><span><strong class="command">Requestv4</strong></span></p>
+ <p><span class="command"><strong>Requestv4</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RQ</strong></span></p>
+ <p><span class="command"><strong>RQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Requestv6</strong></span></p>
+ <p><span class="command"><strong>Requestv6</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RQ</strong></span></p>
+ <p><span class="command"><strong>RQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ReqEdns0</strong></span></p>
+ <p><span class="command"><strong>ReqEdns0</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ReqBadEDNSVer</strong></span></p>
+ <p><span class="command"><strong>ReqBadEDNSVer</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ReqTSIG</strong></span></p>
+ <p><span class="command"><strong>ReqTSIG</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ReqSIG0</strong></span></p>
+ <p><span class="command"><strong>ReqSIG0</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ReqBadSIG</strong></span></p>
+ <p><span class="command"><strong>ReqBadSIG</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ReqTCP</strong></span></p>
+ <p><span class="command"><strong>ReqTCP</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RTCP</strong></span></p>
+ <p><span class="command"><strong>RTCP</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">AuthQryRej</strong></span></p>
+ <p><span class="command"><strong>AuthQryRej</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RUQ</strong></span></p>
+ <p><span class="command"><strong>RUQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RecQryRej</strong></span></p>
+ <p><span class="command"><strong>RecQryRej</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RURQ</strong></span></p>
+ <p><span class="command"><strong>RURQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">XfrRej</strong></span></p>
+ <p><span class="command"><strong>XfrRej</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RUXFR</strong></span></p>
+ <p><span class="command"><strong>RUXFR</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">UpdateRej</strong></span></p>
+ <p><span class="command"><strong>UpdateRej</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RUUpd</strong></span></p>
+ <p><span class="command"><strong>RUUpd</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Response</strong></span></p>
+ <p><span class="command"><strong>Response</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SAns</strong></span></p>
+ <p><span class="command"><strong>SAns</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RespTruncated</strong></span></p>
+ <p><span class="command"><strong>RespTruncated</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RespEDNS0</strong></span></p>
+ <p><span class="command"><strong>RespEDNS0</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RespTSIG</strong></span></p>
+ <p><span class="command"><strong>RespTSIG</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RespSIG0</strong></span></p>
+ <p><span class="command"><strong>RespSIG0</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QrySuccess</strong></span></p>
+ <p><span class="command"><strong>QrySuccess</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
This means the query which returns a NOERROR response
with at least one answer RR.
This corresponds to the
- <span><strong class="command">success</strong></span> counter
+ <span class="command"><strong>success</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryAuthAns</strong></span></p>
+ <p><span class="command"><strong>QryAuthAns</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryNoauthAns</strong></span></p>
+ <p><span class="command"><strong>QryNoauthAns</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SNaAns</strong></span></p>
+ <p><span class="command"><strong>SNaAns</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryReferral</strong></span></p>
+ <p><span class="command"><strong>QryReferral</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Queries resulted in referral answer.
This corresponds to the
- <span><strong class="command">referral</strong></span> counter
+ <span class="command"><strong>referral</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryNxrrset</strong></span></p>
+ <p><span class="command"><strong>QryNxrrset</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Queries resulted in NOERROR responses with no data.
This corresponds to the
- <span><strong class="command">nxrrset</strong></span> counter
+ <span class="command"><strong>nxrrset</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QrySERVFAIL</strong></span></p>
+ <p><span class="command"><strong>QrySERVFAIL</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SFail</strong></span></p>
+ <p><span class="command"><strong>SFail</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryFORMERR</strong></span></p>
+ <p><span class="command"><strong>QryFORMERR</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SFErr</strong></span></p>
+ <p><span class="command"><strong>SFErr</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryNXDOMAIN</strong></span></p>
+ <p><span class="command"><strong>QryNXDOMAIN</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SNXD</strong></span></p>
+ <p><span class="command"><strong>SNXD</strong></span></p>
</td>
<td>
<p>
Queries resulted in NXDOMAIN.
This corresponds to the
- <span><strong class="command">nxdomain</strong></span> counter
+ <span class="command"><strong>nxdomain</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryRecursion</strong></span></p>
+ <p><span class="command"><strong>QryRecursion</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RFwdQ</strong></span></p>
+ <p><span class="command"><strong>RFwdQ</strong></span></p>
</td>
<td>
<p>
Queries which caused the server
to perform recursion in order to find the final answer.
This corresponds to the
- <span><strong class="command">recursion</strong></span> counter
+ <span class="command"><strong>recursion</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryDuplicate</strong></span></p>
+ <p><span class="command"><strong>QryDuplicate</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RDupQ</strong></span></p>
+ <p><span class="command"><strong>RDupQ</strong></span></p>
</td>
<td>
<p>
IP address, port, query ID, name, type and class
already being processed.
This corresponds to the
- <span><strong class="command">duplicate</strong></span> counter
+ <span class="command"><strong>duplicate</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryDropped</strong></span></p>
+ <p><span class="command"><strong>QryDropped</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
class and were subsequently dropped.
This is the number of dropped queries due to
the reason explained with the
- <span><strong class="command">clients-per-query</strong></span>
+ <span class="command"><strong>clients-per-query</strong></span>
and
- <span><strong class="command">max-clients-per-query</strong></span>
+ <span class="command"><strong>max-clients-per-query</strong></span>
options
(see the description about
- <a href="Bv9ARM.ch06.html#clients-per-query"><span><strong class="command">clients-per-query</strong></span></a>.)
+ <a class="xref" href="Bv9ARM.ch06.html#clients-per-query"><span class="command"><strong>clients-per-query</strong></span></a>.)
This corresponds to the
- <span><strong class="command">dropped</strong></span> counter
+ <span class="command"><strong>dropped</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryFailure</strong></span></p>
+ <p><span class="command"><strong>QryFailure</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Other query failures.
This corresponds to the
- <span><strong class="command">failure</strong></span> counter
+ <span class="command"><strong>failure</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
Note: this counter is provided mainly for
backward compatibility with the previous versions.
Normally a more fine-grained counters such as
- <span><strong class="command">AuthQryRej</strong></span> and
- <span><strong class="command">RecQryRej</strong></span>
+ <span class="command"><strong>AuthQryRej</strong></span> and
+ <span class="command"><strong>RecQryRej</strong></span>
that would also fall into this counter are provided,
and so this counter would not be of much
interest in practice.
</tr>
<tr>
<td>
- <p><span><strong class="command">QryNXRedir</strong></span></p>
+ <p><span class="command"><strong>QryNXRedir</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryNXRedirRLookup</strong></span></p>
+ <p><span class="command"><strong>QryNXRedirRLookup</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">XfrReqDone</strong></span></p>
+ <p><span class="command"><strong>XfrReqDone</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">UpdateReqFwd</strong></span></p>
+ <p><span class="command"><strong>UpdateReqFwd</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">UpdateRespFwd</strong></span></p>
+ <p><span class="command"><strong>UpdateRespFwd</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">UpdateFwdFail</strong></span></p>
+ <p><span class="command"><strong>UpdateFwdFail</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">UpdateDone</strong></span></p>
+ <p><span class="command"><strong>UpdateDone</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">UpdateFail</strong></span></p>
+ <p><span class="command"><strong>UpdateFail</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">UpdateBadPrereq</strong></span></p>
+ <p><span class="command"><strong>UpdateBadPrereq</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RateDropped</strong></span></p>
+ <p><span class="command"><strong>RateDropped</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RateSlipped</strong></span></p>
+ <p><span class="command"><strong>RateSlipped</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">RPZRewrites</strong></span></p>
+ <p><span class="command"><strong>RPZRewrites</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
-</div>
-<div class="sect3" lang="en">
+</table>
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2606292"></a>Zone Maintenance Statistics Counters</h4></div></div></div>
-<div class="informaltable"><table border="1">
+<a name="id-1.7.8.10.5"></a>Zone Maintenance Statistics Counters</h4></div></div></div>
+
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.150in" class="1">
+<col width="3.350in" class="2">
</colgroup>
<tbody>
<tr>
</tr>
<tr>
<td>
- <p><span><strong class="command">NotifyOutv4</strong></span></p>
+ <p><span class="command"><strong>NotifyOutv4</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">NotifyOutv6</strong></span></p>
+ <p><span class="command"><strong>NotifyOutv6</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">NotifyInv4</strong></span></p>
+ <p><span class="command"><strong>NotifyInv4</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">NotifyInv6</strong></span></p>
+ <p><span class="command"><strong>NotifyInv6</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">NotifyRej</strong></span></p>
+ <p><span class="command"><strong>NotifyRej</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">SOAOutv4</strong></span></p>
+ <p><span class="command"><strong>SOAOutv4</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">SOAOutv6</strong></span></p>
+ <p><span class="command"><strong>SOAOutv6</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">AXFRReqv4</strong></span></p>
+ <p><span class="command"><strong>AXFRReqv4</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">AXFRReqv6</strong></span></p>
+ <p><span class="command"><strong>AXFRReqv6</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">IXFRReqv4</strong></span></p>
+ <p><span class="command"><strong>IXFRReqv4</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">IXFRReqv6</strong></span></p>
+ <p><span class="command"><strong>IXFRReqv6</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">XfrSuccess</strong></span></p>
+ <p><span class="command"><strong>XfrSuccess</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">XfrFail</strong></span></p>
+ <p><span class="command"><strong>XfrFail</strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
-</div>
-<div class="sect3" lang="en">
+</table>
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2606811"></a>Resolver Statistics Counters</h4></div></div></div>
-<div class="informaltable"><table border="1">
+<a name="id-1.7.8.10.6"></a>Resolver Statistics Counters</h4></div></div></div>
+
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
-<col>
+<col width="1.150in" class="1">
+<col width="1.150in" class="2">
+<col width="3.350in" class="3">
</colgroup>
<tbody>
<tr>
</tr>
<tr>
<td>
- <p><span><strong class="command">Queryv4</strong></span></p>
+ <p><span class="command"><strong>Queryv4</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SFwdQ</strong></span></p>
+ <p><span class="command"><strong>SFwdQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Queryv6</strong></span></p>
+ <p><span class="command"><strong>Queryv6</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SFwdQ</strong></span></p>
+ <p><span class="command"><strong>SFwdQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Responsev4</strong></span></p>
+ <p><span class="command"><strong>Responsev4</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RR</strong></span></p>
+ <p><span class="command"><strong>RR</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Responsev6</strong></span></p>
+ <p><span class="command"><strong>Responsev6</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RR</strong></span></p>
+ <p><span class="command"><strong>RR</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">NXDOMAIN</strong></span></p>
+ <p><span class="command"><strong>NXDOMAIN</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RNXD</strong></span></p>
+ <p><span class="command"><strong>RNXD</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">SERVFAIL</strong></span></p>
+ <p><span class="command"><strong>SERVFAIL</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RFail</strong></span></p>
+ <p><span class="command"><strong>RFail</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">FORMERR</strong></span></p>
+ <p><span class="command"><strong>FORMERR</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RFErr</strong></span></p>
+ <p><span class="command"><strong>RFErr</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">OtherError</strong></span></p>
+ <p><span class="command"><strong>OtherError</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RErr</strong></span></p>
+ <p><span class="command"><strong>RErr</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">EDNS0Fail</strong></span></p>
+ <p><span class="command"><strong>EDNS0Fail</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Mismatch</strong></span></p>
+ <p><span class="command"><strong>Mismatch</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RDupR</strong></span></p>
+ <p><span class="command"><strong>RDupR</strong></span></p>
</td>
<td>
<p>
and/or the response's source port does not
match what was expected.
(The port must be 53 or as defined by
- the <span><strong class="command">port</strong></span> option.)
+ the <span class="command"><strong>port</strong></span> option.)
This may be an indication of a cache
poisoning attempt.
</p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Truncated</strong></span></p>
+ <p><span class="command"><strong>Truncated</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Lame</strong></span></p>
+ <p><span class="command"><strong>Lame</strong></span></p>
</td>
<td>
- <p><span><strong class="command">RLame</strong></span></p>
+ <p><span class="command"><strong>RLame</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">Retry</strong></span></p>
+ <p><span class="command"><strong>Retry</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SDupQ</strong></span></p>
+ <p><span class="command"><strong>SDupQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QueryAbort</strong></span></p>
+ <p><span class="command"><strong>QueryAbort</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QuerySockFail</strong></span></p>
+ <p><span class="command"><strong>QuerySockFail</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QueryTimeout</strong></span></p>
+ <p><span class="command"><strong>QueryTimeout</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">GlueFetchv4</strong></span></p>
+ <p><span class="command"><strong>GlueFetchv4</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SSysQ</strong></span></p>
+ <p><span class="command"><strong>SSysQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">GlueFetchv6</strong></span></p>
+ <p><span class="command"><strong>GlueFetchv6</strong></span></p>
</td>
<td>
- <p><span><strong class="command">SSysQ</strong></span></p>
+ <p><span class="command"><strong>SSysQ</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">GlueFetchv4Fail</strong></span></p>
+ <p><span class="command"><strong>GlueFetchv4Fail</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">GlueFetchv6Fail</strong></span></p>
+ <p><span class="command"><strong>GlueFetchv6Fail</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ValAttempt</strong></span></p>
+ <p><span class="command"><strong>ValAttempt</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ValOk</strong></span></p>
+ <p><span class="command"><strong>ValOk</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ValNegOk</strong></span></p>
+ <p><span class="command"><strong>ValNegOk</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">ValFail</strong></span></p>
+ <p><span class="command"><strong>ValFail</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command">QryRTTnn</strong></span></p>
+ <p><span class="command"><strong>QryRTTnn</strong></span></p>
</td>
<td>
- <p><span><strong class="command"></strong></span></p>
+ <p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Frequency table on round trip times (RTTs) of
queries.
- Each <span><strong class="command">nn</strong></span> specifies the corresponding
+ Each <span class="command"><strong>nn</strong></span> specifies the corresponding
frequency.
In the sequence of
- <span><strong class="command">nn_1</strong></span>,
- <span><strong class="command">nn_2</strong></span>,
+ <span class="command"><strong>nn_1</strong></span>,
+ <span class="command"><strong>nn_2</strong></span>,
...,
- <span><strong class="command">nn_m</strong></span>,
- the value of <span><strong class="command">nn_i</strong></span> is the
+ <span class="command"><strong>nn_m</strong></span>,
+ the value of <span class="command"><strong>nn_i</strong></span> is the
number of queries whose RTTs are between
- <span><strong class="command">nn_(i-1)</strong></span> (inclusive) and
- <span><strong class="command">nn_i</strong></span> (exclusive) milliseconds.
+ <span class="command"><strong>nn_(i-1)</strong></span> (inclusive) and
+ <span class="command"><strong>nn_i</strong></span> (exclusive) milliseconds.
For the sake of convenience we define
- <span><strong class="command">nn_0</strong></span> to be 0.
+ <span class="command"><strong>nn_0</strong></span> to be 0.
The last entry should be represented as
- <span><strong class="command">nn_m+</strong></span>, which means the
+ <span class="command"><strong>nn_m+</strong></span>, which means the
number of queries whose RTTs are equal to or over
- <span><strong class="command">nn_m</strong></span> milliseconds.
+ <span class="command"><strong>nn_m</strong></span> milliseconds.
</p>
</td>
</tr>
</tbody>
-</table></div>
-</div>
-<div class="sect3" lang="en">
+</table>
+ </div>
+
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2607765"></a>Socket I/O Statistics Counters</h4></div></div></div>
-<p>
+<a name="id-1.7.8.10.7"></a>Socket I/O Statistics Counters</h4></div></div></div>
+
+
+ <p>
Socket I/O statistics counters are defined per socket
types, which are
- <span><strong class="command">UDP4</strong></span> (UDP/IPv4),
- <span><strong class="command">UDP6</strong></span> (UDP/IPv6),
- <span><strong class="command">TCP4</strong></span> (TCP/IPv4),
- <span><strong class="command">TCP6</strong></span> (TCP/IPv6),
- <span><strong class="command">Unix</strong></span> (Unix Domain), and
- <span><strong class="command">FDwatch</strong></span> (sockets opened outside the
+ <span class="command"><strong>UDP4</strong></span> (UDP/IPv4),
+ <span class="command"><strong>UDP6</strong></span> (UDP/IPv6),
+ <span class="command"><strong>TCP4</strong></span> (TCP/IPv4),
+ <span class="command"><strong>TCP6</strong></span> (TCP/IPv6),
+ <span class="command"><strong>Unix</strong></span> (Unix Domain), and
+ <span class="command"><strong>FDwatch</strong></span> (sockets opened outside the
socket module).
- In the following table <span><strong class="command"><TYPE></strong></span>
+ In the following table <span class="command"><strong><TYPE></strong></span>
represents a socket type.
Not all counters are available for all socket types;
exceptions are noted in the description field.
</p>
-<div class="informaltable"><table border="1">
+
+ <div class="informaltable">
+ <table border="1">
<colgroup>
-<col>
-<col>
+<col width="1.150in" class="1">
+<col width="3.350in" class="2">
</colgroup>
<tbody>
<tr>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>Open</strong></span></p>
+ <p><span class="command"><strong><TYPE>Open</strong></span></p>
</td>
<td>
<p>
Sockets opened successfully.
This counter is not applicable to the
- <span><strong class="command">FDwatch</strong></span> type.
+ <span class="command"><strong>FDwatch</strong></span> type.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>OpenFail</strong></span></p>
+ <p><span class="command"><strong><TYPE>OpenFail</strong></span></p>
</td>
<td>
<p>
Failures of opening sockets.
This counter is not applicable to the
- <span><strong class="command">FDwatch</strong></span> type.
+ <span class="command"><strong>FDwatch</strong></span> type.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>Close</strong></span></p>
+ <p><span class="command"><strong><TYPE>Close</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>BindFail</strong></span></p>
+ <p><span class="command"><strong><TYPE>BindFail</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>ConnFail</strong></span></p>
+ <p><span class="command"><strong><TYPE>ConnFail</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>Conn</strong></span></p>
+ <p><span class="command"><strong><TYPE>Conn</strong></span></p>
</td>
<td>
<p>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>AcceptFail</strong></span></p>
+ <p><span class="command"><strong><TYPE>AcceptFail</strong></span></p>
</td>
<td>
<p>
Failures of accepting incoming connection requests.
This counter is not applicable to the
- <span><strong class="command">UDP</strong></span> and
- <span><strong class="command">FDwatch</strong></span> types.
+ <span class="command"><strong>UDP</strong></span> and
+ <span class="command"><strong>FDwatch</strong></span> types.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>Accept</strong></span></p>
+ <p><span class="command"><strong><TYPE>Accept</strong></span></p>
</td>
<td>
<p>
Incoming connections successfully accepted.
This counter is not applicable to the
- <span><strong class="command">UDP</strong></span> and
- <span><strong class="command">FDwatch</strong></span> types.
+ <span class="command"><strong>UDP</strong></span> and
+ <span class="command"><strong>FDwatch</strong></span> types.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>SendErr</strong></span></p>
+ <p><span class="command"><strong><TYPE>SendErr</strong></span></p>
</td>
<td>
<p>
Errors in socket send operations.
This counter corresponds
- to <span><strong class="command">SErr</strong></span> counter of
- <span><strong class="command">BIND</strong></span> 8.
+ to <span class="command"><strong>SErr</strong></span> counter of
+ <span class="command"><strong>BIND</strong></span> 8.
</p>
</td>
</tr>
<tr>
<td>
- <p><span><strong class="command"><TYPE>RecvErr</strong></span></p>
+ <p><span class="command"><strong><TYPE>RecvErr</strong></span></p>
</td>
<td>
<p>
</td>
</tr>
</tbody>
-</table></div>
-</div>
-<div class="sect3" lang="en">
+</table>
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2608275"></a>Compatibility with <span class="emphasis"><em>BIND</em></span> 8 Counters</h4></div></div></div>
-<p>
+<a name="id-1.7.8.10.8"></a>Compatibility with <span class="emphasis"><em>BIND</em></span> 8 Counters</h4></div></div></div>
+
+ <p>
Most statistics counters that were available
- in <span><strong class="command">BIND</strong></span> 8 are also supported in
- <span><strong class="command">BIND</strong></span> 9 as shown in the above tables.
+ in <span class="command"><strong>BIND</strong></span> 8 are also supported in
+ <span class="command"><strong>BIND</strong></span> 9 as shown in the above tables.
Here are notes about other counters that do not appear
in these tables.
</p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">RFwdR,SFwdR</strong></span></span></dt>
-<dd><p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>RFwdR,SFwdR</strong></span></span></dt>
+<dd>
+ <p>
These counters are not supported
- because <span><strong class="command">BIND</strong></span> 9 does not adopt
+ because <span class="command"><strong>BIND</strong></span> 9 does not adopt
the notion of <span class="emphasis"><em>forwarding</em></span>
- as <span><strong class="command">BIND</strong></span> 8 did.
- </p></dd>
-<dt><span class="term"><span><strong class="command">RAXFR</strong></span></span></dt>
-<dd><p>
+ as <span class="command"><strong>BIND</strong></span> 8 did.
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>RAXFR</strong></span></span></dt>
+<dd>
+ <p>
This counter is accessible in the Incoming Queries section.
- </p></dd>
-<dt><span class="term"><span><strong class="command">RIQ</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>RIQ</strong></span></span></dt>
+<dd>
+ <p>
This counter is accessible in the Incoming Requests section.
- </p></dd>
-<dt><span class="term"><span><strong class="command">ROpts</strong></span></span></dt>
-<dd><p>
+ </p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>ROpts</strong></span></span></dt>
+<dd>
+ <p>
This counter is not supported
- because <span><strong class="command">BIND</strong></span> 9 does not care
+ because <span class="command"><strong>BIND</strong></span> 9 does not care
about IP options in the first place.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-</div>
-</div>
-</div>
+ </div>
+ </div>
+ </div>
+
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 7. BIND 9 Security Considerations</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch06.html" title="Chapter 6. BIND 9 Configuration Reference">
<link rel="next" href="Bv9ARM.ch08.html" title="Chapter 8. Troubleshooting">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch07"></a>Chapter 7. <acronym class="acronym">BIND</acronym> 9 Security Considerations</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch07"></a>Chapter 7. <acronym class="acronym">BIND</acronym> 9 Security Considerations</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2608685"><span><strong class="command">Chroot</strong></span> and <span><strong class="command">Setuid</strong></span></a></span></dt>
+<dl class="toc">
+<dt><span class="sect
ion"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.4"><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span></a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2608835">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2608894">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.4.7">The <span class="command"><strong>chroot</strong></span> Environment</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.4.8">Using the <span class="command"><strong>setuid</strong></span> Function</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
</dl>
</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="Access_Control_Lists"></a>Access Control Lists</h2></div></div></div>
-<p>
+
+ <p>
Access Control Lists (ACLs) are address match lists that
you can set up and nickname for future use in
- <span><strong class="command">allow-notify</strong></span>, <span><strong class="command">allow-query</strong></span>,
- <span><strong class="command">allow-query-on</strong></span>, <span><strong class="command">allow-recursion</strong></span>,
- <span><strong class="command">blackhole</strong></span>, <span><strong class="command">allow-transfer</strong></span>,
- <span><strong class="command">match-clients</strong></span>, etc.
+ <span class="command"><strong>allow-notify</strong></span>, <span class="command"><strong>allow-query</strong></span>,
+ <span class="command"><strong>allow-query-on</strong></span>, <span class="command"><strong>allow-recursion</strong></span>,
+ <span class="command"><strong>blackhole</strong></span>, <span class="command"><strong>allow-transfer</strong></span>,
+ <span class="command"><strong>match-clients</strong></span>, etc.
</p>
-<p>
Using ACLs allows you to have finer control over who can access
your name server, without cluttering up your config files with huge
lists of IP addresses.
</p>
-<p>
It is a <span class="emphasis"><em>good idea</em></span> to use ACLs, and to
control access to your server. Limiting access to your server by
outside parties can help prevent spoofing and denial of service
(DoS) attacks against your server.
</p>
-<p>
ACLs match clients on the basis of up to three characteristics:
1) The client's IP address; 2) the TSIG or SIG(0) key that was
used to sign the request, if any; and 3) an address prefix
encoded in an EDNS Client Subnet option, if any.
</p>
-<p>
Here is an example of ACLs based on client addresses:
</p>
+
<pre class="programlisting">
// Set up an ACL named "bogusnets" that will block
// RFC1918 space and some reserved space, which is
allow-query { any; };
};
</pre>
-<p>
+
+ <p>
This allows authoritative queries for "example.com" from any
address, but recursive queries only from the networks specified
in "our-nets", and no queries at all from the networks
specified in "bogusnets".
</p>
-<p>
In addition to network addresses and prefixes, which are
matched against the source address of the DNS request, ACLs
may include <code class="option">key</code> elements, which specify the
if that prefix matches an EDNS client subnet option included
in the request.
</p>
-<p>
The EDNS Client Subnet (ECS) option is used by a recursive
resolver to inform an authoritative name server of the network
address block from which the original query was received, enabling
authoritative servers to give different answers to the same
resolver for different resolver clients. An ACL containing
an element of the form
- <span><strong class="command">ecs <em class="replaceable"><code>prefix</code></em></strong></span>
+ <span class="command"><strong>ecs <em class="replaceable"><code>prefix</code></em></strong></span>
will match if a request arrives in containing an ECS option
encoding an address within that prefix. If the request has no
ECS option, then "ecs" elements are simply ignored. Addresses
in ACLs that are not prefixed with "ecs" are matched only
against the source address.
</p>
-<p>
When <acronym class="acronym">BIND</acronym> 9 is built with GeoIP support,
ACLs can also be used for geographic access restrictions.
This is done by specifying an ACL element of the form:
- <span><strong class="command">geoip [<span class="optional">db <em class="replaceable"><code>database</code></em></span>] <em class="replaceable"><code>field</code></em> <em class="replaceable"><code>value</code></em></strong></span>
+ <span class="command"><strong>geoip [<span class="optional">db <em class="replaceable"><code>database</code></em></span>] <em class="replaceable"><code>field</code></em> <em class="replaceable"><code>value</code></em></strong></span>
</p>
-<p>
The <em class="replaceable"><code>field</code></em> indicates which field
to search for a match. Available fields are "country",
"region", "city", "continent", "postal" (postal code),
"metro" (metro code), "area" (area code), "tz" (timezone),
"isp", "org", "asnum", "domain" and "netspeed".
</p>
-<p>
<em class="replaceable"><code>value</code></em> is the value to search
for within the database. A string may be quoted if it
contains spaces or other special characters. If this is
standard two-letter state or province abbreviation;
otherwise it is the full name of the state or province.
</p>
-<p>
The <em class="replaceable"><code>database</code></em> field indicates which
GeoIP database to search for a match. In most cases this is
unnecessary, because most search fields can only be found in
database if it is installed, or the "region" database if it is
installed, or the "country" database, in that order.
</p>
-<p>
By default, if a DNS query includes an EDNS Client Subnet (ECS)
option which encodes a non-zero address prefix, then GeoIP ACLs
will be matched against that address prefix. Otherwise, they
are matched against the source address of the query. To
prevent GeoIP ACLs from matching against ECS options, set
- the <span><strong class="command">geoip-use-ecs</strong></span> to <code class="literal">no</code>.
+ the <span class="command"><strong>geoip-use-ecs</strong></span> to <code class="literal">no</code>.
</p>
-<p>
Some example GeoIP ACLs:
</p>
-<pre class="programlisting">geoip country US;
+
<pre class="programlisting">geoip country US;
geoip country JAP;
geoip db country country Canada;
geoip db region region WA;
geoip tz "America/Los_Angeles";
geoip org "Internet Systems Consortium";
</pre>
-<p>
+
+ <p>
ACLs use a "first-match" logic rather than "best-match":
if an address prefix matches an ACL element, then that ACL
is considered to have matched even if a later element would
have matched more specifically. For example, the ACL
- <span><strong class="command"> { 10/8; !10.0.0.1; }</strong></span> would actually
+ <span class="command"><strong> { 10/8; !10.0.0.1; }</strong></span> would actually
match a query from 10.0.0.1, because the first element
indicated that the query should be accepted, and the second
element is ignored.
</p>
-<p>
When using "nested" ACLs (that is, ACLs included or referenced
within other ACLs), a negative match of a nested ACL will
the containing ACL to continue looking for matches. This
it originates from a particular network <span class="emphasis"><em>and</em></span>
only when it is signed with a particular key, use:
</p>
-<pre class="programlisting">
+
<pre class="programlisting">
allow-query { !{ !10/8; any; }; key example; };
</pre>
-<p>
Within the nested ACL, any address that is
<span class="emphasis"><em>not</em></span> in the 10/8 network prefix will
be rejected, and this will terminate processing of the
will only matches when <span class="emphasis"><em>both</em></span> conditions
are true.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2608685"></a><span><strong class="command">Chroot</strong></span> and <span><strong class="command">Setuid</strong></span>
+<a name="id-1.8.4"></a><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span>
</h2></div></div></div>
-<p>
+
+ <p>
On UNIX servers, it is possible to run <acronym class="acronym">BIND</acronym>
in a <span class="emphasis"><em>chrooted</em></span> environment (using
- the <span><strong class="command">chroot()</strong></span> function) by specifying
- the <code class="option">-t</code> option for <span><strong class="command">named</strong></span>.
+ the <span class="command"><strong>chroot()</strong></span> function) by specifying
+ the <code class="option">-t</code> option for <span class="command"><strong>named</strong></span>.
This can help improve system security by placing
<acronym class="acronym">BIND</acronym> in a "sandbox", which will limit
the damage done if a server is compromised.
</p>
-<p>
Another useful feature in the UNIX version of <acronym class="acronym">BIND</acronym> is the
ability to run the daemon as an unprivileged user ( <code class="option">-u</code> <em class="replaceable"><code>user</code></em> ).
- We suggest running as an unprivileged user when using the <span><strong class="command">chroot</strong></span> feature.
+ We suggest running as an unprivileged user when using the <span class="command"><strong>chroot</strong></span> feature.
</p>
-<p>
- Here is an example command line to load <acronym class="acronym">BIND</acronym> in a <span><strong class="command">chroot</strong></span> sandbox,
- <span><strong class="command">/var/named</strong></span>, and to run <span><strong class="command">named</strong></span> <span><strong class="command">setuid</strong></span> to
+ Here is an example command line to load <acronym class="acronym">BIND</acronym> in a <span class="command"><strong>chroot</strong></span> sandbox,
+ <span class="command"><strong>/var/named</strong></span>, and to run <span class="command"><strong>named</strong></span> <span class="command"><strong>setuid</strong></span> to
user 202:
</p>
-<p>
<strong class="userinput"><code>/usr/local/sbin/named -u 202 -t /var/named</code></strong>
</p>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2608835"></a>The <span><strong class="command">chroot</strong></span> Environment</h3></div></div></div>
-<p>
- In order for a <span><strong class="command">chroot</strong></span> environment
+<a name="id-1.8.4.7"></a>The <span class="command"><strong>chroot</strong></span> Environment</h3></div></div></div>
+
+
+ <p>
+ In order for a <span class="command"><strong>chroot</strong></span> environment
to
work properly in a particular directory
(for example, <code class="filename">/var/named</code>),
From <acronym class="acronym">BIND</acronym>'s point of view, <code class="filename">/var/named</code> is
the root of the filesystem. You will need to adjust the values of
options like
- like <span><strong class="command">directory</strong></span> and <span><strong class="command">pid-file</strong></span> to account
+ like <span class="command"><strong>directory</strong></span> and <span class="command"><strong>pid-file</strong></span> to account
for this.
</p>
-<p>
Unlike with earlier versions of BIND, you typically will
- <span class="emphasis"><em>not</em></span> need to compile <span><strong class="command">named</strong></span>
+ <span class="emphasis"><em>not</em></span> need to compile <span class="command"><strong>named</strong></span>
statically nor install shared libraries under the new root.
However, depending on your operating system, you may need
to set up things like
<code class="filename">/dev/log</code>, and
<code class="filename">/etc/localtime</code>.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2608894"></a>Using the <span><strong class="command">setuid</strong></span> Function</h3></div></div></div>
-<p>
- Prior to running the <span><strong class="command">named</strong></span> daemon,
+<a name="id-1.8.4.8"></a>Using the <span class="command"><strong>setuid</strong></span> Function</h3></div></div></div>
+
+
+ <p>
+ Prior to running the <span class="command"><strong>named</strong></span> daemon,
use
- the <span><strong class="command">touch</strong></span> utility (to change file
+ the <span class="command"><strong>touch</strong></span> utility (to change file
access and
- modification times) or the <span><strong class="command">chown</strong></span>
+ modification times) or the <span class="command"><strong>chown</strong></span>
utility (to
set the user id and/or group id) on files
to which you want <acronym class="acronym">BIND</acronym>
to write.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
- Note that if the <span><strong class="command">named</strong></span> daemon is running as an
+ Note that if the <span class="command"><strong>named</strong></span> daemon is running as an
unprivileged user, it will not be able to bind to new restricted
ports if the server is reloaded.
</div>
-</div>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ </div>
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="dynamic_update_security"></a>Dynamic Update Security</h2></div></div></div>
-<p>
+
+
+ <p>
Access to the dynamic
update facility should be strictly limited. In earlier versions of
<acronym class="acronym">BIND</acronym>, the only way to do this was
based on the IP
address of the host requesting the update, by listing an IP address
or
- network prefix in the <span><strong class="command">allow-update</strong></span>
+ network prefix in the <span class="command"><strong>allow-update</strong></span>
zone option.
This method is insecure since the source address of the update UDP
packet
is easily forged. Also note that if the IP addresses allowed by the
- <span><strong class="command">allow-update</strong></span> option include the
+ <span class="command"><strong>allow-update</strong></span> option include the
address of a slave
server which performs forwarding of dynamic updates, the master can
be
forward it to the master with its own source IP address causing the
master to approve it without question.
</p>
-<p>
+
+ <p>
For these reasons, we strongly recommend that updates be
cryptographically authenticated by means of transaction signatures
- (TSIG). That is, the <span><strong class="command">allow-update</strong></span>
+ (TSIG). That is, the <span class="command"><strong>allow-update</strong></span>
option should
list only TSIG key names, not IP addresses or network
- prefixes. Alternatively, the new <span><strong class="command">update-policy</strong></span>
+ prefixes. Alternatively, the new <span class="command"><strong>update-policy</strong></span>
option can be used.
</p>
-<p>
+
+ <p>
Some sites choose to keep all dynamically-updated DNS data
in a subdomain and delegate that subdomain to a separate zone. This
way, the top-level zone containing critical data such as the IP
of public web and mail servers need not allow dynamic update at
all.
</p>
-</div>
-</div>
+
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 8. Troubleshooting</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch07.html" title="Chapter 7. BIND 9 Security Considerations">
<link rel="next" href="Bv9ARM.ch09.html" title="Appendix A. Release Notes">
</table>
<hr>
</div>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch08"></a>Chapter 8. Troubleshooting</h2></div></div></div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch08"></a>Chapter 8. Troubleshooting</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2608974">Common Problems</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2608980">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2608992">Incrementing and Changing the Serial Number</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2609009">Where Can I Get Help?</a></span></dt>
+<dl class="toc">
+<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.3">Common Problems</a></span></dt>
+<dd><dl><dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.3.3">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
+<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.4">Incrementing and Changing the Serial Number</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.5">Where Can I Get Help?</a></span></dt>
</dl>
</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2608974"></a>Common Problems</h2></div></div></div>
-<div class="sect2" lang="en">
+<a name="id-1.9.3"></a>Common Problems</h2></div></div></div>
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2608980"></a>It's not working; how can I figure out what's wrong?</h3></div></div></div>
-<p>
+<a name="id-1.9.3.3"></a>It's not working; how can I figure out what's wrong?</h3></div></div></div>
+
+
+ <p>
The best solution to solving installation and
configuration issues is to take preventative measures by setting
up logging files beforehand. The log files provide a
source of hints and information that can be used to figure out
what went wrong and how to fix the problem.
</p>
-</div>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2608992"></a>Incrementing and Changing the Serial Number</h2></div></div></div>
-<p>
+<a name="id-1.9.4"></a>Incrementing and Changing the Serial Number</h2></div></div></div>
+
+
+ <p>
Zone serial numbers are just numbers — they aren't
date related. A lot of people set them to a number that
represents a date, usually of the form YYYYMMDDRR.
lower than the serial number on the master, the slave
server will attempt to update its copy of the zone.
</p>
-<p>
+
+ <p>
Setting the serial number to a lower number on the master
server than the slave server means that the slave will not perform
updates to its copy of the zone.
</p>
-<p>
+
+ <p>
The solution to this is to add 2147483647 (2^31-1) to the
number, reload the zone and make sure all slaves have updated to
the new zone serial number, then reset the number to what you want
it to be, and reload the zone again.
</p>
-</div>
-<div class="sect1" lang="en">
+
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2609009"></a>Where Can I Get Help?</h2></div></div></div>
-<p>
+<a name="id-1.9.5"></a>Where Can I Get Help?</h2></div></div></div>
+
+
+ <p>
The Internet Systems Consortium
(<acronym class="acronym">ISC</acronym>) offers a wide range
of support and service agreements for <acronym class="acronym">BIND</acronym> and <acronym class="acronym">DHCP</acronym> servers. Four
fix announcements to remote support. It also includes training in
<acronym class="acronym">BIND</acronym> and <acronym class="acronym">DHCP</acronym>.
</p>
-<p>
+
+ <p>
To discuss arrangements for support, contact
- <a href="mailto:info@isc.org" target="_top">info@isc.org</a> or visit the
+ <a class="ulink" href="mailto:info@isc.org" target="_top">info@isc.org</a> or visit the
<acronym class="acronym">ISC</acronym> web page at
- <a href="http://www.isc.org/services/support/" target="_top">http://www.isc.org/services/support/</a>
+ <a class="ulink" href="http://www.isc.org/services/support/" target="_top">http://www.isc.org/services/support/</a>
to read more.
</p>
-</div>
-</div>
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix A. Release Notes</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch08.html" title="Chapter 8. Troubleshooting">
<link rel="next" href="Bv9ARM.ch10.html" title="Appendix B. A Brief History of the DNS and BIND">
</table>
<hr>
</div>
-<div class="appendix" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch09"></a>Appendix A. Release Notes</h2></div></div></div>
-<font color="red"><xi:include></xi:include></font>
+<div class="appendix">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch09"></a>Appendix A. Release Notes</h1></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl class="toc">
+<dt><span class="section"><a href="Bv9ARM.ch09.html#id-1.10.3">Release Notes for BIND Version 9.11.0pre-alpha</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_intro">Introduction</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_download">Download</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_security">Security Fixes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_features">New Features</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_changes">Feature Changes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_port">Porting Changes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_bugs">Bug Fixes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#end_of_life">End of Life</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_thanks">Thank You</a></span></dt>
+</dl></dd>
+</dl>
</div>
+
+ <div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id-1.10.3"></a>Release Notes for BIND Version 9.11.0pre-alpha</h2></div></div></div>
+
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_intro"></a>Introduction</h3></div></div></div>
+
+ <p>
+ This document summarizes changes since the last production release
+ of BIND on the corresponding major release branch.
+ </p>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_download"></a>Download</h3></div></div></div>
+
+ <p>
+ The latest versions of BIND 9 software can always be found at
+ <a class="ulink" href="http://www.isc.org/downloads/" target="_top">http://www.isc.org/downloads/</a>.
+ There you will find additional information about each release,
+ source code, and pre-compiled versions for Microsoft Windows
+ operating systems.
+ </p>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_security"></a>Security Fixes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ An incorrect boundary check in the OPENPGPKEY rdatatype
+ could trigger an assertion failure. This flaw is disclosed
+ in CVE-2015-5986. [RT #40286]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A buffer accounting error could trigger an assertion failure
+ when parsing certain malformed DNSSEC keys.
+ </p>
+ <p>
+ This flaw was discovered by Hanno Böck of the Fuzzing
+ Project, and is disclosed in CVE-2015-5722. [RT #40212]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A specially crafted query could trigger an assertion failure
+ in message.c.
+ </p>
+ <p>
+ This flaw was discovered by Jonathan Foote, and is disclosed
+ in CVE-2015-5477. [RT #40046]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On servers configured to perform DNSSEC validation, an
+ assertion failure could be triggered on answers from
+ a specially configured server.
+ </p>
+ <p>
+ This flaw was discovered by Breno Silveira Soares, and is
+ disclosed in CVE-2015-4620. [RT #39795]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On servers configured to perform DNSSEC validation using
+ managed trust anchors (i.e., keys configured explicitly
+ via <span class="command"><strong>managed-keys</strong></span>, or implicitly
+ via <span class="command"><strong>dnssec-validation auto;</strong></span> or
+ <span class="command"><strong>dnssec-lookaside auto;</strong></span>), revoking
+ a trust anchor and sending a new untrusted replacement
+ could cause <span class="command"><strong>named</strong></span> to crash with an
+ assertion failure. This could occur in the event of a
+ botched key rollover, or potentially as a result of a
+ deliberate attack if the attacker was in position to
+ monitor the victim's DNS traffic.
+ </p>
+ <p>
+ This flaw was discovered by Jan-Piet Mens, and is
+ disclosed in CVE-2015-1349. [RT #38344]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A flaw in delegation handling could be exploited to put
+ <span class="command"><strong>named</strong></span> into an infinite loop, in which
+ each lookup of a name server triggered additional lookups
+ of more name servers. This has been addressed by placing
+ limits on the number of levels of recursion
+ <span class="command"><strong>named</strong></span> will allow (default 7), and
+ on the number of queries that it will send before
+ terminating a recursive query (default 50).
+ </p>
+ <p>
+ The recursion depth limit is configured via the
+ <code class="option">max-recursion-depth</code> option, and the query limit
+ via the <code class="option">max-recursion-queries</code> option.
+ </p>
+ <p>
+ The flaw was discovered by Florian Maury of ANSSI, and is
+ disclosed in CVE-2014-8500. [RT #37580]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Two separate problems were identified in BIND's GeoIP code that
+ could lead to an assertion failure. One was triggered by use of
+ both IPv4 and IPv6 address families, the other by referencing
+ a GeoIP database in <code class="filename">named.conf</code> which was
+ not installed. Both are covered by CVE-2014-8680. [RT #37672]
+ [RT #37679]
+ </p>
+ <p>
+ A less serious security flaw was also found in GeoIP: changes
+ to the <span class="command"><strong>geoip-directory</strong></span> option in
+ <code class="filename">named.conf</code> were ignored when running
+ <span class="command"><strong>rndc reconfig</strong></span>. In theory, this could allow
+ <span class="command"><strong>named</strong></span> to allow access to unintended clients.
+ </p>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_features"></a>New Features</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ Added support for DynDB, a new interface for loading zone data
+ from an external database, developed by Red Hat for the FreeIPA
+ project. (Thanks in particular to Adam Tkac and Petr
+ Spacek of Red Hat for the contribution.)
+ </p>
+ <p>
+ Unlike the existing DLZ and SDB interfaces, which provide a
+ limited subset of database functionality within BIND —
+ translating DNS queries into real-time database lookups with
+ relatively poor performance and with no ability to handle
+ DNSSEC-signed data — DynDB is able to fully implement
+ and extend the database API used natively by BIND.
+ </p>
+ <p>
+ A DynDB module could pre-load data from an external data
+ source, then serve it with the same performance and
+ functionality as conventional BIND zones, and with the
+ ability to take advantage of database features not
+ available in BIND, such as multi-master replication.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ New quotas have been added to limit the queries that are
+ sent by recursive resolvers to authoritative servers
+ experiencing denial-of-service attacks. When configured,
+ these options can both reduce the harm done to authoritative
+ servers and also avoid the resource exhaustion that can be
+ experienced by recursives when they are being used as a
+ vehicle for such an attack.
+ </p>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
+<li class="listitem">
+ <p>
+ <code class="option">fetches-per-server</code> limits the number of
+ simultaneous queries that can be sent to any single
+ authoritative server. The configured value is a starting
+ point; it is automatically adjusted downward if the server is
+ partially or completely non-responsive. The algorithm used to
+ adjust the quota can be configured via the
+ <code class="option">fetch-quota-params</code> option.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <code class="option">fetches-per-zone</code> limits the number of
+ simultaneous queries that can be sent for names within a
+ single domain. (Note: Unlike "fetches-per-server", this
+ value is not self-tuning.)
+ </p>
+ </li>
+</ul></div>
+ <p>
+ Statistics counters have also been added to track the number
+ of queries affected by these quotas.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Added support for <span class="command"><strong>dnstap</strong></span>, a fast,
+ flexible method for capturing and logging DNS traffic,
+ developed by Robert Edmonds at Farsight Security, Inc.,
+ whose assistance is gratefully acknowledged.
+ </p>
+ <p>
+ To enable <span class="command"><strong>dnstap</strong></span> at compile time,
+ the <span class="command"><strong>fstrm</strong></span> and <span class="command"><strong>protobuf-c</strong></span>
+ libraries must be available, and BIND must be configured with
+ <code class="option">--enable-dnstap</code>.
+ </p>
+ <p>
+ A new utility <span class="command"><strong>dnstap-read</strong></span> has been added
+ to allow <span class="command"><strong>dnstap</strong></span> data to be presented in
+ a human-readable format.
+ </p>
+ <p>
+ For more information on <span class="command"><strong>dnstap</strong></span>, see
+ <a class="ulink" href="http://dnstap.info" target="_top">http://dnstap.info</a>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ New statistics counters have been added to track traffic
+ sizes, as specified in RSSAC002. Query and response
+ message sizes are broken up into ranges of histogram buckets:
+ TCP and UDP queries of size 0-15, 16-31, ..., 272-288, and 288+,
+ and TCP and UDP responses of size 0-15, 16-31, ..., 4080-4095,
+ and 4096+. These values can be accessed via the XML and JSON
+ statistics channels at, for example,
+ <a class="ulink" href="http://localhost:8888/xml/v3/traffic" target="_top">http://localhost:8888/xml/v3/traffic</a>
+ or
+ <a class="ulink" href="http://localhost:8888/json/v1/traffic" target="_top">http://localhost:8888/json/v1/traffic</a>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The serial number of a dynamically updatable zone can
+ now be set using
+ <span class="command"><strong>rndc signing -serial <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>zonename</code></em></strong></span>.
+ This is particularly useful with <code class="option">inline-signing</code>
+ zones that have been reset. Setting the serial number to a value
+ larger than that on the slaves will trigger an AXFR-style
+ transfer.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When answering recursive queries, SERVFAIL responses can now be
+ cached by the server for a limited time; subsequent queries for
+ the same query name and type will return another SERVFAIL until
+ the cache times out. This reduces the frequency of retries
+ when a query is persistently failing, which can be a burden
+ on recursive serviers. The SERVFAIL cache timeout is controlled
+ by <code class="option">servfail-ttl</code>, which defaults to 10 seconds
+ and has an upper limit of 30.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The new <span class="command"><strong>rndc nta</strong></span> command can now be used to
+ set a "negative trust anchor" (NTA), disabling DNSSEC validation for
+ a specific domain; this can be used when responses from a domain
+ are known to be failing validation due to administrative error
+ rather than because of a spoofing attack. NTAs are strictly
+ temporary; by default they expire after one hour, but can be
+ configured to last up to one week. The default NTA lifetime
+ can be changed by setting the <code class="option">nta-lifetime</code> in
+ <code class="filename">named.conf</code>. When added, NTAs are stored in a
+ file (<code class="filename"><em class="replaceable"><code>viewname</code></em>.nta</code>)
+ in order to persist across restarts of the <span class="command"><strong>named</strong></span> server.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The EDNS Client Subnet (ECS) option is now supported for
+ authoritative servers; if a query contains an ECS option then
+ ACLs containing <code class="option">geoip</code> or <code class="option">ecs</code>
+ elements can match against the the address encoded in the option.
+ This can be used to select a view for a query, so that different
+ answers can be provided depending on the client network.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The EDNS EXPIRE option has been implemented on the client
+ side, allowing a slave server to set the expiration timer
+ correctly when transferring zone data from another slave
+ server.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A new <code class="option">masterfile-style</code> zone option controls
+ the formatting of text zone files: When set to
+ <code class="literal">full</code>, the zone file will dumped in
+ single-line-per-record format.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +ednsopt</strong></span> can now be used to set
+ arbitrary EDNS options in DNS requests.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +ednsflags</strong></span> can now be used to set
+ yet-to-be-defined EDNS flags in DNS requests.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +[no]ednsnegotiation</strong></span> can now be used enable /
+ disable EDNS version negotiation.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +header-only</strong></span> can now be used to send
+ queries without a question section.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +ttlunits</strong></span> causes <span class="command"><strong>dig</strong></span>
+ to print TTL values with time-unit suffixes: w, d, h, m, s for
+ weeks, days, hours, minutes, and seconds.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +zflag</strong></span> can be used to set the last
+ unassigned DNS header flag bit. This bit in normally zero.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +dscp=<em class="replaceable"><code>value</code></em></strong></span>
+ can now be used to set the DSCP code point in outgoing query
+ packets.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <code class="option">serial-update-method</code> can now be set to
+ <code class="literal">date</code>. On update, the serial number will
+ be set to the current date in YYYYMMDDNN format.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dnssec-signzone -N date</strong></span> also sets the serial
+ number to YYYYMMDDNN.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>named -L <em class="replaceable"><code>filename</code></em></strong></span>
+ causes <span class="command"><strong>named</strong></span> to send log messages to the specified file by
+ default instead of to the system log.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The rate limiter configured by the
+ <code class="option">serial-query-rate</code> option no longer covers
+ NOTIFY messages; those are now separately controlled by
+ <code class="option">notify-rate</code> and
+ <code class="option">startup-notify-rate</code> (the latter of which
+ controls the rate of NOTIFY messages sent when the server
+ is first started up or reconfigured).
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The default number of tasks and client objects available
+ for serving lightweight resolver queries have been increased,
+ and are now configurable via the new <code class="option">lwres-tasks</code>
+ and <code class="option">lwres-clients</code> options in
+ <code class="filename">named.conf</code>. [RT #35857]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Log output to files can now be buffered by specifying
+ <span class="command"><strong>buffered yes;</strong></span> when creating a channel.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>delv +tcp</strong></span> will exclusively use TCP when
+ sending queries.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>named</strong></span> will now check to see whether
+ other name server processes are running before starting up.
+ This is implemented in two ways: 1) by refusing to start
+ if the configured network interfaces all return "address
+ in use", and 2) by attempting to acquire a lock on a file
+ specified by the <code class="option">lock-file</code> option or
+ the <span class="command"><strong>-X</strong></span> command line option. The
+ default lock file is
+ <code class="filename">/var/run/named/named.lock</code>.
+ Specifying <code class="literal">none</code> will disable the lock
+ file check.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>rndc delzone</strong></span> can now be applied to zones
+ which were configured in <code class="filename">named.conf</code>;
+ it is no longer restricted to zones which were added by
+ <span class="command"><strong>rndc addzone</strong></span>. (Note, however, that
+ this does not edit <code class="filename">named.conf</code>; the zone
+ must be removed from the configuration or it will return
+ when <span class="command"><strong>named</strong></span> is restarted or reloaded.)
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>rndc modzone</strong></span> can be used to reconfigure
+ a zone, using similar syntax to <span class="command"><strong>rndc addzone</strong></span>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>rndc showzone</strong></span> displays the current
+ configuration for a specified zone.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Added server-side support for pipelined TCP queries. Clients
+ may continue sending queries via TCP while previous queries are
+ processed in parallel. Responses are sent when they are
+ ready, not necessarily in the order in which the queries were
+ received.
+ </p>
+ <p>
+ To revert to the former behavior for a particular
+ client address or range of addresses, specify the address prefix
+ in the "keep-response-order" option. To revert to the former
+ behavior for all clients, use "keep-response-order { any; };".
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The new <span class="command"><strong>mdig</strong></span> command is a version of
+ <span class="command"><strong>dig</strong></span> that sends multiple pipelined
+ queries and then waits for responses, instead of sending one
+ query and waiting the response before sending the next. [RT #38261]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ To enable better monitoring and troubleshooting of RFC 5011
+ trust anchor management, the new <span class="command"><strong>rndc managed-keys</strong></span>
+ can be used to check status of trust anchors or to force keys
+ to be refreshed. Also, the managed-keys data file now has
+ easier-to-read comments. [RT #38458]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ An <span class="command"><strong>--enable-querytrace</strong></span> configure switch is
+ now available to enable very verbose query tracelogging. This
+ option can only be set at compile time. This option has a
+ negative performance impact and should be used only for
+ debugging. [RT #37520]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A new <span class="command"><strong>tcp-only</strong></span> option can be specified
+ in <span class="command"><strong>server</strong></span> statements to force
+ <span class="command"><strong>named</strong></span> to connect to the specified
+ server via TCP. [RT #37800]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The <span class="command"><strong>nxdomain-redirect</strong></span> option specifies
+ a DNS namespace to use for NXDOMAIN redirection. When a
+ recursive lookup returns NXDOMAIN, a second lookup is
+ initiated with the specified name appended to the query
+ name. This allows NXDOMAIN redirection data to be supplied
+ by multiple zones configured on the server or by recursive
+ queries to other servers. (The older method, using
+ a single <span class="command"><strong>type redirect</strong></span> zone, has
+ better average performance but is less flexible.) [RT #37989]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The following types have been implemented: CSYNC, NINFO, RKEY,
+ SINK, TA, TALINK.
+ </p>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_changes"></a>Feature Changes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ ACLs containing <span class="command"><strong>geoip asnum</strong></span> elements were
+ not correctly matched unless the full organization name was
+ specified in the ACL (as in
+ <span class="command"><strong>geoip asnum "AS1234 Example, Inc.";</strong></span>).
+ They can now match against the AS number alone (as in
+ <span class="command"><strong>geoip asnum "AS1234";</strong></span>).
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When using native PKCS#11 cryptography (i.e.,
+ <span class="command"><strong>configure --enable-native-pkcs11</strong></span>) HSM PINs
+ of up to 256 characters can now be used.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ NXDOMAIN responses to queries of type DS are now cached separately
+ from those for other types. This helps when using "grafted" zones
+ of type forward, for which the parent zone does not contain a
+ delegation, such as local top-level domains. Previously a query
+ of type DS for such a zone could cause the zone apex to be cached
+ as NXDOMAIN, blocking all subsequent queries. (Note: This
+ change is only helpful when DNSSEC validation is not enabled.
+ "Grafted" zones without a delegation in the parent are not a
+ recommended configuration.)
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Update forwarding performance has been improved by allowing
+ a single TCP connection to be shared between multiple updates.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ By default, <span class="command"><strong>nsupdate</strong></span> will now check
+ the correctness of hostnames when adding records of type
+ A, AAAA, MX, SOA, NS, SRV or PTR. This behavior can be
+ disabled with <span class="command"><strong>check-names no</strong></span>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Added support for OPENPGPKEY type.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The names of the files used to store managed keys and added
+ zones for each view are no longer based on the SHA256 hash
+ of the view name, except when this is necessary because the
+ view name contains characters that would be incompatible with use
+ as a file name. For views whose names do not contain forward
+ slashes ('/'), backslashes ('\'), or capital letters - which
+ could potentially cause namespace collision problems on
+ case-insensitive filesystems - files will now be named
+ after the view (for example, <code class="filename">internal.mkeys</code>
+ or <code class="filename">external.nzf</code>). However, to ensure
+ consistent behavior when upgrading, if a file using the old
+ name format is found to exist, it will continue to be used.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ "rndc" can now return text output of arbitrary size to
+ the caller. (Prior to this, certain commands such as
+ "rndc tsig-list" and "rndc zonestatus" could return
+ truncated output.)
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Errors reported when running <span class="command"><strong>rndc addzone</strong></span>
+ (e.g., when a zone file cannot be loaded) have been clarified
+ to make it easier to diagnose problems.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When encountering an authoritative name server whose name is
+ an alias pointing to another name, the resolver treats
+ this as an error and skips to the next server. Previously
+ this happened silently; now the error will be logged to
+ the newly-created "cname" log category.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ If <span class="command"><strong>named</strong></span> is not configured to validate the answer then
+ allow fallback to plain DNS on timeout even when we know
+ the server supports EDNS. This will allow the server to
+ potentially resolve signed queries when TCP is being
+ blocked.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Large inline-signing changes should be less disruptive.
+ Signature generation is now done incrementally; the number
+ of signatures to be generated in each quantum is controlled
+ by "sig-signing-signatures <em class="replaceable"><code>number</code></em>;".
+ [RT #37927]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The experimental SIT option (code point 65001) of BIND
+ 9.10.0 through BIND 9.10.2 has been replaced with the COOKIE
+ option (code point 10). It is no longer experimental, and
+ is sent by default, by both <span class="command"><strong>named</strong></span> and
+ <span class="command"><strong>dig</strong></span>.
+ </p>
+ <p>
+ The SIT-related named.conf options have been marked as
+ obsolete, and are otherwise ignored.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When <span class="command"><strong>dig</strong></span> receives a truncated (TC=1)
+ response or a BADCOOKIE response code from a server, it
+ will automatically retry the query using the server COOKIE
+ that was returned by the server in its initial response.
+ [RT #39047]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A alternative NXDOMAIN redirect method (nxdomain-redirect)
+ which allows the redirect information to be looked up from
+ a namespace on the Internet rather than requiring a zone
+ to be configured on the server is now available.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Retrieving the local port range from net.ipv4.ip_local_port_range
+ on Linux is now supported.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Within the <code class="option">response-policy</code> option, it is now
+ possible to configure RPZ rewrite logging on a per-zone basis
+ using the <code class="option">log</code> clause.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The default preferred glue is now the address type of the
+ transport the query was received over.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On machines with 2 or more processors (CPU), the default value
+ for the number of UDP listeners has been changed to the number
+ of detected processors minus one.
+ </p>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_port"></a>Porting Changes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ <p>
+ The Microsoft Windows install tool
+ <span class="command"><strong>BINDInstall.exe</strong></span> which requires a
+ non-free version of Visual Studio to be built, now uses two
+ files (lists of flags and files) created by the Configure
+ perl script with all the needed information which were
+ previously compiled in the binary. Read
+ <code class="filename">win32utils/build.txt</code> for more details.
+ [RT #38915]
+ </p>
+ </li></ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_bugs"></a>Bug Fixes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig</strong></span>, <span class="command"><strong>host</strong></span> and
+ <span class="command"><strong>nslookup</strong></span> aborted when encountering
+ a name which, after appending search list elements,
+ exceeded 255 bytes. Such names are now skipped, but
+ processing of other names will continue. [RT #36892]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The error message generated when
+ <span class="command"><strong>named-checkzone</strong></span> or
+ <span class="command"><strong>named-checkconf -z</strong></span> encounters a
+ <code class="option">$TTL</code> directive without a value has
+ been clarified. [RT #37138]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Semicolon characters (;) included in TXT records were
+ incorrectly escaped with a backslash when the record was
+ displayed as text. This is actually only necessary when there
+ are no quotation marks. [RT #37159]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When files opened for writing by <span class="command"><strong>named</strong></span>,
+ such as zone journal files, were referenced more than once
+ in <code class="filename">named.conf</code>, it could lead to file
+ corruption as multiple threads wrote to the same file. This
+ is now detected when loading <code class="filename">named.conf</code>
+ and reported as an error. [RT #37172]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When checking for updates to trust anchors listed in
+ <code class="option">managed-keys</code>, <span class="command"><strong>named</strong></span>
+ now revalidates keys based on the current set of
+ active trust anchors, without relying on any cached
+ record of previous validation. [RT #37506]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Large-system tuning
+ (<span class="command"><strong>configure --with-tuning=large</strong></span>) caused
+ problems on some platforms by setting a socket receive
+ buffer size that was too large. This is now detected and
+ corrected at run time. [RT #37187]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When NXDOMAIN redirection is in use, queries for a name
+ that is present in the redirection zone but a type that
+ is not present will now return NOERROR instead of NXDOMAIN.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Due to an inadvertent removal of code in the previous
+ release, when <span class="command"><strong>named</strong></span> encountered an
+ authoritative name server which dropped all EDNS queries,
+ it did not always try plain DNS. This has been corrected.
+ [RT #37965]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A regression caused nsupdate to use the default recursive servers
+ rather than the SOA MNAME server when sending the UPDATE.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Adjusted max-recursion-queries to accommodate the smaller
+ initial packet sizes used in BIND 9.10 and higher when
+ contacting authoritative servers for the first time.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Built-in "empty" zones did not correctly inherit the
+ "allow-transfer" ACL from the options or view. [RT #38310]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Two leaks were fixed that could cause <span class="command"><strong>named</strong></span>
+ processes to grow to very large sizes. [RT #38454]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Fixed some bugs in RFC 5011 trust anchor management,
+ including a memory leak and a possible loss of state
+ information. [RT #38458]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Asynchronous zone loads were not handled correctly when the
+ zone load was already in progress; this could trigger a crash
+ in zt.c. [RT #37573]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A race during shutdown or reconfiguration could
+ cause an assertion failure in mem.c. [RT #38979]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Some answer formatting options didn't work correctly with
+ <span class="command"><strong>dig +short</strong></span>. [RT #39291]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Several bugs have been fixed in the RPZ implementation:
+ </p>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
+<li class="listitem">
+ <p>
+ Policy zones that did not specifically require recursion
+ could be treated as if they did; consequently, setting
+ <span class="command"><strong>qname-wait-recurse no;</strong></span> was
+ sometimes ineffective. This has been corrected.
+ In most configurations, behavioral changes due to this
+ fix will not be noticeable. [RT #39229]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The server could crash if policy zones were updated (e.g.
+ via <span class="command"><strong>rndc reload</strong></span> or an incoming zone
+ transfer) while RPZ processing was still ongoing for an
+ active query. [RT #39415]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On servers with one or more policy zones configured as
+ slaves, if a policy zone updated during regular operation
+ (rather than at startup) using a full zone reload, such as
+ via AXFR, a bug could allow the RPZ summary data to fall out
+ of sync, potentially leading to an assertion failure in
+ rpz.c when further incremental updates were made to the
+ zone, such as via IXFR. [RT #39567]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The server could match a shorter prefix than what was
+ available in CLIENT-IP policy triggers, and so, an
+ unexpected action could be taken. This has been
+ corrected. [RT #39481]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The server could crash if a reload of an RPZ zone was
+ initiated while another reload of the same zone was
+ already in progress. [RT #39649]
+ </p>
+ </li>
+</ul></div>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="end_of_life"></a>End of Life</h3></div></div></div>
+
+ <p>
+ The end of life for BIND 9.11 is yet to be determined but
+ will not be before BIND 9.13.0 has been released for 6 months.
+ <a class="ulink" href="https://www.isc.org/downloads/software-support-policy/" target="_top">https://www.isc.org/downloads/software-support-policy/</a>
+ </p>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_thanks"></a>Thank You</h3></div></div></div>
+
+ <p>
+ Thank you to everyone who assisted us in making this release possible.
+ If you would like to contribute to ISC to assist us in continuing to
+ make quality open source software, please visit our donations page at
+ <a class="ulink" href="http://www.isc.org/donate/" target="_top">http://www.isc.org/donate/</a>.
+ </p>
+ </div>
+</div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix B. A Brief History of the DNS and BIND</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch09.html" title="Appendix A. Release Notes">
<link rel="next" href="Bv9ARM.ch11.html" title="Appendix C. General DNS Reference Information">
</table>
<hr>
</div>
-<div class="appendix" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
+<div class="appendix">
+<div class="titlepage"><div><div><h1 class="title">
<a name="Bv9ARM.ch10"></a>Appendix B. A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym>
-</h2></div></div></div>
-<p><a name="historical_dns_information"></a>
+</h1></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl class="toc">
+<dt><span class="section"><a href="Bv9ARM.ch10.html#dns_history">DNS</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch10.html#bind_history">BIND</a></span></dt>
+</dl>
+</div>
+
+ <div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="dns_history"></a>DNS</h2></div></div></div>
+ <p>
Although the "official" beginning of the Domain Name
System occurred in 1984 with the publication of RFC 920, the
core of the new system was described in 1983 in RFCs 882 and
became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are
built.
</p>
-<p>
+
+ <p>
The first working domain name server, called "Jeeves", was
written in 1983-84 by Paul Mockapetris for operation on DEC
Tops-20
Administration
(DARPA).
</p>
-<p>
+ </div>
+
+ <div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="bind_history"></a>BIND</h2></div></div></div>
+ <p>
Versions of <acronym class="acronym">BIND</acronym> through
4.8.3 were maintained by the Computer
Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently
handled by Mike Karels and Øivind Kure.
</p>
-<p>
<acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were
released by Digital Equipment
Corporation (now Compaq Computer Corporation). Paul Vixie, then
Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
Wolfhugel, and others.
</p>
-<p>
In 1994, <acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by
Vixie Enterprises. Paul
Vixie became <acronym class="acronym">BIND</acronym>'s principal
architect/programmer.
</p>
-<p>
<acronym class="acronym">BIND</acronym> versions from 4.9.3 onward
have been developed and maintained
by the Internet Systems Consortium and its predecessor,
the Internet Software Consortium, with support being provided
by ISC's sponsors.
</p>
-<p>
As co-architects/programmers, Bob Halley and
Paul Vixie released the first production-ready version of
<acronym class="acronym">BIND</acronym> version 8 in May 1997.
</p>
-<p>
BIND version 9 was released in September 2000 and is a
major rewrite of nearly all aspects of the underlying
BIND architecture.
</p>
-<p>
BIND versions 4 and 8 are officially deprecated.
No additional development is done
on BIND version 4 or BIND version 8.
</p>
-<p>
<acronym class="acronym">BIND</acronym> development work is made
possible today by the sponsorship
of several corporations, and by the tireless work efforts of
numerous individuals.
</p>
-</div>
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix C. General DNS Reference Information</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch10.html" title="Appendix B. A Brief History of the DNS and BIND">
<link rel="next" href="Bv9ARM.ch12.html" title="Appendix D. BIND 9 DNS Library Support">
</table>
<hr>
</div>
-<div class="appendix" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch11"></a>Appendix C. General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div>
+<div class="appendix">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch11"></a>Appendix C. General <acronym class="acronym">DNS</acronym> Reference Information</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch11.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch11.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
+<dl class="toc">
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
<dd><dl>
-<dt><span class="sect
2"><a href="Bv9ARM.ch11.html#rfcs">Request for Comments (RFCs)</a></span></dt>
-<dt><span class="sect
2"><a href="Bv9ARM.ch11.html#internet_drafts">Internet Drafts</a></span></dt>
-<dt><span class="sect
2"><a href="Bv9ARM.ch11.html#id2612661">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#rfcs">Request for Comments (RFCs)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#internet_drafts">Internet Drafts</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#id-1.12.4.5">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
</dl></dd>
</dl>
</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h2></div></div></div>
-<p>
+
+ <p>
IPv6 addresses are 128-bit identifiers for interfaces and
sets of interfaces which were introduced in the <acronym class="acronym">DNS</acronym> to facilitate
scalable Internet routing. There are three types of addresses: <span class="emphasis"><em>Unicast</em></span>,
Unicast address scheme. For more information, see RFC 3587,
"Global Unicast Address Format."
</p>
-<p>
IPv6 unicast addresses consist of a
<span class="emphasis"><em>global routing prefix</em></span>, a
<span class="emphasis"><em>subnet identifier</em></span>, and an
<span class="emphasis"><em>interface identifier</em></span>.
</p>
-<p>
The global routing prefix is provided by the
upstream provider or ISP, and (roughly) corresponds to the
IPv4 <span class="emphasis"><em>network</em></span> section
interface on a given network; in IPv6, addresses belong to
interfaces rather than to machines.
</p>
-<p>
The subnetting capability of IPv6 is much more flexible than
that of IPv4: subnetting can be carried out on bit boundaries,
in much the same way as Classless InterDomain Routing
(CIDR), and the DNS PTR representation ("nibble" format)
makes setting up reverse zones easier.
</p>
-<p>
The Interface Identifier must be unique on the local link,
and is usually generated automatically by the IPv6
implementation, although it is usually possible to
override the default setting if necessary. A typical IPv6
address might look like:
- <span><strong class="command">2001:db8:201:9:a00:20ff:fe81:2b32</strong></span>
+ <span class="command"><strong>2001:db8:201:9:a00:20ff:fe81:2b32</strong></span>
</p>
-<p>
IPv6 address specifications often contain long strings
of zeros, so the architects have included a shorthand for
specifying
string
of zeros that can fit, and can be used only once in an address.
</p>
-</div>
-<div class="sect1" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="bibliography"></a>Bibliography (and Suggested Reading)</h2></div></div></div>
-<div class="sect2" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="rfcs"></a>Request for Comments (RFCs)</h3></div></div></div>
-<p>
+
+ <p>
Specification documents for the Internet protocol suite, including
the <acronym class="acronym">DNS</acronym>, are published as part of
the Request for Comments (RFCs)
by the Internet Engineering Task Force (IETF) and the Internet
Engineering Steering Group (IESG). RFCs can be obtained online via FTP at:
</p>
-<p>
- <a href="ftp://www.isi.edu/in-notes/" target="_top">
+ <a class="ulink" href="ftp://www.isi.edu/in-notes/" target="_top">
ftp://www.isi.edu/in-notes/RFC<em class="replaceable"><code>xxxx</code></em>.txt
</a>
</p>
-<p>
(where <em class="replaceable"><code>xxxx</code></em> is
the number of the RFC). RFCs are also available via the Web at:
</p>
-<p>
- <a href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>.
+ <a class="ulink" href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>.
</p>
-<div class="bibliography">
+
<div class="bibliography">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2609637"></a>Bibliography</h4></div></div></div>
-<div class="bibliodiv">
-<h3 class="title">Standards</h3>
-<div class="biblioentry">
-<a name="id2609648"></a><p>[<abbr class="abbrev">RFC974</abbr>] <span class="author"><span class="firstname">C.</span> <span class="surname">Partridge</span>. </span><span class="title"><i>Mail Routing and the Domain System</i>. </span><span class="pubdate">January 1986. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609671"></a><p>[<abbr class="abbrev">RFC1034</abbr>] <span class="author"><span class="firstname">P.V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names — Concepts and Facilities</i>. </span><span class="pubdate">November 1987. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609694"></a><p>[<abbr class="abbrev">RFC1035</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names — Implementation and
- Specification</i>. </span><span class="pubdate">November 1987. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
+<a name="id-1.12.4.3.7"></a>Bibliography</h4></div></div></div>
+ <div class="bibliodiv">
+<h3 class="title">
+<a name="id-1.12.4.3.7.1"></a>Standards</h3>
+
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.1.3"></a><p>[<abbr class="abbrev">RFC974</abbr>]
+
+ <span class="author"><span class="firstname">C.</span> <span class="surname">Partridge</span>. </span>
+ <span class="citetitle"><em class="citetitle">Mail Routing and the Domain System</em>. </span>
+ <span class="pubdate">January 1986. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.1.4"></a><p>[<abbr class="abbrev">RFC1034</abbr>]
+
+ <span class="author"><span class="firstname">P.V.</span> <span class="surname">Mockapetris</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Names — Concepts and Facilities</em>. </span>
+ <span class="pubdate">November 1987. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.1.5"></a><p>[<abbr class="abbrev">RFC1035</abbr>]
+
+ <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span> <span class="citetitle"><em class="citetitle">Domain Names — Implementation and
+ Specification</em>. </span>
+ <span class="pubdate">November 1987. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
<h3 class="title">
<a name="proposed_standards"></a>Proposed Standards</h3>
-<div class="biblioentry">
-<a name="id2609731"></a><p>[<abbr class="abbrev">RFC2181</abbr>] <span class="author"><span class="firstname">R., R. Bush</span> <span class="surname">Elz</span>. </span><span class="title"><i>Clarifications to the <acronym class="acronym">DNS</acronym>
- Specification</i>. </span><span class="pubdate">July 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609757"></a><p>[<abbr class="abbrev">RFC2308</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Andrews</span>. </span><span class="title"><i>Negative Caching of <acronym class="acronym">DNS</acronym>
- Queries</i>. </span><span class="pubdate">March 1998. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609783"></a><p>[<abbr class="abbrev">RFC1995</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Ohta</span>. </span><span class="title"><i>Incremental Zone Transfer in <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">August 1996. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609808"></a><p>[<abbr class="abbrev">RFC1996</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A Mechanism for Prompt Notification of Zone Changes</i>. </span><span class="pubdate">August 1996. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609831"></a><p>[<abbr class="abbrev">RFC2136</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">Y.</span> <span class="surname">Rekhter</span>, and <span class="firstname">J.</span> <span class="surname">Bound</span>. </span><span class="title"><i>Dynamic Updates in the Domain Name System</i>. </span><span class="pubdate">April 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609886"></a><p>[<abbr class="abbrev">RFC2671</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Extension Mechanisms for DNS (EDNS0)</i>. </span><span class="pubdate">August 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2609981"></a><p>[<abbr class="abbrev">RFC2672</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span><span class="title"><i>Non-Terminal DNS Name Redirection</i>. </span><span class="pubdate">August 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610008"></a><p>[<abbr class="abbrev">RFC2845</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>, <span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, and <span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Secret Key Transaction Authentication for <acronym class="acronym">DNS</acronym> (TSIG)</i>. </span><span class="pubdate">May 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610070"></a><p>[<abbr class="abbrev">RFC2930</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Secret Key Establishment for DNS (TKEY RR)</i>. </span><span class="pubdate">September 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610100"></a><p>[<abbr class="abbrev">RFC2931</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>DNS Request and Transaction Signatures (SIG(0)s)</i>. </span><span class="pubdate">September 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610130"></a><p>[<abbr class="abbrev">RFC3007</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Secure Domain Name System (DNS) Dynamic Update</i>. </span><span class="pubdate">November 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610156"></a><p>[<abbr class="abbrev">RFC3645</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Kwan</span>, <span class="firstname">P.</span> <span class="surname">Garg</span>, <span class="firstname">J.</span> <span class="surname">Gilroy</span>, <span class="firstname">L.</span> <span class="surname">Esibov</span>, <span class="firstname">J.</span> <span class="surname">Westhead</span>, and <span class="firstname">R.</span> <span class="surname">Hall</span>. </span><span class="title"><i>Generic Security Service Algorithm for Secret
+
+
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.3"></a><p>[<abbr class="abbrev">RFC2181</abbr>]
+
+ <span class="author"><span class="firstname">R., R. Bush</span> <span class="surname">Elz</span>. </span>
+ <span class="citetitle"><em class="citetitle">Clarifications to the <acronym class="acronym">DNS</acronym>
+ Specification</em>. </span>
+ <span class="pubdate">July 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.4"></a><p>[<abbr class="abbrev">RFC2308</abbr>]
+
+ <span class="author"><span class="firstname">M.</span> <span class="surname">Andrews</span>. </span>
+ <span class="citetitle"><em class="citetitle">Negative Caching of <acronym class="acronym">DNS</acronym>
+ Queries</em>. </span>
+ <span class="pubdate">March 1998. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.5"></a><p>[<abbr class="abbrev">RFC1995</abbr>]
+
+ <span class="author"><span class="firstname">M.</span> <span class="surname">Ohta</span>. </span>
+ <span class="citetitle"><em class="citetitle">Incremental Zone Transfer in <acronym class="acronym">DNS</acronym></em>. </span>
+ <span class="pubdate">August 1996. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.6"></a><p>[<abbr class="abbrev">RFC1996</abbr>]
+
+ <span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span>
+ <span class="citetitle"><em class="citetitle">A Mechanism for Prompt Notification of Zone Changes</em>. </span>
+ <span class="pubdate">August 1996. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.7"></a><p>[<abbr class="abbrev">RFC2136</abbr>]
+
+ <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">Y.</span> <span class="surname">Rekhter</span>, and <span class="firstname">J.</span> <span class="surname">Bound</span>. </span>
+ <span class="citetitle"><em class="citetitle">Dynamic Updates in the Domain Name System</em>. </span>
+ <span class="pubdate">April 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.8"></a><p>[<abbr class="abbrev">RFC2671</abbr>]
+
+ <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span>
+ <span class="citetitle"><em class="citetitle">Extension Mechanisms for DNS (EDNS0)</em>. </span>
+ <span class="pubdate">August 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.9"></a><p>[<abbr class="abbrev">RFC2672</abbr>]
+
+ <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span>
+ <span class="citetitle"><em class="citetitle">Non-Terminal DNS Name Redirection</em>. </span>
+ <span class="pubdate">August 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.10"></a><p>[<abbr class="abbrev">RFC2845</abbr>]
+
+ <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>, <span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, and <span class="firstname">B.</span> <span class="surname">Wellington</span>. </span>
+ <span class="citetitle"><em class="citetitle">Secret Key Transaction Authentication for <acronym class="acronym">DNS</acronym> (TSIG)</em>. </span>
+ <span class="pubdate">May 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.11"></a><p>[<abbr class="abbrev">RFC2930</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">Secret Key Establishment for DNS (TKEY RR)</em>. </span>
+ <span class="pubdate">September 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.12"></a><p>[<abbr class="abbrev">RFC2931</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">DNS Request and Transaction Signatures (SIG(0)s)</em>. </span>
+ <span class="pubdate">September 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.13"></a><p>[<abbr class="abbrev">RFC3007</abbr>]
+
+ <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span>
+ <span class="citetitle"><em class="citetitle">Secure Domain Name System (DNS) Dynamic Update</em>. </span>
+ <span class="pubdate">November 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.2.14"></a><p>[<abbr class="abbrev">RFC3645</abbr>]
+
+ <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Kwan</span>, <span class="firstname">P.</span> <span class="surname">Garg</span>, <span class="firstname">J.</span> <span class="surname">Gilroy</span>, <span class="firstname">L.</span> <span class="surname">Esibov</span>, <span class="firstname">J.</span> <span class="surname">Westhead</span>, and <span class="firstname">R.</span> <span class="surname">Hall</span>. </span>
+ <span class="citetitle"><em class="citetitle">Generic Security Service Algorithm for Secret
Key Transaction Authentication for DNS
- (GSS-TSIG)</i>. </span><span class="pubdate">October 2003. </span></p>
+ (GSS-TSIG)</em>. </span>
+ <span class="pubdate">October 2003. </span>
+ </p>
</div>
-</div>
-<div class="bibliodiv">
+ </div>
+
<div class="bibliodiv">
<h3 class="title">
-<acronym class="acronym">DNS</acronym> Security Proposed Standards</h3>
-<div class="biblioentry">
-<a name="id2610238"></a><p>[<abbr class="abbrev">RFC3225</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Conrad</span>. </span><span class="title"><i>Indicating Resolver Support of DNSSEC</i>. </span><span class="pubdate">December 2001. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610265"></a><p>[<abbr class="abbrev">RFC3833</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Atkins</span> and <span class="firstname">R.</span> <span class="surname">Austein</span>. </span><span class="title"><i>Threat Analysis of the Domain Name System (DNS)</i>. </span><span class="pubdate">August 2004. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610301"></a><p>[<abbr class="abbrev">RFC4033</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>DNS Security Introduction and Requirements</i>. </span><span class="pubdate">March 2005. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610366"></a><p>[<abbr class="abbrev">RFC4034</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Resource Records for the DNS Security Extensions</i>. </span><span class="pubdate">March 2005. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610432"></a><p>[<abbr class="abbrev">RFC4035</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Protocol Modifications for the DNS
- Security Extensions</i>. </span><span class="pubdate">March 2005. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
-<h3 class="title">Other Important RFCs About <acronym class="acronym">DNS</acronym>
+<a name="id-1.12.4.3.7.3"></a><acronym class="acronym">DNS</acronym> Security Proposed Standards</h3>
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.3.3"></a><p>[<abbr class="abbrev">RFC3225</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Conrad</span>. </span>
+ <span class="citetitle"><em class="citetitle">Indicating Resolver Support of DNSSEC</em>. </span>
+ <span class="pubdate">December 2001. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.3.4"></a><p>[<abbr class="abbrev">RFC3833</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Atkins</span> and <span class="firstname">R.</span> <span class="surname">Austein</span>. </span>
+ <span class="citetitle"><em class="citetitle">Threat Analysis of the Domain Name System (DNS)</em>. </span>
+ <span class="pubdate">August 2004. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.3.5"></a><p>[<abbr class="abbrev">RFC4033</abbr>]
+
+ <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span>
+ <span class="citetitle"><em class="citetitle">DNS Security Introduction and Requirements</em>. </span>
+ <span class="pubdate">March 2005. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.3.6"></a><p>[<abbr class="abbrev">RFC4034</abbr>]
+
+ <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span>
+ <span class="citetitle"><em class="citetitle">Resource Records for the DNS Security Extensions</em>. </span>
+ <span class="pubdate">March 2005. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.3.7"></a><p>[<abbr class="abbrev">RFC4035</abbr>]
+
+ <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span>
+ <span class="citetitle"><em class="citetitle">Protocol Modifications for the DNS
+ Security Extensions</em>. </span>
+ <span class="pubdate">March 2005. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
+<h3 class="title">
+<a name="id-1.12.4.3.7.4"></a>Other Important RFCs About <acronym class="acronym">DNS</acronym>
Implementation</h3>
-<div class="biblioentry">
-<a name="id2610505"></a><p>[<abbr class="abbrev">RFC1535</abbr>] <span class="author"><span class="firstname">E.</span> <span class="surname">Gavron</span>. </span><span class="title"><i>A Security Problem and Proposed Correction With Widely
- Deployed <acronym class="acronym">DNS</acronym> Software</i>. </span><span class="pubdate">October 1993. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610531"></a><p>[<abbr class="abbrev">RFC1536</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Kumar</span>, <span class="firstname">J.</span> <span class="surname">Postel</span>, <span class="firstname">C.</span> <span class="surname">Neuman</span>, <span class="firstname">P.</span> <span class="surname">Danzig</span>, and <span class="firstname">S.</span> <span class="surname">Miller</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Implementation
- Errors and Suggested Fixes</i>. </span><span class="pubdate">October 1993. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610599"></a><p>[<abbr class="abbrev">RFC1982</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Elz</span> and <span class="firstname">R.</span> <span class="surname">Bush</span>. </span><span class="title"><i>Serial Number Arithmetic</i>. </span><span class="pubdate">August 1996. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610634"></a><p>[<abbr class="abbrev">RFC4074</abbr>] <span class="authorgroup"><span class="firstname">Y.</span> <span class="surname">Morishita</span> and <span class="firstname">T.</span> <span class="surname">Jinmei</span>. </span><span class="title"><i>Common Misbehaviour Against <acronym class="acronym">DNS</acronym>
- Queries for IPv6 Addresses</i>. </span><span class="pubdate">May 2005. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
-<h3 class="title">Resource Record Types</h3>
-<div class="biblioentry">
-<a name="id2610680"></a><p>[<abbr class="abbrev">RFC1183</abbr>] <span class="authorgroup"><span class="firstname">C.F.</span> <span class="surname">Everhart</span>, <span class="firstname">L. A.</span> <span class="surname">Mamakos</span>, <span class="firstname">R.</span> <span class="surname">Ullmann</span>, and <span class="firstname">P.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>New <acronym class="acronym">DNS</acronym> RR Definitions</i>. </span><span class="pubdate">October 1990. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610738"></a><p>[<abbr class="abbrev">RFC1706</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">R.</span> <span class="surname">Colella</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> NSAP Resource Records</i>. </span><span class="pubdate">October 1994. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610775"></a><p>[<abbr class="abbrev">RFC2168</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Daniel</span> and <span class="firstname">M.</span> <span class="surname">Mealling</span>. </span><span class="title"><i>Resolution of Uniform Resource Identifiers using
- the Domain Name System</i>. </span><span class="pubdate">June 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610810"></a><p>[<abbr class="abbrev">RFC1876</abbr>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Davis</span>, <span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">T.</span>, and <span class="firstname">I.</span> <span class="surname">Dickinson</span>. </span><span class="title"><i>A Means for Expressing Location Information in the
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.4.3"></a><p>[<abbr class="abbrev">RFC1535</abbr>]
+
+ <span class="author"><span class="firstname">E.</span> <span class="surname">Gavron</span>. </span>
+ <span class="citetitle"><em class="citetitle">A Security Problem and Proposed Correction With Widely
+ Deployed <acronym class="acronym">DNS</acronym> Software</em>. </span>
+ <span class="pubdate">October 1993. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.4.4"></a><p>[<abbr class="abbrev">RFC1536</abbr>]
+
+ <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Kumar</span>, <span class="firstname">J.</span> <span class="surname">Postel</span>, <span class="firstname">C.</span> <span class="surname">Neuman</span>, <span class="firstname">P.</span> <span class="surname">Danzig</span>, and <span class="firstname">S.</span> <span class="surname">Miller</span>. </span>
+ <span class="citetitle"><em class="citetitle">Common <acronym class="acronym">DNS</acronym> Implementation
+ Errors and Suggested Fixes</em>. </span>
+ <span class="pubdate">October 1993. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.4.5"></a><p>[<abbr class="abbrev">RFC1982</abbr>]
+
+ <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Elz</span> and <span class="firstname">R.</span> <span class="surname">Bush</span>. </span>
+ <span class="citetitle"><em class="citetitle">Serial Number Arithmetic</em>. </span>
+ <span class="pubdate">August 1996. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.4.6"></a><p>[<abbr class="abbrev">RFC4074</abbr>]
+
+ <span class="authorgroup"><span class="firstname">Y.</span> <span class="surname">Morishita</span> and <span class="firstname">T.</span> <span class="surname">Jinmei</span>. </span>
+ <span class="citetitle"><em class="citetitle">Common Misbehaviour Against <acronym class="acronym">DNS</acronym>
+ Queries for IPv6 Addresses</em>. </span>
+ <span class="pubdate">May 2005. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
+<h3 class="title">
+<a name="id-1.12.4.3.7.5"></a>Resource Record Types</h3>
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.3"></a><p>[<abbr class="abbrev">RFC1183</abbr>]
+
+ <span class="authorgroup"><span class="firstname">C.F.</span> <span class="surname">Everhart</span>, <span class="firstname">L. A.</span> <span class="surname">Mamakos</span>, <span class="firstname">R.</span> <span class="surname">Ullmann</span>, and <span class="firstname">P.</span> <span class="surname">Mockapetris</span>. </span>
+ <span class="citetitle"><em class="citetitle">New <acronym class="acronym">DNS</acronym> RR Definitions</em>. </span>
+ <span class="pubdate">October 1990. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.4"></a><p>[<abbr class="abbrev">RFC1706</abbr>]
+
+ <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">R.</span> <span class="surname">Colella</span>. </span>
+ <span class="citetitle"><em class="citetitle"><acronym class="acronym">DNS</acronym> NSAP Resource Records</em>. </span>
+ <span class="pubdate">October 1994. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.5"></a><p>[<abbr class="abbrev">RFC2168</abbr>]
+
+ <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Daniel</span> and <span class="firstname">M.</span> <span class="surname">Mealling</span>. </span>
+ <span class="citetitle"><em class="citetitle">Resolution of Uniform Resource Identifiers using
+ the Domain Name System</em>. </span>
+ <span class="pubdate">June 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.6"></a><p>[<abbr class="abbrev">RFC1876</abbr>]
+
+ <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Davis</span>, <span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">T.</span>, and <span class="firstname">I.</span> <span class="surname">Dickinson</span>. </span>
+ <span class="citetitle"><em class="citetitle">A Means for Expressing Location Information in the
Domain
- Name System</i>. </span><span class="pubdate">January 1996. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610865"></a><p>[<abbr class="abbrev">RFC2052</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A <acronym class="acronym">DNS</acronym> RR for Specifying the
+ Name System</em>. </span>
+ <span class="pubdate">January 1996. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.7"></a><p>[<abbr class="abbrev">RFC2052</abbr>]
+
+ <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span>
+ <span class="citetitle"><em class="citetitle">A <acronym class="acronym">DNS</acronym> RR for Specifying the
Location of
- Services</i>. </span><span class="pubdate">October 1996. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610903"></a><p>[<abbr class="abbrev">RFC2163</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Allocchio</span>. </span><span class="title"><i>Using the Internet <acronym class="acronym">DNS</acronym> to
+ Services</em>. </span>
+ <span class="pubdate">October 1996. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.8"></a><p>[<abbr class="abbrev">RFC2163</abbr>]
+
+ <span class="author"><span class="firstname">A.</span> <span class="surname">Allocchio</span>. </span>
+ <span class="citetitle"><em class="citetitle">Using the Internet <acronym class="acronym">DNS</acronym> to
Distribute MIXER
- Conformant Global Address Mapping</i>. </span><span class="pubdate">January 1998. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610929"></a><p>[<abbr class="abbrev">RFC2230</abbr>] <span class="author"><span class="firstname">R.</span> <span class="surname">Atkinson</span>. </span><span class="title"><i>Key Exchange Delegation Record for the <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">October 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610954"></a><p>[<abbr class="abbrev">RFC2536</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>DSA KEYs and SIGs in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2610981"></a><p>[<abbr class="abbrev">RFC2537</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611008"></a><p>[<abbr class="abbrev">RFC2538</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Storing Certificates in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611047"></a><p>[<abbr class="abbrev">RFC2539</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611077"></a><p>[<abbr class="abbrev">RFC2540</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Detached Domain Name System (DNS) Information</i>. </span><span class="pubdate">March 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611107"></a><p>[<abbr class="abbrev">RFC2782</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span>. </span><span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="author"><span class="firstname">L.</span> <span class="surname">Esibov</span>. </span><span class="title"><i>A DNS RR for specifying the location of services (DNS SRV)</i>. </span><span class="pubdate">February 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611149"></a><p>[<abbr class="abbrev">RFC2915</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Mealling</span>. </span><span class="author"><span class="firstname">R.</span> <span class="surname">Daniel</span>. </span><span class="title"><i>The Naming Authority Pointer (NAPTR) DNS Resource Record</i>. </span><span class="pubdate">September 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611182"></a><p>[<abbr class="abbrev">RFC3110</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</i>. </span><span class="pubdate">May 2001. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611209"></a><p>[<abbr class="abbrev">RFC3123</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Koch</span>. </span><span class="title"><i>A DNS RR Type for Lists of Address Prefixes (APL RR)</i>. </span><span class="pubdate">June 2001. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611233"></a><p>[<abbr class="abbrev">RFC3596</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">C.</span> <span class="surname">Huitema</span>, <span class="firstname">V.</span> <span class="surname">Ksinant</span>, and <span class="firstname">M.</span> <span class="surname">Souissi</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Extensions to support IP
- version 6</i>. </span><span class="pubdate">October 2003. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611290"></a><p>[<abbr class="abbrev">RFC3597</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Gustafsson</span>. </span><span class="title"><i>Handling of Unknown DNS Resource Record (RR) Types</i>. </span><span class="pubdate">September 2003. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
+ Conformant Global Address Mapping</em>. </span>
+ <span class="pubdate">January 1998. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.9"></a><p>[<abbr class="abbrev">RFC2230</abbr>]
+
+ <span class="author"><span class="firstname">R.</span> <span class="surname">Atkinson</span>. </span>
+ <span class="citetitle"><em class="citetitle">Key Exchange Delegation Record for the <acronym class="acronym">DNS</acronym></em>. </span>
+ <span class="pubdate">October 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.10"></a><p>[<abbr class="abbrev">RFC2536</abbr>]
+
+ <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">DSA KEYs and SIGs in the Domain Name System (DNS)</em>. </span>
+ <span class="pubdate">March 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.11"></a><p>[<abbr class="abbrev">RFC2537</abbr>]
+
+ <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</em>. </span>
+ <span class="pubdate">March 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.12"></a><p>[<abbr class="abbrev">RFC2538</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span>
+ <span class="citetitle"><em class="citetitle">Storing Certificates in the Domain Name System (DNS)</em>. </span>
+ <span class="pubdate">March 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.13"></a><p>[<abbr class="abbrev">RFC2539</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</em>. </span>
+ <span class="pubdate">March 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.14"></a><p>[<abbr class="abbrev">RFC2540</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">Detached Domain Name System (DNS) Information</em>. </span>
+ <span class="pubdate">March 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.15"></a><p>[<abbr class="abbrev">RFC2782</abbr>]
+
+ <span class="author"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span>. </span>
+ <span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span>
+ <span class="author"><span class="firstname">L.</span> <span class="surname">Esibov</span>. </span>
+ <span class="citetitle"><em class="citetitle">A DNS RR for specifying the location of services (DNS SRV)</em>. </span>
+ <span class="pubdate">February 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.16"></a><p>[<abbr class="abbrev">RFC2915</abbr>]
+
+ <span class="author"><span class="firstname">M.</span> <span class="surname">Mealling</span>. </span>
+ <span class="author"><span class="firstname">R.</span> <span class="surname">Daniel</span>. </span>
+ <span class="citetitle"><em class="citetitle">The Naming Authority Pointer (NAPTR) DNS Resource Record</em>. </span>
+ <span class="pubdate">September 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.17"></a><p>[<abbr class="abbrev">RFC3110</abbr>]
+
+ <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</em>. </span>
+ <span class="pubdate">May 2001. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.18"></a><p>[<abbr class="abbrev">RFC3123</abbr>]
+
+ <span class="author"><span class="firstname">P.</span> <span class="surname">Koch</span>. </span>
+ <span class="citetitle"><em class="citetitle">A DNS RR Type for Lists of Address Prefixes (APL RR)</em>. </span>
+ <span class="pubdate">June 2001. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.19"></a><p>[<abbr class="abbrev">RFC3596</abbr>]
+
+ <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">C.</span> <span class="surname">Huitema</span>, <span class="firstname">V.</span> <span class="surname">Ksinant</span>, and <span class="firstname">M.</span> <span class="surname">Souissi</span>. </span>
+ <span class="citetitle"><em class="citetitle"><acronym class="acronym">DNS</acronym> Extensions to support IP
+ version 6</em>. </span>
+ <span class="pubdate">October 2003. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.5.20"></a><p>[<abbr class="abbrev">RFC3597</abbr>]
+
+ <span class="author"><span class="firstname">A.</span> <span class="surname">Gustafsson</span>. </span>
+ <span class="citetitle"><em class="citetitle">Handling of Unknown DNS Resource Record (RR) Types</em>. </span>
+ <span class="pubdate">September 2003. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
<h3 class="title">
-<acronym class="acronym">DNS</acronym> and the Internet</h3>
-<div class="biblioentry">
-<a name="id2611322"></a><p>[<abbr class="abbrev">RFC1101</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Encoding of Network Names
- and Other Types</i>. </span><span class="pubdate">April 1989. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611348"></a><p>[<abbr class="abbrev">RFC1123</abbr>] <span class="author"><span class="surname">Braden</span>. </span><span class="title"><i>Requirements for Internet Hosts - Application and
- Support</i>. </span><span class="pubdate">October 1989. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611370"></a><p>[<abbr class="abbrev">RFC1591</abbr>] <span class="author"><span class="firstname">J.</span> <span class="surname">Postel</span>. </span><span class="title"><i>Domain Name System Structure and Delegation</i>. </span><span class="pubdate">March 1994. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611394"></a><p>[<abbr class="abbrev">RFC2317</abbr>] <span class="authorgroup"><span class="firstname">H.</span> <span class="surname">Eidnes</span>, <span class="firstname">G.</span> <span class="surname">de Groot</span>, and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Classless IN-ADDR.ARPA Delegation</i>. </span><span class="pubdate">March 1998. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611440"></a><p>[<abbr class="abbrev">RFC2826</abbr>] <span class="authorgroup"><span class="surname">Internet Architecture Board</span>. </span><span class="title"><i>IAB Technical Comment on the Unique DNS Root</i>. </span><span class="pubdate">May 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611463"></a><p>[<abbr class="abbrev">RFC2929</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, <span class="firstname">E.</span> <span class="surname">Brunner-Williams</span>, and <span class="firstname">B.</span> <span class="surname">Manning</span>. </span><span class="title"><i>Domain Name System (DNS) IANA Considerations</i>. </span><span class="pubdate">September 2000. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
+<a name="id-1.12.4.3.7.6"></a><acronym class="acronym">DNS</acronym> and the Internet</h3>
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.6.3"></a><p>[<abbr class="abbrev">RFC1101</abbr>]
+
+ <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span>
+ <span class="citetitle"><em class="citetitle"><acronym class="acronym">DNS</acronym> Encoding of Network Names
+ and Other Types</em>. </span>
+ <span class="pubdate">April 1989. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.6.4"></a><p>[<abbr class="abbrev">RFC1123</abbr>]
+
+ <span class="author"><span class="surname">Braden</span>. </span>
+ <span class="citetitle"><em class="citetitle">Requirements for Internet Hosts - Application and
+ Support</em>. </span>
+ <span class="pubdate">October 1989. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.6.5"></a><p>[<abbr class="abbrev">RFC1591</abbr>]
+
+ <span class="author"><span class="firstname">J.</span> <span class="surname">Postel</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Name System Structure and Delegation</em>. </span>
+ <span class="pubdate">March 1994. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.6.6"></a><p>[<abbr class="abbrev">RFC2317</abbr>]
+
+ <span class="authorgroup"><span class="firstname">H.</span> <span class="surname">Eidnes</span>, <span class="firstname">G.</span> <span class="surname">de Groot</span>, and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span>
+ <span class="citetitle"><em class="citetitle">Classless IN-ADDR.ARPA Delegation</em>. </span>
+ <span class="pubdate">March 1998. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.6.7"></a><p>[<abbr class="abbrev">RFC2826</abbr>]
+
+ <span class="authorgroup"><span class="surname">Internet Architecture Board</span>. </span>
+ <span class="citetitle"><em class="citetitle">IAB Technical Comment on the Unique DNS Root</em>. </span>
+ <span class="pubdate">May 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.6.8"></a><p>[<abbr class="abbrev">RFC2929</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, <span class="firstname">E.</span> <span class="surname">Brunner-Williams</span>, and <span class="firstname">B.</span> <span class="surname">Manning</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Name System (DNS) IANA Considerations</em>. </span>
+ <span class="pubdate">September 2000. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
<h3 class="title">
-<acronym class="acronym">DNS</acronym> Operations</h3>
-<div class="biblioentry">
-<a name="id2611521"></a><p>[<abbr class="abbrev">RFC1033</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Lottor</span>. </span><span class="title"><i>Domain administrators operations guide</i>. </span><span class="pubdate">November 1987. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611544"></a><p>[<abbr class="abbrev">RFC1537</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Beertema</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Data File
- Configuration Errors</i>. </span><span class="pubdate">October 1993. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611571"></a><p>[<abbr class="abbrev">RFC1912</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Barr</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Operational and
- Configuration Errors</i>. </span><span class="pubdate">February 1996. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611597"></a><p>[<abbr class="abbrev">RFC2010</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Operational Criteria for Root Name Servers</i>. </span><span class="pubdate">October 1996. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611634"></a><p>[<abbr class="abbrev">RFC2219</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Hamilton</span> and <span class="firstname">R.</span> <span class="surname">Wright</span>. </span><span class="title"><i>Use of <acronym class="acronym">DNS</acronym> Aliases for
- Network Services</i>. </span><span class="pubdate">October 1997. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
-<h3 class="title">Internationalized Domain Names</h3>
-<div class="biblioentry">
-<a name="id2611680"></a><p>[<abbr class="abbrev">RFC2825</abbr>] <span class="authorgroup"><span class="surname">IAB</span> and <span class="firstname">R.</span> <span class="surname">Daigle</span>. </span><span class="title"><i>A Tangled Web: Issues of I18N, Domain Names,
- and the Other Internet protocols</i>. </span><span class="pubdate">May 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611712"></a><p>[<abbr class="abbrev">RFC3490</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Faltstrom</span>, <span class="firstname">P.</span> <span class="surname">Hoffman</span>, and <span class="firstname">A.</span> <span class="surname">Costello</span>. </span><span class="title"><i>Internationalizing Domain Names in Applications (IDNA)</i>. </span><span class="pubdate">March 2003. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611757"></a><p>[<abbr class="abbrev">RFC3491</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Hoffman</span> and <span class="firstname">M.</span> <span class="surname">Blanchet</span>. </span><span class="title"><i>Nameprep: A Stringprep Profile for Internationalized Domain Names</i>. </span><span class="pubdate">March 2003. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611793"></a><p>[<abbr class="abbrev">RFC3492</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Costello</span>. </span><span class="title"><i>Punycode: A Bootstring encoding of Unicode
+<a name="id-1.12.4.3.7.7"></a><acronym class="acronym">DNS</acronym> Operations</h3>
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.7.3"></a><p>[<abbr class="abbrev">RFC1033</abbr>]
+
+ <span class="author"><span class="firstname">M.</span> <span class="surname">Lottor</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain administrators operations guide</em>. </span>
+ <span class="pubdate">November 1987. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.7.4"></a><p>[<abbr class="abbrev">RFC1537</abbr>]
+
+ <span class="author"><span class="firstname">P.</span> <span class="surname">Beertema</span>. </span>
+ <span class="citetitle"><em class="citetitle">Common <acronym class="acronym">DNS</acronym> Data File
+ Configuration Errors</em>. </span>
+ <span class="pubdate">October 1993. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.7.5"></a><p>[<abbr class="abbrev">RFC1912</abbr>]
+
+ <span class="author"><span class="firstname">D.</span> <span class="surname">Barr</span>. </span>
+ <span class="citetitle"><em class="citetitle">Common <acronym class="acronym">DNS</acronym> Operational and
+ Configuration Errors</em>. </span>
+ <span class="pubdate">February 1996. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.7.6"></a><p>[<abbr class="abbrev">RFC2010</abbr>]
+
+ <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span>
+ <span class="citetitle"><em class="citetitle">Operational Criteria for Root Name Servers</em>. </span>
+ <span class="pubdate">October 1996. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.7.7"></a><p>[<abbr class="abbrev">RFC2219</abbr>]
+
+ <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Hamilton</span> and <span class="firstname">R.</span> <span class="surname">Wright</span>. </span>
+ <span class="citetitle"><em class="citetitle">Use of <acronym class="acronym">DNS</acronym> Aliases for
+ Network Services</em>. </span>
+ <span class="pubdate">October 1997. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
+<h3 class="title">
+<a name="id-1.12.4.3.7.8"></a>Internationalized Domain Names</h3>
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.8.3"></a><p>[<abbr class="abbrev">RFC2825</abbr>]
+
+ <span class="authorgroup"><span class="surname">IAB</span> and <span class="firstname">R.</span> <span class="surname">Daigle</span>. </span>
+ <span class="citetitle"><em class="citetitle">A Tangled Web: Issues of I18N, Domain Names,
+ and the Other Internet protocols</em>. </span>
+ <span class="pubdate">May 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.8.4"></a><p>[<abbr class="abbrev">RFC3490</abbr>]
+
+ <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Faltstrom</span>, <span class="firstname">P.</span> <span class="surname">Hoffman</span>, and <span class="firstname">A.</span> <span class="surname">Costello</span>. </span>
+ <span class="citetitle"><em class="citetitle">Internationalizing Domain Names in Applications (IDNA)</em>. </span>
+ <span class="pubdate">March 2003. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.8.5"></a><p>[<abbr class="abbrev">RFC3491</abbr>]
+
+ <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Hoffman</span> and <span class="firstname">M.</span> <span class="surname">Blanchet</span>. </span>
+ <span class="citetitle"><em class="citetitle">Nameprep: A Stringprep Profile for Internationalized Domain Names</em>. </span>
+ <span class="pubdate">March 2003. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.8.6"></a><p>[<abbr class="abbrev">RFC3492</abbr>]
+
+ <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Costello</span>. </span>
+ <span class="citetitle"><em class="citetitle">Punycode: A Bootstring encoding of Unicode
for Internationalized Domain Names in
- Applications (IDNA)</i>. </span><span class="pubdate">March 2003. </span></p>
+ Applications (IDNA)</em>. </span>
+ <span class="pubdate">March 2003. </span>
+ </p>
</div>
-</div>
-<div class="bibliodiv">
-<h3 class="title">Other <acronym class="acronym">DNS</acronym>-related RFCs</h3>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+ </div>
+ <div class="bibliodiv">
+<h3 class="title">
+<a name="id-1.12.4.3.7.9"></a>Other <acronym class="acronym">DNS</acronym>-related RFCs</h3>
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Note: the following list of RFCs, although
<acronym class="acronym">DNS</acronym>-related, are not
concerned with implementing software.
</p>
-</div>
-<div class="biblioentry">
-<a name="id2611837"></a><p>[<abbr class="abbrev">RFC1464</abbr>] <span class="author"><span class="firstname">R.</span> <span class="surname">Rosenbaum</span>. </span><span class="title"><i>Using the Domain Name System To Store Arbitrary String
- Attributes</i>. </span><span class="pubdate">May 1993. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611860"></a><p>[<abbr class="abbrev">RFC1713</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Romao</span>. </span><span class="title"><i>Tools for <acronym class="acronym">DNS</acronym> Debugging</i>. </span><span class="pubdate">November 1994. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611885"></a><p>[<abbr class="abbrev">RFC1794</abbr>] <span class="author"><span class="firstname">T.</span> <span class="surname">Brisco</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Support for Load
- Balancing</i>. </span><span class="pubdate">April 1995. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611911"></a><p>[<abbr class="abbrev">RFC2240</abbr>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Legal Basis for Domain Name Allocation</i>. </span><span class="pubdate">November 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611934"></a><p>[<abbr class="abbrev">RFC2345</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>, <span class="firstname">T.</span> <span class="surname">Wolf</span>, and <span class="firstname">G.</span> <span class="surname">Oglesby</span>. </span><span class="title"><i>Domain Names and Company Name Retrieval</i>. </span><span class="pubdate">May 1998. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2611980"></a><p>[<abbr class="abbrev">RFC2352</abbr>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Convention For Using Legal Names as Domain Names</i>. </span><span class="pubdate">May 1998. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612004"></a><p>[<abbr class="abbrev">RFC3071</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>. </span><span class="title"><i>Reflections on the DNS, RFC 1591, and Categories of Domains</i>. </span><span class="pubdate">February 2001. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612030"></a><p>[<abbr class="abbrev">RFC3258</abbr>] <span class="authorgroup"><span class="firstname">T.</span> <span class="surname">Hardie</span>. </span><span class="title"><i>Distributing Authoritative Name Servers via
- Shared Unicast Addresses</i>. </span><span class="pubdate">April 2002. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612056"></a><p>[<abbr class="abbrev">RFC3901</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Durand</span> and <span class="firstname">J.</span> <span class="surname">Ihren</span>. </span><span class="title"><i>DNS IPv6 Transport Operational Guidelines</i>. </span><span class="pubdate">September 2004. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
-<h3 class="title">Obsolete and Unimplemented Experimental RFC</h3>
-<div class="biblioentry">
-<a name="id2612100"></a><p>[<abbr class="abbrev">RFC1712</abbr>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Farrell</span>, <span class="firstname">M.</span> <span class="surname">Schulze</span>, <span class="firstname">S.</span> <span class="surname">Pleitner</span>, and <span class="firstname">D.</span> <span class="surname">Baldoni</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Encoding of Geographical
- Location</i>. </span><span class="pubdate">November 1994. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612226"></a><p>[<abbr class="abbrev">RFC2673</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span><span class="title"><i>Binary Labels in the Domain Name System</i>. </span><span class="pubdate">August 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612252"></a><p>[<abbr class="abbrev">RFC2874</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span> and <span class="firstname">C.</span> <span class="surname">Huitema</span>. </span><span class="title"><i>DNS Extensions to Support IPv6 Address Aggregation
- and Renumbering</i>. </span><span class="pubdate">July 2000. </span></p>
-</div>
-</div>
-<div class="bibliodiv">
-<h3 class="title">Obsoleted DNS Security RFCs</h3>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+ </div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.4"></a><p>[<abbr class="abbrev">RFC1464</abbr>]
+
+ <span class="author"><span class="firstname">R.</span> <span class="surname">Rosenbaum</span>. </span>
+ <span class="citetitle"><em class="citetitle">Using the Domain Name System To Store Arbitrary String
+ Attributes</em>. </span>
+ <span class="pubdate">May 1993. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.5"></a><p>[<abbr class="abbrev">RFC1713</abbr>]
+
+ <span class="author"><span class="firstname">A.</span> <span class="surname">Romao</span>. </span>
+ <span class="citetitle"><em class="citetitle">Tools for <acronym class="acronym">DNS</acronym> Debugging</em>. </span>
+ <span class="pubdate">November 1994. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.6"></a><p>[<abbr class="abbrev">RFC1794</abbr>]
+
+ <span class="author"><span class="firstname">T.</span> <span class="surname">Brisco</span>. </span>
+ <span class="citetitle"><em class="citetitle"><acronym class="acronym">DNS</acronym> Support for Load
+ Balancing</em>. </span>
+ <span class="pubdate">April 1995. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.7"></a><p>[<abbr class="abbrev">RFC2240</abbr>]
+
+ <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span>
+ <span class="citetitle"><em class="citetitle">A Legal Basis for Domain Name Allocation</em>. </span>
+ <span class="pubdate">November 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.8"></a><p>[<abbr class="abbrev">RFC2345</abbr>]
+
+ <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>, <span class="firstname">T.</span> <span class="surname">Wolf</span>, and <span class="firstname">G.</span> <span class="surname">Oglesby</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Names and Company Name Retrieval</em>. </span>
+ <span class="pubdate">May 1998. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.9"></a><p>[<abbr class="abbrev">RFC2352</abbr>]
+
+ <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span>
+ <span class="citetitle"><em class="citetitle">A Convention For Using Legal Names as Domain Names</em>. </span>
+ <span class="pubdate">May 1998. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.10"></a><p>[<abbr class="abbrev">RFC3071</abbr>]
+
+ <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>. </span>
+ <span class="citetitle"><em class="citetitle">Reflections on the DNS, RFC 1591, and Categories of Domains</em>. </span>
+ <span class="pubdate">February 2001. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.11"></a><p>[<abbr class="abbrev">RFC3258</abbr>]
+
+ <span class="authorgroup"><span class="firstname">T.</span> <span class="surname">Hardie</span>. </span>
+ <span class="citetitle"><em class="citetitle">Distributing Authoritative Name Servers via
+ Shared Unicast Addresses</em>. </span>
+ <span class="pubdate">April 2002. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.9.12"></a><p>[<abbr class="abbrev">RFC3901</abbr>]
+
+ <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Durand</span> and <span class="firstname">J.</span> <span class="surname">Ihren</span>. </span>
+ <span class="citetitle"><em class="citetitle">DNS IPv6 Transport Operational Guidelines</em>. </span>
+ <span class="pubdate">September 2004. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
+<h3 class="title">
+<a name="id-1.12.4.3.7.10"></a>Obsolete and Unimplemented Experimental RFC</h3>
+
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.10.3"></a><p>[<abbr class="abbrev">RFC1712</abbr>]
+
+ <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Farrell</span>, <span class="firstname">M.</span> <span class="surname">Schulze</span>, <span class="firstname">S.</span> <span class="surname">Pleitner</span>, and <span class="firstname">D.</span> <span class="surname">Baldoni</span>. </span>
+ <span class="citetitle"><em class="citetitle"><acronym class="acronym">DNS</acronym> Encoding of Geographical
+ Location</em>. </span>
+ <span class="pubdate">November 1994. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.10.4"></a><p>[<abbr class="abbrev">RFC2673</abbr>]
+
+ <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span>
+ <span class="citetitle"><em class="citetitle">Binary Labels in the Domain Name System</em>. </span>
+ <span class="pubdate">August 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.10.5"></a><p>[<abbr class="abbrev">RFC2874</abbr>]
+
+ <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span> and <span class="firstname">C.</span> <span class="surname">Huitema</span>. </span>
+ <span class="citetitle"><em class="citetitle">DNS Extensions to Support IPv6 Address Aggregation
+ and Renumbering</em>. </span>
+ <span class="pubdate">July 2000. </span>
+ </p>
+</div>
+ </div>
+ <div class="bibliodiv">
+<h3 class="title">
+<a name="id-1.12.4.3.7.11"></a>Obsoleted DNS Security RFCs</h3>
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
Most of these have been consolidated into RFC4033,
RFC4034 and RFC4035 which collectively describe DNSSECbis.
</p>
-</div>
-<div class="biblioentry">
-<a name="id2612300"></a><p>[<abbr class="abbrev">RFC2065</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">C.</span> <span class="surname">Kaufman</span>. </span><span class="title"><i>Domain Name System Security Extensions</i>. </span><span class="pubdate">January 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612340"></a><p>[<abbr class="abbrev">RFC2137</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Secure Domain Name System Dynamic Update</i>. </span><span class="pubdate">April 1997. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612366"></a><p>[<abbr class="abbrev">RFC2535</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Domain Name System Security Extensions</i>. </span><span class="pubdate">March 1999. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612396"></a><p>[<abbr class="abbrev">RFC3008</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Domain Name System Security (DNSSEC)
- Signing Authority</i>. </span><span class="pubdate">November 2000. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612422"></a><p>[<abbr class="abbrev">RFC3090</abbr>] <span class="authorgroup"><span class="firstname">E.</span> <span class="surname">Lewis</span>. </span><span class="title"><i>DNS Security Extension Clarification on Zone Status</i>. </span><span class="pubdate">March 2001. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612449"></a><p>[<abbr class="abbrev">RFC3445</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Massey</span> and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Limiting the Scope of the KEY Resource Record (RR)</i>. </span><span class="pubdate">December 2002. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612485"></a><p>[<abbr class="abbrev">RFC3655</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Redefinition of DNS Authenticated Data (AD) bit</i>. </span><span class="pubdate">November 2003. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612521"></a><p>[<abbr class="abbrev">RFC3658</abbr>] <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Delegation Signer (DS) Resource Record (RR)</i>. </span><span class="pubdate">December 2003. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612548"></a><p>[<abbr class="abbrev">RFC3755</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Weiler</span>. </span><span class="title"><i>Legacy Resolver Compatibility for Delegation Signer (DS)</i>. </span><span class="pubdate">May 2004. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612574"></a><p>[<abbr class="abbrev">RFC3757</abbr>] <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Kolkman</span>, <span class="firstname">J.</span> <span class="surname">Schlyter</span>, and <span class="firstname">E.</span> <span class="surname">Lewis</span>. </span><span class="title"><i>Domain Name System KEY (DNSKEY) Resource Record
- (RR) Secure Entry Point (SEP) Flag</i>. </span><span class="pubdate">April 2004. </span></p>
-</div>
-<div class="biblioentry">
-<a name="id2612619"></a><p>[<abbr class="abbrev">RFC3845</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Schlyter</span>. </span><span class="title"><i>DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</i>. </span><span class="pubdate">August 2004. </span></p>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.4"></a><p>[<abbr class="abbrev">RFC2065</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">C.</span> <span class="surname">Kaufman</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Name System Security Extensions</em>. </span>
+ <span class="pubdate">January 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.5"></a><p>[<abbr class="abbrev">RFC2137</abbr>]
+
+ <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">Secure Domain Name System Dynamic Update</em>. </span>
+ <span class="pubdate">April 1997. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.6"></a><p>[<abbr class="abbrev">RFC2535</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Name System Security Extensions</em>. </span>
+ <span class="pubdate">March 1999. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.7"></a><p>[<abbr class="abbrev">RFC3008</abbr>]
+
+ <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Name System Security (DNSSEC)
+ Signing Authority</em>. </span>
+ <span class="pubdate">November 2000. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.8"></a><p>[<abbr class="abbrev">RFC3090</abbr>]
+
+ <span class="authorgroup"><span class="firstname">E.</span> <span class="surname">Lewis</span>. </span>
+ <span class="citetitle"><em class="citetitle">DNS Security Extension Clarification on Zone Status</em>. </span>
+ <span class="pubdate">March 2001. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.9"></a><p>[<abbr class="abbrev">RFC3445</abbr>]
+
+ <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Massey</span> and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span>
+ <span class="citetitle"><em class="citetitle">Limiting the Scope of the KEY Resource Record (RR)</em>. </span>
+ <span class="pubdate">December 2002. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.10"></a><p>[<abbr class="abbrev">RFC3655</abbr>]
+
+ <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span>
+ <span class="citetitle"><em class="citetitle">Redefinition of DNS Authenticated Data (AD) bit</em>. </span>
+ <span class="pubdate">November 2003. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.11"></a><p>[<abbr class="abbrev">RFC3658</abbr>]
+
+ <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span>
+ <span class="citetitle"><em class="citetitle">Delegation Signer (DS) Resource Record (RR)</em>. </span>
+ <span class="pubdate">December 2003. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.12"></a><p>[<abbr class="abbrev">RFC3755</abbr>]
+
+ <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Weiler</span>. </span>
+ <span class="citetitle"><em class="citetitle">Legacy Resolver Compatibility for Delegation Signer (DS)</em>. </span>
+ <span class="pubdate">May 2004. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.13"></a><p>[<abbr class="abbrev">RFC3757</abbr>]
+
+ <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Kolkman</span>, <span class="firstname">J.</span> <span class="surname">Schlyter</span>, and <span class="firstname">E.</span> <span class="surname">Lewis</span>. </span>
+ <span class="citetitle"><em class="citetitle">Domain Name System KEY (DNSKEY) Resource Record
+ (RR) Secure Entry Point (SEP) Flag</em>. </span>
+ <span class="pubdate">April 2004. </span>
+ </p>
+</div>
+ <div class="biblioentry">
+<a name="id-1.12.4.3.7.11.14"></a><p>[<abbr class="abbrev">RFC3845</abbr>]
+
+ <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Schlyter</span>. </span>
+ <span class="citetitle"><em class="citetitle">DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</em>. </span>
+ <span class="pubdate">August 2004. </span>
+ </p>
+</div>
+ </div>
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="internet_drafts"></a>Internet Drafts</h3></div></div></div>
-<p>
+
+ <p>
Internet Drafts (IDs) are rough-draft working documents of
the Internet Engineering Task Force. They are, in essence, RFCs
in the preliminary stages of development. Implementors are
they are "works in progress." IDs have a lifespan of six months
after which they are deleted unless updated by their authors.
</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id
2612661"></a>Other Documents About <acronym class="acronym">BIND</acronym>
+<a name="id
-1.12.4.5"></a>Other Documents About <acronym class="acronym">BIND</acronym>
</h3></div></div></div>
-<p></p>
-<div class="bibliography">
+
+ <p></p>
+ <div class="bibliography">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2612670"></a>Bibliography</h4></div></div></div>
-<div class="biblioentry">
-<a name="id2612673"></a><p><span class="authorgroup"><span class="firstname">Paul</span> <span class="surname">Albitz</span> and <span class="firstname">Cricket</span> <span class="surname">Liu</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></i>. </span><span class="copyright">Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. </span></p>
-</div>
-</div>
-</div>
-</div>
-</div>
+<a name="id-1.12.4.5.4"></a>Bibliography</h4></div></div></div>
+ <div class="biblioentry">
+<a name="id-1.12.4.5.4.1"></a><p>
+ <span class="authorgroup"><span class="firstname">Paul</span> <span class="surname">Albitz</span> and <span class="firstname">Cricket</span> <span class="surname">Liu</span>. </span>
+ <span class="citetitle"><em class="citetitle"><acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></em>. </span>
+ <span class="copyright">Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. </span>
+ </p>
+</div>
+ </div>
+ </div>
+ </div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix D. BIND 9 DNS Library Support</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch11.html" title="Appendix C. General DNS Reference Information">
<link rel="next" href="Bv9ARM.ch13.html" title="Manual pages">
</table>
<hr>
</div>
-<div class="appendix" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="Bv9ARM.ch12"></a>Appendix D. BIND 9 DNS Library Support</h2></div></div></div>
+<div class="appendix">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="Bv9ARM.ch12"></a>Appendix D. BIND 9 DNS Library Support</h1></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch12.html#bind9.library">BIND 9 DNS Library Support</a></span></dt>
+<dl class="toc">
+<dt><span class="sect
ion"><a href="Bv9ARM.ch12.html#bind9.library">BIND 9 DNS Library Support</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2616519">Prerequisite</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615300">Compilation</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615324">Installation</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615355">Known Defects/Restrictions</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615432">The dns.conf File</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615459">Sample Applications</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2616705">Library References</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.5">Prerequisite</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.6">Compilation</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.7">Installation</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.8">Known Defects/Restrictions</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.9">The dns.conf File</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.10">Sample Applications</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.11">Library References</a></span></dt>
</dl></dd>
</dl>
</div>
-<div class="sect1" lang="en">
+
+ <div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="bind9.library"></a>BIND 9 DNS Library Support</h2></div></div></div>
-<p>This version of BIND 9 "exports" its internal libraries so
+
+ <p>This version of BIND 9 "exports" its internal libraries so
that they can be used by third-party applications more easily (we
call them "export" libraries in this document). In addition to
all major DNS-related APIs BIND 9 is currently using, the export
libraries provide the following features:</p>
-<div class="itemizedlist"><ul type="disc">
-<li><p>The newly created "DNS client" module. This is a higher
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>The newly created "DNS client" module. This is a higher
level API that provides an interface to name resolution,
single DNS transaction with a particular server, and dynamic
update. Regarding name resolution, it supports advanced
features such as DNSSEC validation and caching. This module
- supports both synchronous and asynchronous mode.</p></li>
-<li><p>The new "IRS" (Information Retrieval System) library.
+ supports both synchronous and asynchronous mode.</p>
+ </li>
+<li class="listitem">
+ <p>The new "IRS" (Information Retrieval System) library.
It provides an interface to parse the traditional resolv.conf
file and more advanced, DNS-specific configuration file for
the rest of this package (see the description for the
- dns.conf file below).</p></li>
-<li><p>As part of the IRS library, newly implemented standard
+ dns.conf file below).</p>
+ </li>
+<li class="listitem">
+ <p>As part of the IRS library, newly implemented standard
address-name mapping functions, getaddrinfo() and
getnameinfo(), are provided. They use the DNSSEC-aware
validating resolver backend, and could use other advanced
features of the BIND 9 libraries such as caching. The
getaddrinfo() function resolves both A and AAAA RRs
- concurrently (when the address family is unspecified).</p></li>
-<li><p>An experimental framework to support other event
- libraries than BIND 9's internal event task system.</p></li>
+ concurrently (when the address family is unspecified).</p>
+ </li>
+<li class="listitem">
+ <p>An experimental framework to support other event
+ libraries than BIND 9's internal event task system.</p>
+ </li>
</ul></div>
-<div class="sect2" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2616519"></a>Prerequisite</h3></div></div></div>
-<p>GNU make is required to build the export libraries (other
+<a name="id-1.13.3.5"></a>Prerequisite</h3></div></div></div>
+
+ <p>GNU make is required to build the export libraries (other
part of BIND 9 can still be built with other types of make). In
the reminder of this document, "make" means GNU make. Note that
in some platforms you may need to invoke a different command name
than "make" (e.g. "gmake") to indicate it's GNU make.</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2615300"></a>Compilation</h3></div></div></div>
-<pre class="screen">
+<a name="id-1.13.3.6"></a>Compilation</h3></div></div></div>
+
+ <pre class="screen">
$ <strong class="userinput"><code>./configure --enable-exportlib <em class="replaceable"><code>[other flags]</code></em></code></strong>
$ <strong class="userinput"><code>make</code></strong>
</pre>
-<p>
This will create (in addition to usual BIND 9 programs) and a
separate set of libraries under the lib/export directory. For
example, <code class="filename">lib/export/dns/libdns.a</code> is the archive file of the
export version of the BIND 9 DNS library. Sample application
programs using the libraries will also be built under the
lib/export/samples directory (see below).</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2615324"></a>Installation</h3></div></div></div>
-<pre class="screen">
+<a name="id-1.13.3.7"></a>Installation</h3></div></div></div>
+
+ <pre class="screen">
$ <strong class="userinput"><code>cd lib/export</code></strong>
$ <strong class="userinput"><code>make install</code></strong>
</pre>
-<p>
This will install library object files under the directory
specified by the --with-export-libdir configure option (default:
EPREFIX/lib/bind9), and header files under the directory
specified by the --with-export-includedir configure option
(default: PREFIX/include/bind9).
Root privilege is normally required.
- "<span><strong class="command">make install</strong></span>" at the top directory will do the
+ "<span class="command"><strong>make install</strong></span>" at the top directory will do the
same.
</p>
-<p>
To see how to build your own
application after the installation, see
<code class="filename">lib/export/samples/Makefile-postinstall.in</code>.</p>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2615355"></a>Known Defects/Restrictions</h3></div></div></div>
-<div class="itemizedlist"><ul type="disc">
-<li><p>Currently, win32 is not supported for the export
+<a name="id-1.13.3.8"></a>Known Defects/Restrictions</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+
+ <p>Currently, win32 is not supported for the export
library. (Normal BIND 9 application can be built as
- before).</p></li>
-<li>
-<p>The "fixed" RRset order is not (currently) supported in
+ before).</p>
+ </li>
+<li class="listitem">
+ <p>The "fixed" RRset order is not (currently) supported in
the export library. If you want to use "fixed" RRset order
- for, e.g. <span><strong class="command">named</strong></span> while still building the
+ for, e.g. <span class="command"><strong>named</strong></span> while still building the
export library even without the fixed order support, build
them separately:
</p>
</pre>
<p>
</p>
-</li>
-<li><p>The client module and the IRS library currently do not
+ </li>
+<li class="listitem">
+ <p>The client module and the IRS library currently do not
support DNSSEC validation using DLV (the underlying modules
can handle it, but there is no tunable interface to enable
- the feature).</p></li>
-<li><p>RFC 5011 is not supported in the validating stub
+ the feature).</p>
+ </li>
+<li class="listitem">
+ <p>RFC 5011 is not supported in the validating stub
resolver of the export library. In fact, it is not clear
whether it should: trust anchors would be a system-wide
configuration which would be managed by an administrator,
while the stub resolver will be used by ordinary applications
- run by a normal user.</p></li>
-<li><p>Not all common <code class="filename">/etc/resolv.conf</code>
+ run by a normal user.</p>
+ </li>
+<li class="listitem">
+ <p>Not all common <code class="filename">/etc/resolv.conf</code>
options are supported
in the IRS library. The only available options in this
- version are "debug" and "ndots".</p></li>
+ version are "debug" and "ndots".</p>
+ </li>
</ul></div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2615432"></a>The dns.conf File</h3></div></div></div>
-<p>The IRS library supports an "advanced" configuration file
+<a name="id-1.13.3.9"></a>The dns.conf File</h3></div></div></div>
+
+ <p>The IRS library supports an "advanced" configuration file
related to the DNS library for configuration parameters that
would be beyond the capability of the
<code class="filename">resolv.conf</code> file.
This module is very
experimental and the configuration syntax or library interfaces
may change in future versions. Currently, only the
- <span><strong class="command">trusted-keys</strong></span>
+ <span class="command"><strong>trusted-keys</strong></span>
statement is supported, whose syntax is the same as the same name
of statement for <code class="filename">named.conf</code>. (See
- <a href="Bv9ARM.ch06.html#trusted-keys" title="trusted-keys Statement Grammar">the section called “<span><strong class="command">trusted-keys</strong></span> Statement Grammar”</a> for details.)</p>
-</div>
-<div class="sect2" lang="en">
+ <a class="xref" href="Bv9ARM.ch06.html#trusted-keys" title="trusted-keys Statement Grammar">the section called “<span class="command"><strong>trusted-keys</strong></span> Statement Grammar”</a> for details.)</p>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2615459"></a>Sample Applications</h3></div></div></div>
-<p>Some sample application programs using this API are
+<a name="id-1.13.3.10"></a>Sample Applications</h3></div></div></div>
+
+ <p>Some sample application programs using this API are
provided for reference. The following is a brief description of
these applications.
</p>
-<div class="sect3" lang="en">
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2615467"></a>sample: a simple stub resolver utility</h4></div></div></div>
-<p>
+<a name="id-1.13.3.10.4"></a>sample: a simple stub resolver utility</h4></div></div></div>
+
+ <p>
It sends a query of a given name (of a given optional RR type) to a
specified recursive server, and prints the result as a list of
RRs. It can also act as a validating stub resolver if a trust
anchor is given via a set of command line options.</p>
-<p>
Usage: sample [options] server_address hostname
</p>
-<p>
Options and Arguments:
</p>
-<div class="variablelist"><dl>
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">
-t RRtype
</span></dt>
<dd><p>
- specify the RR type of the query. The default is the A RR.
+ specify the RR type of the query. The default is the A RR.
</p></dd>
<dt><span class="term">
[-a algorithm] [-e] -k keyname -K keystring
</span></dt>
<dd>
<p>
- specify a command-line DNS key to validate the answer. For
- example, to specify the following DNSKEY of example.com:
+ specify a command-line DNS key to validate the answer. For
+ example, to specify the following DNSKEY of example.com:
</p>
<div class="literallayout"><p><br>
- example.com. 3600 IN DNSKEY 257 3 5 xxx<br>
+ example.com. 3600 IN DNSKEY 257 3 5 xxx<br>
</p></div>
<p>
- specify the options as follows:
+ specify the options as follows:
</p>
<pre class="screen">
<strong class="userinput"><code>
- -e -k example.com -K "xxx"
+ -e -k example.com -K "xxx"
</code></strong>
</pre>
<p>
- -e means that this key is a zone's "key signing key" (as known
- as "secure Entry point").
- When -a is omitted rsasha1 will be used by default.
+ -e means that this key is a zone's "key signing key" (as known
+ as "secure Entry point").
+ When -a is omitted rsasha1 will be used by default.
</p>
</dd>
<dt><span class="term">
-s domain:alt_server_address
</span></dt>
<dd><p>
- specify a separate recursive server address for the specific
- "domain". Example: -s example.com:2001:db8::1234
+ specify a separate recursive server address for the specific
+ "domain". Example: -s example.com:2001:db8::1234
</p></dd>
<dt><span class="term">server_address</span></dt>
<dd><p>
- an IP(v4/v6) address of the recursive server to which queries
- are sent.
+ an IP(v4/v6) address of the recursive server to which queries
+ are sent.
</p></dd>
<dt><span class="term">hostname</span></dt>
<dd><p>
- the domain name for the query
+ the domain name for the query
</p></dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2615558"></a>sample-async: a simple stub resolver, working asynchronously</h4></div></div></div>
-<p>
+<a name="id-1.13.3.10.5"></a>sample-async: a simple stub resolver, working asynchronously</h4></div></div></div>
+
+ <p>
Similar to "sample", but accepts a list
of (query) domain names as a separate file and resolves the names
asynchronously.</p>
-<p>
Usage: sample-async [-s server_address] [-t RR_type] input_file</p>
-<p>
Options and Arguments:
</p>
-<div class="variablelist"><dl>
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">
-s server_address
</span></dt>
mx.example.net<br>
ns.xxx.example<br>
</p></div>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2616021"></a>sample-request: a simple DNS transaction client</h4></div></div></div>
-<p>
+<a name="id-1.13.3.10.6"></a>sample-request: a simple DNS transaction client</h4></div></div></div>
+
+ <p>
It sends a query to a specified server, and
prints the response with minimal processing. It doesn't act as a
"stub resolver": it stops the processing once it gets any
response from the server, whether it's a referral or an alias
(CNAME or DNAME) that would require further queries to get the
ultimate answer. In other words, this utility acts as a very
- simplified <span><strong class="command">dig</strong></span>.
+ simplified <span class="command"><strong>dig</strong></span>.
</p>
-<p>
Usage: sample-request [-t RRtype] server_address hostname
</p>
-<p>
Options and Arguments:
</p>
-<div class="variablelist"><dl>
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">
-t RRtype
</span></dt>
-<dd><p>
+<dd>
+ <p>
specify the RR type of
the queries. The default is the A RR.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
server_address
</span></dt>
-<dd><p>
+<dd>
+ <p>
an IP(v4/v6)
address of the recursive server to which the query is sent.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
hostname
</span></dt>
-<dd><p>
+<dd>
+ <p>
the domain name for the query
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2616085"></a>sample-gai: getaddrinfo() and getnameinfo() test code</h4></div></div></div>
-<p>
+<a name="id-1.13.3.10.7"></a>sample-gai: getaddrinfo() and getnameinfo() test code</h4></div></div></div>
+
+ <p>
This is a test program
to check getaddrinfo() and getnameinfo() behavior. It takes a
host name as an argument, calls getaddrinfo() with the given host
validating resolver, and getaddrinfo()/getnameinfo() will fail
with an EAI_INSECUREDATA error when DNSSEC validation fails.
</p>
-<p>
Usage: sample-gai hostname
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2616100"></a>sample-update: a simple dynamic update client program</h4></div></div></div>
-<p>
+<a name="id-1.13.3.10.8"></a>sample-update: a simple dynamic update client program</h4></div></div></div>
+
+ <p>
It accepts a single update command as a
command-line argument, sends an update request message to the
authoritative server, and shows the response from the server. In
- other words, this is a simplified <span><strong class="command">nsupdate</strong></span>.
+ other words, this is a simplified <span class="command"><strong>nsupdate</strong></span>.
</p>
-<p>
Usage: sample-update [options] (add|delete) "update data"
</p>
-<p>
Options and Arguments:
</p>
-<div class="variablelist"><dl>
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">
-a auth_server
</span></dt>
<dd><p>
- An IP address of the authoritative server that has authority
- for the zone containing the update name. This should normally
- be the primary authoritative server that accepts dynamic
- updates. It can also be a secondary server that is configured
- to forward update requests to the primary server.
+ An IP address of the authoritative server that has authority
+ for the zone containing the update name. This should normally
+ be the primary authoritative server that accepts dynamic
+ updates. It can also be a secondary server that is configured
+ to forward update requests to the primary server.
</p></dd>
<dt><span class="term">
-k keyfile
</span></dt>
<dd><p>
- A TSIG key file to secure the update transaction. The keyfile
- format is the same as that for the nsupdate utility.
+ A TSIG key file to secure the update transaction. The keyfile
+ format is the same as that for the nsupdate utility.
</p></dd>
<dt><span class="term">
-p prerequisite
</span></dt>
<dd><p>
- A prerequisite for the update (only one prerequisite can be
- specified). The prerequisite format is the same as that is
- accepted by the nsupdate utility.
+ A prerequisite for the update (only one prerequisite can be
+ specified). The prerequisite format is the same as that is
+ accepted by the nsupdate utility.
</p></dd>
<dt><span class="term">
-r recursive_server
</span></dt>
<dd><p>
- An IP address of a recursive server that this utility will
- use. A recursive server may be necessary to identify the
- authoritative server address to which the update request is
- sent.
+ An IP address of a recursive server that this utility will
+ use. A recursive server may be necessary to identify the
+ authoritative server address to which the update request is
+ sent.
</p></dd>
<dt><span class="term">
-z zonename
</span></dt>
<dd><p>
- The domain name of the zone that contains
+ The domain name of the zone that contains
</p></dd>
<dt><span class="term">
(add|delete)
</span></dt>
<dd><p>
- Specify the type of update operation. Either "add" or "delete"
- must be specified.
+ Specify the type of update operation. Either "add" or "delete"
+ must be specified.
</p></dd>
<dt><span class="term">
"update data"
</span></dt>
<dd><p>
- Specify the data to be updated. A typical example of the data
- would look like "name TTL RRtype RDATA".
+ Specify the data to be updated. A typical example of the data
+ would look like "name TTL RRtype RDATA".
</p></dd>
</dl></div>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
+ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>In practice, either -a or -r must be specified. Others can
be optional; the underlying library routine tries to identify the
appropriate server and the zone name for the update.</div>
-<p>
+
+ <p>
Examples: assuming the primary authoritative server of the
dynamic.example.com zone has an IPv6 address 2001:db8::1234,
</p>
-<pre class="screen">
$ <strong class="userinput"><code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key add "foo.dynamic.example.com 30 IN A 192.168.2.1"</code></strong></pre>
-<p>
adds an A RR for foo.dynamic.example.com using the given key.
</p>
-<pre class="screen">
$ <strong class="userinput"><code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com 30 IN A"</code></strong></pre>
-<p>
removes all A RRs for foo.dynamic.example.com using the given key.
</p>
-<pre class="screen">
$ <strong class="userinput"><code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com"</code></strong></pre>
-<p>
removes all RRs for foo.dynamic.example.com using the given key.
</p>
-</div>
-<div class="sect3" lang="en">
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id2616641"></a>nsprobe: domain/name server checker in terms of RFC 4074</h4></div></div></div>
-<p>
+<a name="id-1.13.3.10.9"></a>nsprobe: domain/name server checker in terms of RFC 4074</h4></div></div></div>
+
+ <p>
It checks a set
of domains to see the name servers of the domains behave
correctly in terms of RFC 4074. This is included in the set of
sample programs to show how the export library can be used in a
DNS-related application.
</p>
-<p>
Usage: nsprobe [-d] [-v [-v...]] [-c cache_address] [input_file]
</p>
-<p>
Options
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">
-d
</span></dt>
<dd><p>
- run in the "debug" mode. with this option nsprobe will dump
- every RRs it receives.
+ run in the "debug" mode. with this option nsprobe will dump
+ every RRs it receives.
</p></dd>
<dt><span class="term">
-v
</span></dt>
<dd><p>
- increase verbosity of other normal log messages. This can be
- specified multiple times
+ increase verbosity of other normal log messages. This can be
+ specified multiple times
</p></dd>
<dt><span class="term">
-c cache_address
</span></dt>
<dd><p>
- specify an IP address of a recursive (caching) name server.
- nsprobe uses this server to get the NS RRset of each domain and
- the A and/or AAAA RRsets for the name servers. The default
- value is 127.0.0.1.
+ specify an IP address of a recursive (caching) name server.
+ nsprobe uses this server to get the NS RRset of each domain and
+ the A and/or AAAA RRsets for the name servers. The default
+ value is 127.0.0.1.
</p></dd>
<dt><span class="term">
input_file
</span></dt>
<dd><p>
- a file name containing a list of domain (zone) names to be
- probed. when omitted the standard input will be used. Each
- line of the input file specifies a single domain name such as
- "example.com". In general this domain name must be the apex
- name of some DNS zone (unlike normal "host names" such as
- "www.example.com"). nsprobe first identifies the NS RRsets for
- the given domain name, and sends A and AAAA queries to these
- servers for some "widely used" names under the zone;
- specifically, adding "www" and "ftp" to the zone name.
+ a file name containing a list of domain (zone) names to be
+ probed. when omitted the standard input will be used. Each
+ line of the input file specifies a single domain name such as
+ "example.com". In general this domain name must be the apex
+ name of some DNS zone (unlike normal "host names" such as
+ "www.example.com"). nsprobe first identifies the NS RRsets for
+ the given domain name, and sends A and AAAA queries to these
+ servers for some "widely used" names under the zone;
+ specifically, adding "www" and "ftp" to the zone name.
</p></dd>
</dl></div>
-</div>
-</div>
-<div class="sect2" lang="en">
+ </div>
+ </div>
+ <div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="id2616705"></a>Library References</h3></div></div></div>
-<p>As of this writing, there is no formal "manual" of the
+<a name="id-1.13.3.11"></a>Library References</h3></div></div></div>
+
+ <p>As of this writing, there is no formal "manual" of the
libraries, except this document, header files (some of them
provide pretty detailed explanations), and sample application
programs.</p>
+ </div>
</div>
-</div>
-</div>
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Manual pages</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch12.html" title="Appendix D. BIND 9 DNS Library Support">
<link rel="next" href="man.dig.html" title="dig">
</table>
<hr>
</div>
-<div class="reference" lang="en">
+<div class="reference">
<div class="titlepage">
<div><div><h1 class="title">
<a name="Bv9ARM.ch13"></a>Manual pages</h1></div></div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
+<dl class="toc">
<dt>
<span class="refentrytitle"><a href="man.dig.html">dig</a></span><span class="refpurpose"> — DNS lookup utility</span>
</dt>
<span class="refentrytitle"><a href="man.dnssec-verify.html"><span class="application">dnssec-verify</span></a></span><span class="refpurpose"> — DNSSEC zone verification tool</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named-checkconf.html"><span class="application">named-checkconf</span></a></span><span class="refpurpose"> — named configuration file syntax checking tool</span>
+<span class="refentrytitle"><a href="man.lwresd.html"><span class="application">lwresd</span></a></span><span class="refpurpose"> — lightweight resolver daemon</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named-checkzone.html"><span class="application">named-checkzone</span></a></span><span class="refpurpose"> — zone file validity checking or converting tool</span>
+<span class="refentrytitle"><a href="man.named.html"><span class="application">named</span></a></span><span class="refpurpose"> — Internet domain name server</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named.html"><span class="application">named</span></a></span><span class="refpurpose"> — Internet domain name server</span>
+<span class="refentrytitle"><a href="man.named.conf.html"><code class="filename">named.conf</code></a></span><span class="refpurpose"> — configuration file for <span class="command"><strong>named</strong></span></span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named.conf.html"><code class="filename">named.conf</code></a></span><span class="refpurpose"> — configuration file for <span><strong class="command">named</strong></span></span>
+<span class="refentrytitle"><a href="man.named-checkconf.html"><span class="application">named-checkconf</span></a></span><span class="refpurpose"> — named configuration file syntax checking tool</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.lwresd.html"><span class="application">lwresd</span></a></span><span class="refpurpose"> — lightweight resolver daemon</span>
+<span class="refentrytitle"><a href="man.named-checkzone.html"><span class="application">named-checkzone</span></a></span><span class="refpurpose"> — zone file validity checking or converting tool</span>
</dt>
<dt>
<span class="refentrytitle"><a href="man.named-journalprint.html"><span class="application">named-journalprint</span></a></span><span class="refpurpose"> — print zone journal in human-readable form</span>
<span class="refentrytitle"><a href="man.isc-hmac-fixup.html"><span class="application">isc-hmac-fixup</span></a></span><span class="refpurpose"> — fixes HMAC keys generated by older versions of BIND</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named-journalprint.html"><span class="application">named-journalprint</span></a></span><span class="refpurpose"> — print zone journal in human-readable form</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="man.named-rrchecker.html"><span class="application">named-rrchecker</span></a></span><span class="refpurpose"> — A syntax checker for individual DNS resource records</span>
-</dt>
-<dt>
<span class="refentrytitle"><a href="man.nsec3hash.html"><span class="application">nsec3hash</span></a></span><span class="refpurpose"> — generate NSEC3 hash</span>
</dt>
</dl>
</div>
-</div>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
--- /dev/null
+TexInputs: ../tex//
+TexStyle: armstyle
+XslParam: ../xsl/arm-param.xsl
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>BIND 9 Administrator Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="next" href="Bv9ARM.ch01.html" title="Chapter 1. Introduction">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
</table>
<hr>
</div>
-<div class="book" lang="en">
+<div class="book">
<div class="titlepage">
<div>
<div><h1 class="title">
-<a name="id2563180"></a>BIND 9 Administrator Reference Manual</h1></div>
+<a name="id-1"></a>BIND 9 Administrator Reference Manual</h1></div>
<div><p class="releaseinfo">BIND Version 9.11.0pre-alpha</p></div>
<div><p class="copyright">Copyright © 2004-2015 Internet Systems Consortium, Inc. ("ISC")</p></div>
<div><p class="copyright">Copyright © 2000-2003 Internet Software Consortium.</p></div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
-<dl>
+<dl class="toc">
<dt><span class="chapter"><a href="Bv9ARM.ch01.html">1. Introduction</a></span></dt>
<dd><dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2563509">Scope of Document</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2563533">Organization of This Document</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2564629">Conventions Used in This Document</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch01.html#id2564810">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.4">Scope of Document</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.5">Organization of This Document</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6">Conventions Used in This Document</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch01.html#id-1.2.7">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2564832">DNS Fundamentals</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2564934">Domains and Domain Names</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567271">Zones</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567348">Authoritative Name Servers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567589">Caching Name Servers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567651">Name Servers in Multiple Roles</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.4">DNS Fundamentals</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.5">Domains and Domain Names</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.6">Zones</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.7">Authoritative Name Servers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.8">Caching Name Servers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.7.9">Name Servers in Multiple Roles</a></span></dt>
</dl></dd>
</dl></dd>
<dt><span class="chapter"><a href="Bv9ARM.ch02.html">2. <acronym class="acronym">BIND</acronym> Resource Requirements</a></span></dt>
<dd><dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567685">Hardware requirements</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567712">CPU Requirements</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567793">Memory Requirements</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567819">Name Server Intensive Environment Issues</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567830">Supported Operating Systems</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.3">Hardware requirements</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.4">CPU Requirements</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.5">Memory Requirements</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.6">Name Server Intensive Environment Issues</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.7">Supported Operating Systems</a></span></dt>
</dl></dd>
<dt><span class="chapter"><a href="Bv9ARM.ch03.html">3. Name Server Configuration</a></span></dt>
<dd><dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2567998">A Caching-only Name Server</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568014">An Authoritative-only Name Server</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.4.3">A Caching-only Name Server</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.4.4">An Authoritative-only Name Server</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568037">Load Balancing</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568391">Name Server Operations</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5">Load Balancing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.6">Name Server Operations</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568396">Tools for Use With the Name Server Daemon</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2569465">Signals</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.6.3">Tools for Use With the Name Server Daemon</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.6.4">Signals</a></span></dt>
</dl></dd>
</dl></dd>
<dt><span class="chapter"><a href="Bv9ARM.ch04.html">4. Advanced DNS Features</a></span></dt>
<dd><dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#notify">Notify</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
-<dd><dl><dt><span class="sect
2"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2569988">Split DNS</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570006">Example split DNS setup</a></span></dt></dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#notify">Notify</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
+<dd><dl><dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6">Split DNS</a></span></dt>
+<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.6">Example split DNS setup</a></span></dt></dl></dd>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570439">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570581">Copying the Shared Secret to Both Machines</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570592">Informing the Servers of the Key's Existence</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570628">Instructing the Server to Use the Key</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570685">TSIG Key Based Access Control</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570734">Errors</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.6">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.7">Copying the Shared Secret to Both Machines</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.8">Informing the Servers of the Key's Existence</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.9">Instructing the Server to Use the Key</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.10">TSIG Key Based Access Control</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7.11">Errors</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570748">TKEY</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570866">SIG(0)</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.8">TKEY</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9">SIG(0)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571002">Generating Keys</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571218">Signing the Zone</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571299">Configuring Servers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.7">Generating Keys</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.8">Signing the Zone</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.9">Configuring Servers</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613607">Converting from insecure to secure</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613644">Dynamic DNS update method</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563573">Fully automatic zone signing</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563820">Private-type records</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573415">DNSKEY rollovers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573428">Dynamic DNS update method</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573461">Automatic key rollovers</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573488">NSEC3PARAM rollovers via UPDATE</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573497">Converting from NSEC to NSEC3</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573507">Converting from NSEC3 to NSEC</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573520">Converting from secure to insecure</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573557">Periodic re-signing</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573571">NSEC3 and OPTOUT</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.4">Converting from insecure to secure</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.9">Dynamic DNS update method</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.17">Fully automatic zone signing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.26">Private-type records</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.33">DNSKEY rollovers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.35">Dynamic DNS update method</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.40">Automatic key rollovers</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.42">NSEC3PARAM rollovers via UPDATE</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.44">Converting from NSEC to NSEC3</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.46">Converting from NSEC3 to NSEC</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.48">Converting from secure to insecure</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.52">Periodic re-signing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.54">NSEC3 and OPTOUT</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#rfc5011.support">Dynamic Trust Anchor Management</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#rfc5011.support">Dynamic Trust Anchor Management</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573594">Validating Resolver</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573617">Authoritative Server</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.4">Validating Resolver</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.5">Authoritative Server</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#pkcs11">PKCS#11 (Cryptoki) support</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#pkcs11">PKCS#11 (Cryptoki) support</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613795">Prerequisites</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613804">Native PKCS#11</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613950">OpenSSL-based PKCS#11</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641062">PKCS#11 Tools</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641098">Using the HSM</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641452">Specifying the engine on the command line</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2641500">Running named with automatic zone re-signing</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.7">Prerequisites</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.8">Native PKCS#11</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.9">OpenSSL-based PKCS#11</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.10">PKCS#11 Tools</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.11">Using the HSM</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.12">Specifying the engine on the command line</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.13">Running named with automatic zone re-signing</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dlz-info">DLZ (Dynamically Loadable Zones)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dlz-info">DLZ (Dynamically Loadable Zones)</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613331">Configuring DLZ</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2613473">Sample DLZ Driver</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.14.7">Configuring DLZ</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.14.8">Sample DLZ Driver</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#dyndb-info">DynDB (Dynamic Database)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#dyndb-info">DynDB (Dynamic Database)</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2668419">Configuring DynDB</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2614349">Sample DynDB Module</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.15.6">Configuring DynDB</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.15.7">Sample DynDB Module</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch04.html#id2571527">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch04.html#id-1.5.16">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571794">Address Lookups Using AAAA Records</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571815">Address to Name Lookups Using Nibble Format</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.16.7">Address Lookups Using AAAA Records</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.16.8">Address to Name Lookups Using Nibble Format</a></span></dt>
</dl></dd>
</dl></dd>
<dt><span class="chapter"><a href="Bv9ARM.ch05.html">5. The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver</a></span></dt>
<dd><dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch05.html#id2571848">The Lightweight Resolver Library</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch05.html#id-1.6.3">The Lightweight Resolver Library</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt>
</dl></dd>
<dt><span class="chapter"><a href="Bv9ARM.ch06.html">6. <acronym class="acronym">BIND</acronym> 9 Configuration Reference</a></span></dt>
<dd><dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
<dd><dl>
-<dt><span class="sect
2"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2564126">Comment Syntax</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.6">Comment Syntax</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574276"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.7"><span class="command"><strong>acl</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#acl"><span class="command"><strong>acl</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574466"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.9"><span class="command"><strong>controls</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span class="command"><strong>controls</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574893"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574910"><span><strong class="command">include</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.11"><span class="command"><strong>include</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.12"><span class="command"><strong>include</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574934"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574957"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575051"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575187"><span><strong class="command">logging</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.13"><span class="command"><strong>key</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.14"><span class="command"><strong>key</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.15"><span class="command"><strong>logging</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.16"><span class="command"><strong>logging</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576512"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576677"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576773"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576822"><span><strong class="command">masters</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.17"><span class="command"><strong>lwres</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.18"><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.19"><span class="command"><strong>masters</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.20"><span class="command"><strong>masters</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576843"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.21"><span class="command"><strong>options</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#options"><span class="command"><strong>options</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span class="command"><strong>server</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span class="command"><strong>server</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#statschannels"><span><strong class="command">statistics-channels</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2592781"><span><strong class="command">statistics-channels</strong></span> Statement Definition and
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statschannels"><span class="command"><strong>statistics-channels</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.26"><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#trusted-keys"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593147"><span><strong class="command">trusted-keys</strong></span> Statement Definition
+<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted-keys"><span class="command"><strong>trusted-keys</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.28"><span class="command"><strong>trusted-keys</strong></span> Statement Definition
and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593269"><span><strong class="command">managed-keys</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#managed-keys"><span><strong class="command">managed-keys</strong></span> Statement Definition
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.29"><span class="command"><strong>managed-keys</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#managed-keys"><span class="command"><strong>managed-keys</strong></span> Statement Definition
and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593704"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span class="command"><strong>view</strong></span> Statement Grammar</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.32"><span class="command"><strong>view</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span class="command"><strong>zone</strong></span>
Statement Grammar</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2595733"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.34"><span class="command"><strong>zone</strong></span> Statement Definition and Usage</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2599438">Zone File</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7">Zone File</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2602566">Discussion of MX Records</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603113">Inverse Mapping in IPv4</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603308">Other Zone File Directives</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603581"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.4">Discussion of MX Records</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.6">Inverse Mapping in IPv4</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.7">Other Zone File Directives</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.7.8"><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statsfile">The Statistics File</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt>
</dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt></dl></dd>
</dl></dd>
<dt><span class="chapter"><a href="Bv9ARM.ch07.html">7. <acronym class="acronym">BIND</acronym> 9 Security Considerations</a></span></dt>
<dd><dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2608685"><span><strong class="command">Chroot</strong></span> and <span><strong class="command">Setuid</strong></span></a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.4"><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span></a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2608835">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2608894">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.4.7">The <span class="command"><strong>chroot</strong></span> Environment</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.4.8">Using the <span class="command"><strong>setuid</strong></span> Function</a></span></dt>
</dl></dd>
-<dt><span class="sect
1"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
</dl></dd>
<dt><span class="chapter"><a href="Bv9ARM.ch08.html">8. Troubleshooting</a></span></dt>
<dd><dl>
-<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2608974">Common Problems</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2608980">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
-<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2608992">Incrementing and Changing the Serial Number</a></span></dt>
-<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2609009">Where Can I Get Help?</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.3">Common Problems</a></span></dt>
+<dd><dl><dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.3.3">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
+<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.4">Incrementing and Changing the Serial Number</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.5">Where Can I Get Help?</a></span></dt>
</dl></dd>
<dt><span class="appendix"><a href="Bv9ARM.ch09.html">A. Release Notes</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#id-1.10.3">Release Notes for BIND Version 9.11.0pre-alpha</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_intro">Introduction</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_download">Download</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_security">Security Fixes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_features">New Features</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_changes">Feature Changes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_port">Porting Changes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_bugs">Bug Fixes</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#end_of_life">End of Life</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_thanks">Thank You</a></span></dt>
+</dl></dd>
+</dl></dd>
<dt><span class="appendix"><a href="Bv9ARM.ch10.html">B. A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="Bv9ARM.ch10.html#dns_history">DNS</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch10.html#bind_history">BIND</a></span></dt>
+</dl></dd>
<dt><span class="appendix"><a href="Bv9ARM.ch11.html">C. General <acronym class="acronym">DNS</acronym> Reference Information</a></span></dt>
<dd><dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch11.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt>
-<dt><span class="sect
1"><a href="Bv9ARM.ch11.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
<dd><dl>
-<dt><span class="sect
2"><a href="Bv9ARM.ch11.html#rfcs">Request for Comments (RFCs)</a></span></dt>
-<dt><span class="sect
2"><a href="Bv9ARM.ch11.html#internet_drafts">Internet Drafts</a></span></dt>
-<dt><span class="sect
2"><a href="Bv9ARM.ch11.html#id2612661">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#rfcs">Request for Comments (RFCs)</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#internet_drafts">Internet Drafts</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch11.html#id-1.12.4.5">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
</dl></dd>
</dl></dd>
<dt><span class="appendix"><a href="Bv9ARM.ch12.html">D. BIND 9 DNS Library Support</a></span></dt>
<dd><dl>
-<dt><span class="sect
1"><a href="Bv9ARM.ch12.html#bind9.library">BIND 9 DNS Library Support</a></span></dt>
+<dt><span class="sect
ion"><a href="Bv9ARM.ch12.html#bind9.library">BIND 9 DNS Library Support</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2616519">Prerequisite</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615300">Compilation</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615324">Installation</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615355">Known Defects/Restrictions</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615432">The dns.conf File</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2615459">Sample Applications</a></span></dt>
-<dt><span class="sect2"><a href="Bv9ARM.ch12.html#id2616705">Library References</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.5">Prerequisite</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.6">Compilation</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.7">Installation</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.8">Known Defects/Restrictions</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.9">The dns.conf File</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.10">Sample Applications</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch12.html#id-1.13.3.11">Library References</a></span></dt>
</dl></dd>
</dl></dd>
<dt><span class="reference"><a href="Bv9ARM.ch13.html">I. Manual pages</a></span></dt>
<span class="refentrytitle"><a href="man.dnssec-verify.html"><span class="application">dnssec-verify</span></a></span><span class="refpurpose"> — DNSSEC zone verification tool</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named-checkconf.html"><span class="application">named-checkconf</span></a></span><span class="refpurpose"> — named configuration file syntax checking tool</span>
+<span class="refentrytitle"><a href="man.lwresd.html"><span class="application">lwresd</span></a></span><span class="refpurpose"> — lightweight resolver daemon</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named-checkzone.html"><span class="application">named-checkzone</span></a></span><span class="refpurpose"> — zone file validity checking or converting tool</span>
+<span class="refentrytitle"><a href="man.named.html"><span class="application">named</span></a></span><span class="refpurpose"> — Internet domain name server</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named.html"><span class="application">named</span></a></span><span class="refpurpose"> — Internet domain name server</span>
+<span class="refentrytitle"><a href="man.named.conf.html"><code class="filename">named.conf</code></a></span><span class="refpurpose"> — configuration file for <span class="command"><strong>named</strong></span></span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named.conf.html"><code class="filename">named.conf</code></a></span><span class="refpurpose"> — configuration file for <span><strong class="command">named</strong></span></span>
+<span class="refentrytitle"><a href="man.named-checkconf.html"><span class="application">named-checkconf</span></a></span><span class="refpurpose"> — named configuration file syntax checking tool</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.lwresd.html"><span class="application">lwresd</span></a></span><span class="refpurpose"> — lightweight resolver daemon</span>
+<span class="refentrytitle"><a href="man.named-checkzone.html"><span class="application">named-checkzone</span></a></span><span class="refpurpose"> — zone file validity checking or converting tool</span>
</dt>
<dt>
<span class="refentrytitle"><a href="man.named-journalprint.html"><span class="application">named-journalprint</span></a></span><span class="refpurpose"> — print zone journal in human-readable form</span>
<span class="refentrytitle"><a href="man.isc-hmac-fixup.html"><span class="application">isc-hmac-fixup</span></a></span><span class="refpurpose"> — fixes HMAC keys generated by older versions of BIND</span>
</dt>
<dt>
-<span class="refentrytitle"><a href="man.named-journalprint.html"><span class="application">named-journalprint</span></a></span><span class="refpurpose"> — print zone journal in human-readable form</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="man.named-rrchecker.html"><span class="application">named-rrchecker</span></a></span><span class="refpurpose"> — A syntax checker for individual DNS resource records</span>
-</dt>
-<dt>
<span class="refentrytitle"><a href="man.nsec3hash.html"><span class="application">nsec3hash</span></a></span><span class="refpurpose"> — generate NSEC3 hash</span>
</dt>
</dl></dd>
</dl>
</div>
-</div>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ </div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
# PERFORMANCE OF THIS SOFTWARE.
-# $Id: Makefile.in,v 1.22 2009/02/12 23:47:56 tbox Exp $
-
srcdir = @srcdir@
VPATH = @srcdir@
top_srcdir = @top_srcdir@
clean::
rm -f Bv9ARM.aux Bv9ARM.brf Bv9ARM.glo Bv9ARM.idx Bv9ARM.toc
- rm -f Bv9ARM.log Bv9ARM.out Bv9ARM.tex Bv9ARM.tex.tmp
+ rm -f Bv9ARM.log Bv9ARM.out
rm -f notes.aux notes.brf notes.glo notes.idx notes.toc
- rm -f notes.log notes.out notes.tex notes.tex.tmp
+ rm -f notes.log notes.out
docclean manclean maintainer-clean:: clean
rm -f *.html ${PDFOBJS}
notes.html: notes-wrapper.xml notes.xml releaseinfo.xml pkgversion.xml noteversion.xml
expand notes-wrapper.xml | \
- ${XSLTPROC} --stringparam generate.toc "" ../xsl/isc-notes-html.xsl - |\
- @PERL@ html-fixup.pl > notes.html
-
-notes.tex: notes-wrapper.xml notes.xml releaseinfo.xml pkgversion.xml noteversion.xml
- expand notes-wrapper.xml | \
- ${XSLTPROC} --stringparam generate.toc "book toc" ${top_srcdir}/doc/xsl/pre-latex.xsl - | \
- ${XSLTPROC} ${top_srcdir}/doc/xsl/isc-notes-latex.xsl - | \
- @PERL@ latex-fixup.pl >$@.tmp
- if test -s $@.tmp; then mv $@.tmp $@; else rm -f $@.tmp; exit 1; fi
+ ${XSLTPROC} --stringparam generate.toc "" ../xsl/isc-notes-html.xsl - > notes.html
-notes.pdf: notes.tex releaseinfo.xml pkgversion.xml noteversion.xml
- rm -f notes-wrapper.aux notes.pdf notes.log
- ${PDFLATEX} '\batchmode\input notes.tex' || (rm -f $@ ; exit 1)
+notes.pdf: notes-wrapper.xml notes.xml releaseinfo.xml pkgversion.xml noteversion.xml
+ ${XSLTPROC} ${top_srcdir}/doc/xsl/pre-latex.xsl notes-wrapper.xml | \
+ ${DBLATEX} -c notes.conf -Pdoc.layout="mainmatter" -o notes.pdf -
Bv9ARM.html: Bv9ARM-book.xml releaseinfo.xml pkgversion.xml noteversion.xml
expand Bv9ARM-book.xml | \
expand Bv9ARM-book.xml | \
${XSLTPROC} -o Bv9ARM-all.html ../xsl/isc-docbook-html.xsl -
-Bv9ARM.tex: Bv9ARM-book.xml releaseinfo.xml pkgversion.xml noteversion.xml
+Bv9ARM.pdf: Bv9ARM-book.xml releaseinfo.xml pkgversion.xml noteversion.xml
expand Bv9ARM-book.xml | \
${XSLTPROC} ${top_srcdir}/doc/xsl/pre-latex.xsl - | \
- ${XSLTPROC} ${top_srcdir}/doc/xsl/isc-docbook-latex.xsl - | \
- @PERL@ latex-fixup.pl >$@.tmp
- if test -s $@.tmp; then mv $@.tmp $@; else rm -f $@.tmp; exit 1; fi
-
-Bv9ARM.dvi: Bv9ARM.tex releaseinfo.xml pkgversion.xml noteversion.xml
- rm -f Bv9ARM-book.aux Bv9ARM-book.dvi Bv9ARM-book.log
- ${LATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
- ${LATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
- ${LATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
-
-Bv9ARM.pdf: Bv9ARM.tex releaseinfo.xml pkgversion.xml noteversion.xml
- rm -f Bv9ARM-book.aux Bv9ARM-book.pdf Bv9ARM-book.log
- ${PDFLATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
- ${PDFLATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
- ${PDFLATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
+ ${DBLATEX} -c Bv9ARM.conf -o Bv9ARM.pdf -
FORCE:
-<?xml version="1.0" encoding="utf-8"?>
<!--
- Copyright (C) 2012-2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<!-- $Id$ -->
-
-<sect1 id="dlz-info">
- <title>DLZ (Dynamically Loadable Zones)</title>
+<!-- Converted by db4-upgrade version 1.0 -->
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="dlz-info"><info><title>DLZ (Dynamically Loadable Zones)</title></info>
+
<para>
DLZ (Dynamically Loadable Zones) is an extension to BIND 9 that allows
zone data to be retrieved directly from an external database. There is
zones in the database.)
</para>
- <sect2>
- <title>Configuring DLZ</title>
+ <section><info><title>Configuring DLZ</title></info>
+
<para>
A DLZ database is configured with a <command>dlz</command>
statement in <filename>named.conf</filename>:
</para>
<screen>
dlz example {
- database "dlopen driver.so <option>args</option>";
- search yes;
+ database "dlopen driver.so <option>args</option>";
+ search yes;
};
</screen>
<para>
</para>
<screen>
dlz other {
- database "dlopen driver.so <option>args</option>";
- search no;
+ database "dlopen driver.so <option>args</option>";
+ search no;
};
zone "." {
- type redirect;
- dlz other;
+ type redirect;
+ dlz other;
};
</screen>
- </sect2>
- <sect2>
- <title>Sample DLZ Driver</title>
+ </section>
+ <section><info><title>Sample DLZ Driver</title></info>
+
<para>
For guidance in implementation of DLZ modules, the directory
<filename>contrib/dlz/example</filename> contains a basic
</para>
<screen>
dlz other {
- database "dlopen driver.so example.nil";
+ database "dlopen driver.so example.nil";
};
</screen>
<para>
</para>
<screen>
example.nil. 3600 IN SOA example.nil. hostmaster.example.nil. (
- 123 900 600 86400 3600
- )
+ 123 900 600 86400 3600
+ )
example.nil. 3600 IN NS example.nil.
example.nil. 1800 IN A 10.53.0.1
</screen>
The sample driver is capable of retrieving information about the
querying client, and altering its response on the basis of this
information. To demonstrate this feature, the example driver
- responds to queries for "source-addr.<option>zonename</option>>/TXT"
+ responds to queries for "source-addr.<option>zonename</option>>/TXT"
with the source address of the query. Note, however, that this
record will *not* be included in AXFR or ANY responses. Normally,
this feature would be used to alter responses in some other fashion,
defines the API and should be included by any dynamically-linkable
DLZ module.
</para>
- </sect2>
-</sect1>
+ </section>
+</section>
-<?xml version="1.0" encoding="utf-8"?>
<!--
- Copyright (C) 2010, 2011, 2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<sect1 id="dnssec.dynamic.zones">
- <title>DNSSEC, Dynamic Zones, and Automatic Signing</title>
+<!-- Converted by db4-upgrade version 1.0 -->
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="dnssec.dynamic.zones"><info><title>DNSSEC, Dynamic Zones, and Automatic Signing</title></info>
+
<para>As of BIND 9.7.0 it is possible to change a dynamic zone
from insecure to signed and back again. A secure zone can use
either NSEC or NSEC3 chains.</para>
- <sect2>
- <title>Converting from insecure to secure</title>
- </sect2>
+ <section><info><title>Converting from insecure to secure</title></info>
+
+ </section>
<para>Changing a zone from insecure to secure can be done in two
ways: using a dynamic DNS update, or the
<command>auto-dnssec</command> zone option.</para>
in the key-directory, as specified in
<filename>named.conf</filename>:</para>
<programlisting>
- zone example.net {
- type master;
- update-policy local;
- file "dynamic/example.net/example.net";
- key-directory "dynamic/example.net";
- };
+ zone example.net {
+ type master;
+ update-policy local;
+ file "dynamic/example.net/example.net";
+ key-directory "dynamic/example.net";
+ };
</programlisting>
<para>If one KSK and one ZSK DNSKEY key have been generated, this
configuration will cause all records in the zone to be signed
with the ZSK, and the DNSKEY RRset to be signed with the KSK as
well. An NSEC chain will be generated as part of the initial
signing process.</para>
- <sect2>
- <title>Dynamic DNS update method</title>
- </sect2>
+ <section><info><title>Dynamic DNS update method</title></info>
+
+ </section>
<para>To insert the keys via dynamic update:</para>
<screen>
- % nsupdate
- > ttl 3600
- > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
- > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
- > send
+ % nsupdate
+ > ttl 3600
+ > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+ > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+ > send
</screen>
<para>While the update request will complete almost immediately,
the zone will not be completely signed until
wish the NSEC3 chain to have the OPTOUT bit set, set it in the
flags field of the NSEC3PARAM record.</para>
<screen>
- % nsupdate
- > ttl 3600
- > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
- > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
- > update add example.net NSEC3PARAM 1 1 100 1234567890
- > send
+ % nsupdate
+ > ttl 3600
+ > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+ > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+ > update add example.net NSEC3PARAM 1 1 100 1234567890
+ > send
</screen>
<para>Again, this update request will complete almost
immediately; however, the record won't show up until
be removed once the operation completes.</para>
<para>While the initial signing and NSEC/NSEC3 chain generation
is happening, other updates are possible as well.</para>
- <sect2>
- <title>Fully automatic zone signing</title>
- </sect2>
+ <section><info><title>Fully automatic zone signing</title></info>
+
+ </section>
<para>To enable automatic signing, add the
<command>auto-dnssec</command> option to the zone statement in
<filename>named.conf</filename>.
<command>update-policy</command> statement to the zone
configuration. If this has not been done, the configuration will
fail.</para>
- <sect2>
- <title>Private-type records</title>
- </sect2>
+ <section><info><title>Private-type records</title></info>
+
+ </section>
<para>The state of the signing process is signaled by
private-type records (with a default type value of 65534). When
signing is complete, these records will have a nonzero value for
0x20 NONSEC
</literallayout>
</para>
- <sect2>
- <title>DNSKEY rollovers</title>
- </sect2>
+ <section><info><title>DNSKEY rollovers</title></info>
+
+ </section>
<para>As with insecure-to-secure conversions, rolling DNSSEC
keys can be done in two ways: using a dynamic DNS update, or the
<command>auto-dnssec</command> zone option.</para>
- <sect2>
- <title>Dynamic DNS update method</title>
- </sect2>
+ <section><info><title>Dynamic DNS update method</title></info>
+
+ </section>
<para> To perform key rollovers via dynamic update, you need to add
the <filename>K*</filename> files for the new keys so that
<command>named</command> can find them. You can then add the new
specify the correct key.
<command>named</command> will clean out any signatures generated
by the old key after the update completes.</para>
- <sect2>
- <title>Automatic key rollovers</title>
- </sect2>
+ <section><info><title>Automatic key rollovers</title></info>
+
+ </section>
<para>When a new key reaches its activation date (as set by
<command>dnssec-keygen</command> or <command>dnssec-settime</command>),
if the <command>auto-dnssec</command> zone option is set to
signature validity periods expire. By default, this rollover
completes in 30 days, after which it will be safe to remove the
old key from the DNSKEY RRset.</para>
- <sect2>
- <title>NSEC3PARAM rollovers via UPDATE</title>
- </sect2>
+ <section><info><title>NSEC3PARAM rollovers via UPDATE</title></info>
+
+ </section>
<para>Add the new NSEC3PARAM record via dynamic update. When the
new NSEC3 chain has been generated, the NSEC3PARAM flag field
will be zero. At this point you can remove the old NSEC3PARAM
record. The old chain will be removed after the update request
completes.</para>
- <sect2>
- <title>Converting from NSEC to NSEC3</title>
- </sect2>
+ <section><info><title>Converting from NSEC to NSEC3</title></info>
+
+ </section>
<para>To do this, you just need to add an NSEC3PARAM record. When
the conversion is complete, the NSEC chain will have been removed
and the NSEC3PARAM record will have a zero flag field. The NSEC3
chain will be generated before the NSEC chain is
destroyed.</para>
- <sect2>
- <title>Converting from NSEC3 to NSEC</title>
- </sect2>
+ <section><info><title>Converting from NSEC3 to NSEC</title></info>
+
+ </section>
<para>To do this, use <command>nsupdate</command> to
remove all NSEC3PARAM records with a zero flag
field. The NSEC chain will be generated before the NSEC3 chain is
removed.</para>
- <sect2>
- <title>Converting from secure to insecure</title>
- </sect2>
+ <section><info><title>Converting from secure to insecure</title></info>
+
+ </section>
<para>To convert a signed zone to unsigned using dynamic DNS,
delete all the DNSKEY records from the zone apex using
<command>nsupdate</command>. All signatures, NSEC or NSEC3 chains,
zone statement is used, it should be removed or changed to
<command>allow</command> instead (or it will re-sign).
</para>
- <sect2>
- <title>Periodic re-signing</title>
- </sect2>
+ <section><info><title>Periodic re-signing</title></info>
+
+ </section>
<para>In any secure zone which supports dynamic updates, <command>named</command>
will periodically re-sign RRsets which have not been re-signed as
a result of some update action. The signature lifetimes will be
adjusted so as to spread the re-sign load over time rather than
all at once.</para>
- <sect2>
- <title>NSEC3 and OPTOUT</title>
- </sect2>
+ <section><info><title>NSEC3 and OPTOUT</title></info>
+
+ </section>
<para>
<command>named</command> only supports creating new NSEC3 chains
where all the NSEC3 records in the zone have the same OPTOUT
state of an individual NSEC3 record, the entire chain needs to be
changed if the OPTOUT state of an individual NSEC3 needs to be
changed.</para>
-</sect1>
+</section>
-<?xml version="1.0" encoding="utf-8"?>
<!--
- Copyright (C) 2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<sect1 id="dyndb-info">
- <title>DynDB (Dynamic Database)</title>
+<!-- Converted by db4-upgrade version 1.0 -->
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="dyndb-info"><info><title>DynDB (Dynamic Database)</title></info>
+
<para>
DynDB is an extension to BIND 9 which, like DLZ
(see <xref linkend="dlz-info"/>), allows zone data to be
<para>
A DynDB module supporting LDAP has been created by Red Hat
and is available from
- <ulink url="https://fedorahosted.org/bind-dyndb-ldap/"
- >https://fedorahosted.org/bind-dyndb-ldap/</ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://fedorahosted.org/bind-dyndb-ldap/">https://fedorahosted.org/bind-dyndb-ldap/</link>.
</para>
<para>
A sample DynDB module for testing and developer guidance
<filename>bin/tests/system/dyndb/driver</filename>.
</para>
- <sect2>
- <title>Configuring DynDB</title>
+ <section><info><title>Configuring DynDB</title></info>
+
<para>
A DynDB database is configured with a <command>dyndb</command>
statement in <filename>named.conf</filename>:
string to the DynDB module's initialization routine. Configuration
syntax will differ depending on the driver.
</para>
- </sect2>
- <sect2>
- <title>Sample DynDB Module</title>
+ </section>
+ <section><info><title>Sample DynDB Module</title></info>
+
<para>
For guidance in implementation of DynDB modules, the directory
<filename>bin/tests/system/dyndb/driver</filename>.
reverse zone. (Updates are not stored permanently; all updates are
lost when the server is restarted.)
</para>
- </sect2>
-</sect1>
+ </section>
+</section>
+++ /dev/null
-#!/usr/bin/perl -w
-#
-# Copyright (C) 2005, 2007, 2012, 2015 Internet Systems Consortium, Inc. ("ISC")
-#
-# Permission to use, copy, modify, and/or distribute this software for any
-# purpose with or without fee is hereby granted, provided that the above
-# copyright notice and this permission notice appear in all copies.
-#
-# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
-# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
-# AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
-# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
-# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
-# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
-# PERFORMANCE OF THIS SOFTWARE.
-
-# $Id: latex-fixup.pl,v 1.5 2007/06/19 23:47:13 tbox Exp $
-
-# Sadly, the final stages of generating a presentable PDF file always
-# seem to require some manual tweaking. Doesn't seem to matter what
-# typesetting tool one uses, sane forms of automation only go so far,
-# at least with present technology.
-#
-# This script is intended to be a collection of tweaks. The theory is
-# that, while we can't avoid the need for tweaking, we can at least
-# write the silly things down in a form that a program might be able
-# to execute. Undoubtedly everythig in here will break, eventually,
-# at which point it will need to be updated, but since the alternative
-# is to do the final editing by hand every time, this approach seems
-# the lesser of two evils.
-
-while (<>) {
-
- # Fix a db2latex oops. LaTeX2e does not like having tables with
- # duplicate names. Perhaps the dblatex project will fix this
- # someday, but we can get by with just deleting the offending
- # LaTeX commands for now.
-
- s/\\addtocounter\{table\}\{-1\}//g;
-
- # Line break in the middle of quoting one period looks weird.
-
- s/{\\texttt{{\.\\dbz{}}}}/\\mbox{{\\texttt{{\.\\dbz{}}}}}/;
-
- # Add any further tweaking here.
- # https://en.wikibooks.org/wiki/LaTeX/Special_Characters
- s/쎶/{\\"o}/; # umlaut o 쎶 or 쎶
-
- # Write out whatever we have now.
- print;
-}
-<?xml version="1.0" encoding="utf-8"?>
<!--
- Copyright (C) 2010, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<sect1 id="bind9.library">
- <title>BIND 9 DNS Library Support</title>
+<!-- Converted by db4-upgrade version 1.0 -->
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="bind9.library"><info><title>BIND 9 DNS Library Support</title></info>
+
<para>This version of BIND 9 "exports" its internal libraries so
that they can be used by third-party applications more easily (we
call them "export" libraries in this document). In addition to
libraries than BIND 9's internal event task system.</para>
</listitem>
</itemizedlist>
- <sect2>
- <title>Prerequisite</title>
+ <section><info><title>Prerequisite</title></info>
+
<para>GNU make is required to build the export libraries (other
part of BIND 9 can still be built with other types of make). In
the reminder of this document, "make" means GNU make. Note that
in some platforms you may need to invoke a different command name
than "make" (e.g. "gmake") to indicate it's GNU make.</para>
- </sect2>
- <sect2>
- <title>Compilation</title>
+ </section>
+ <section><info><title>Compilation</title></info>
+
<screen>
$ <userinput>./configure --enable-exportlib <replaceable>[other flags]</replaceable></userinput>
$ <userinput>make</userinput>
export version of the BIND 9 DNS library. Sample application
programs using the libraries will also be built under the
lib/export/samples directory (see below).</para>
- </sect2>
- <sect2>
- <title>Installation</title>
+ </section>
+ <section><info><title>Installation</title></info>
+
<screen>
$ <userinput>cd lib/export</userinput>
$ <userinput>make install</userinput>
To see how to build your own
application after the installation, see
<filename>lib/export/samples/Makefile-postinstall.in</filename>.</para>
- </sect2>
- <sect2>
- <title>Known Defects/Restrictions</title>
+ </section>
+ <section><info><title>Known Defects/Restrictions</title></info>
+
<itemizedlist>
<listitem>
<!-- TODO: what about AIX? -->
version are "debug" and "ndots".</para>
</listitem>
</itemizedlist>
- </sect2>
- <sect2>
- <title>The dns.conf File</title>
+ </section>
+ <section><info><title>The dns.conf File</title></info>
+
<para>The IRS library supports an "advanced" configuration file
related to the DNS library for configuration parameters that
would be beyond the capability of the
<command>trusted-keys</command>
statement is supported, whose syntax is the same as the same name
of statement for <filename>named.conf</filename>. (See
- <xref linkend="trusted-keys" /> for details.)</para>
- </sect2>
- <sect2>
- <title>Sample Applications</title>
+ <xref linkend="trusted-keys"/> for details.)</para>
+ </section>
+ <section><info><title>Sample Applications</title></info>
+
<para>Some sample application programs using this API are
provided for reference. The following is a brief description of
these applications.
</para>
- <sect3>
- <title>sample: a simple stub resolver utility</title>
+ <section><info><title>sample: a simple stub resolver utility</title></info>
+
<para>
It sends a query of a given name (of a given optional RR type) to a
specified recursive server, and prints the result as a list of
-t RRtype
</term>
<listitem><para>
- specify the RR type of the query. The default is the A RR.
+ specify the RR type of the query. The default is the A RR.
</para></listitem>
</varlistentry>
<varlistentry>
[-a algorithm] [-e] -k keyname -K keystring
</term>
<listitem><para>
- specify a command-line DNS key to validate the answer. For
- example, to specify the following DNSKEY of example.com:
+ specify a command-line DNS key to validate the answer. For
+ example, to specify the following DNSKEY of example.com:
<literallayout>
- example.com. 3600 IN DNSKEY 257 3 5 xxx
+ example.com. 3600 IN DNSKEY 257 3 5 xxx
</literallayout>
- specify the options as follows:
+ specify the options as follows:
<screen>
<userinput>
- -e -k example.com -K "xxx"
+ -e -k example.com -K "xxx"
</userinput>
</screen>
- -e means that this key is a zone's "key signing key" (as known
- as "secure Entry point").
- When -a is omitted rsasha1 will be used by default.
+ -e means that this key is a zone's "key signing key" (as known
+ as "secure Entry point").
+ When -a is omitted rsasha1 will be used by default.
</para></listitem>
</varlistentry>
<varlistentry>
-s domain:alt_server_address
</term>
<listitem><para>
- specify a separate recursive server address for the specific
- "domain". Example: -s example.com:2001:db8::1234
+ specify a separate recursive server address for the specific
+ "domain". Example: -s example.com:2001:db8::1234
</para></listitem>
</varlistentry>
<varlistentry>
<term>server_address</term>
<listitem><para>
- an IP(v4/v6) address of the recursive server to which queries
- are sent.
+ an IP(v4/v6) address of the recursive server to which queries
+ are sent.
</para></listitem>
</varlistentry>
<varlistentry>
<term>hostname</term>
<listitem><para>
- the domain name for the query
+ the domain name for the query
</para></listitem>
</varlistentry>
</variablelist>
- </sect3>
- <sect3>
- <title>sample-async: a simple stub resolver, working asynchronously</title>
+ </section>
+ <section><info><title>sample-async: a simple stub resolver, working asynchronously</title></info>
+
<para>
Similar to "sample", but accepts a list
of (query) domain names as a separate file and resolves the names
</listitem>
</varlistentry>
</variablelist>
- </sect3>
- <sect3>
- <title>sample-request: a simple DNS transaction client</title>
+ </section>
+ <section><info><title>sample-request: a simple DNS transaction client</title></info>
+
<para>
It sends a query to a specified server, and
prints the response with minimal processing. It doesn't act as a
</listitem>
</varlistentry>
</variablelist>
- </sect3>
- <sect3>
- <title>sample-gai: getaddrinfo() and getnameinfo() test code</title>
+ </section>
+ <section><info><title>sample-gai: getaddrinfo() and getnameinfo() test code</title></info>
+
<para>
This is a test program
to check getaddrinfo() and getnameinfo() behavior. It takes a
<para>
Usage: sample-gai hostname
</para>
- </sect3>
- <sect3>
- <title>sample-update: a simple dynamic update client program</title>
+ </section>
+ <section><info><title>sample-update: a simple dynamic update client program</title></info>
+
<para>
It accepts a single update command as a
command-line argument, sends an update request message to the
-a auth_server
</term>
<listitem><para>
- An IP address of the authoritative server that has authority
- for the zone containing the update name. This should normally
- be the primary authoritative server that accepts dynamic
- updates. It can also be a secondary server that is configured
- to forward update requests to the primary server.
+ An IP address of the authoritative server that has authority
+ for the zone containing the update name. This should normally
+ be the primary authoritative server that accepts dynamic
+ updates. It can also be a secondary server that is configured
+ to forward update requests to the primary server.
</para></listitem>
</varlistentry>
<varlistentry>
-k keyfile
</term>
<listitem><para>
- A TSIG key file to secure the update transaction. The keyfile
- format is the same as that for the nsupdate utility.
+ A TSIG key file to secure the update transaction. The keyfile
+ format is the same as that for the nsupdate utility.
</para></listitem>
</varlistentry>
<varlistentry>
-p prerequisite
</term>
<listitem><para>
- A prerequisite for the update (only one prerequisite can be
- specified). The prerequisite format is the same as that is
- accepted by the nsupdate utility.
+ A prerequisite for the update (only one prerequisite can be
+ specified). The prerequisite format is the same as that is
+ accepted by the nsupdate utility.
</para></listitem>
</varlistentry>
<varlistentry>
-r recursive_server
</term>
<listitem><para>
- An IP address of a recursive server that this utility will
- use. A recursive server may be necessary to identify the
- authoritative server address to which the update request is
- sent.
+ An IP address of a recursive server that this utility will
+ use. A recursive server may be necessary to identify the
+ authoritative server address to which the update request is
+ sent.
</para></listitem>
</varlistentry>
<varlistentry>
-z zonename
</term>
<listitem><para>
- The domain name of the zone that contains
+ The domain name of the zone that contains
</para></listitem>
</varlistentry>
<varlistentry>
(add|delete)
</term>
<listitem><para>
- Specify the type of update operation. Either "add" or "delete"
- must be specified.
+ Specify the type of update operation. Either "add" or "delete"
+ must be specified.
</para></listitem>
</varlistentry>
<varlistentry>
"update data"
</term>
<listitem><para>
- Specify the data to be updated. A typical example of the data
- would look like "name TTL RRtype RDATA".
+ Specify the data to be updated. A typical example of the data
+ would look like "name TTL RRtype RDATA".
</para></listitem>
</varlistentry>
</variablelist>
<para>
removes all RRs for foo.dynamic.example.com using the given key.
</para>
- </sect3>
- <sect3>
- <title>nsprobe: domain/name server checker in terms of RFC 4074</title>
+ </section>
+ <section><info><title>nsprobe: domain/name server checker in terms of RFC 4074</title></info>
+
<para>
It checks a set
of domains to see the name servers of the domains behave
-d
</term>
<listitem><para>
- run in the "debug" mode. with this option nsprobe will dump
- every RRs it receives.
+ run in the "debug" mode. with this option nsprobe will dump
+ every RRs it receives.
</para></listitem>
</varlistentry>
<varlistentry>
-v
</term>
<listitem><para>
- increase verbosity of other normal log messages. This can be
- specified multiple times
+ increase verbosity of other normal log messages. This can be
+ specified multiple times
</para></listitem>
</varlistentry>
<varlistentry>
-c cache_address
</term>
<listitem><para>
- specify an IP address of a recursive (caching) name server.
- nsprobe uses this server to get the NS RRset of each domain and
- the A and/or AAAA RRsets for the name servers. The default
- value is 127.0.0.1.
+ specify an IP address of a recursive (caching) name server.
+ nsprobe uses this server to get the NS RRset of each domain and
+ the A and/or AAAA RRsets for the name servers. The default
+ value is 127.0.0.1.
</para></listitem>
</varlistentry>
<varlistentry>
input_file
</term>
<listitem><para>
- a file name containing a list of domain (zone) names to be
- probed. when omitted the standard input will be used. Each
- line of the input file specifies a single domain name such as
- "example.com". In general this domain name must be the apex
- name of some DNS zone (unlike normal "host names" such as
- "www.example.com"). nsprobe first identifies the NS RRsets for
- the given domain name, and sends A and AAAA queries to these
- servers for some "widely used" names under the zone;
- specifically, adding "www" and "ftp" to the zone name.
+ a file name containing a list of domain (zone) names to be
+ probed. when omitted the standard input will be used. Each
+ line of the input file specifies a single domain name such as
+ "example.com". In general this domain name must be the apex
+ name of some DNS zone (unlike normal "host names" such as
+ "www.example.com"). nsprobe first identifies the NS RRsets for
+ the given domain name, and sends A and AAAA queries to these
+ servers for some "widely used" names under the zone;
+ specifically, adding "www" and "ftp" to the zone name.
</para></listitem>
</varlistentry>
</variablelist>
- </sect3>
- </sect2>
- <sect2>
- <title>Library References</title>
+ </section>
+ </section>
+ <section><info><title>Library References</title></info>
+
<para>As of this writing, there is no formal "manual" of the
libraries, except this document, header files (some of them
provide pretty detailed explanations), and sample application
programs.</para>
- </sect2>
-</sect1>
-<!-- $Id: libdns.xml,v 1.3 2010/02/03 23:49:07 tbox Exp $ -->
+ </section>
+</section>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<informaltable colsep="0" rowsep="0">
+<!-- Converted by db4-upgrade version 1.0 -->
+<informaltable xmlns="http://docbook.org/ns/docbook" version="5.0" colsep="0" rowsep="0">
<tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
<colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
<colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>arpaname</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.ddns-confgen.html" title="ddns-confgen">
<link rel="next" href="man.dnstap-read.html" title="dnstap-read">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.arpaname"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">arpaname</span> — translate IP addresses to the corresponding ARPA names</p>
+<p>
+ <span class="application">arpaname</span>
+ — translate IP addresses to the corresponding ARPA names
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">arpaname</code> {<em class="replaceable"><code>ipaddress </code></em>...}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2719185"></a><h2>DESCRIPTION</h2>
-<p>
- <span><strong class="command">arpaname</strong></span> translates IP addresses (IPv4 and
+ <div class="cmdsynopsis"><p>
+ <code class="command">arpaname</code>
+ {<em class="replaceable"><code>ipaddress </code></em>...}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.27.7"></a><h2>DESCRIPTION</h2>
+
+ <p>
+ <span class="command"><strong>arpaname</strong></span> translates IP addresses (IPv4 and
IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745619"></a><h2>SEE ALSO</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.27.8"></a><h2>SEE ALSO</h2>
+
+ <p>
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745633"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>ddns-confgen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.rndc-confgen.html" title="rndc-confgen">
<link rel="next" href="man.arpaname.html" title="arpaname">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.ddns-confgen"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">ddns-confgen</span> — ddns key generation tool</p>
+<p>
+ <span class="application">ddns-confgen</span>
+ — ddns key generation tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">tsig-keygen</code> [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-h</code>] [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>] [name]</p></div>
-<div class="cmdsynopsis"><p><code class="command">ddns-confgen</code> [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-h</code>] [<code class="option">-k <em class="replaceable"><code>keyname</code></em></code>] [<code class="option">-q</code>] [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>] [ -s <em class="replaceable"><code>name</code></em> | -z <em class="replaceable"><code>zone</code></em> ]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2719524"></a><h2>DESCRIPTION</h2>
-<p>
- <span><strong class="command">tsig-keygen</strong></span> and <span><strong class="command">ddns-confgen</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">tsig-keygen</code>
+ [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>]
+ [name]
+ </p></div>
+ <div class="cmdsynopsis"><p>
+ <code class="command">ddns-confgen</code>
+ [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-k <em class="replaceable"><code>keyname</code></em></code>]
+ [<code class="option">-q</code>]
+ [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>]
+ [
+ -s <em class="replaceable"><code>name</code></em>
+ | -z <em class="replaceable"><code>zone</code></em>
+ ]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.26.7"></a><h2>DESCRIPTION</h2>
+
+ <p>
+ <span class="command"><strong>tsig-keygen</strong></span> and <span class="command"><strong>ddns-confgen</strong></span>
are invocation methods for a utility that generates keys for use
in TSIG signing. The resulting keys can be used, for example,
to secure dynamic DNS updates to a zone or for the
- <span><strong class="command">rndc</strong></span> command channel.
+ <span class="command"><strong>rndc</strong></span> command channel.
</p>
-<p>
- When run as <span><strong class="command">tsig-keygen</strong></span>, a domain name
+
+ <p>
+ When run as <span class="command"><strong>tsig-keygen</strong></span>, a domain name
can be specified on the command line which will be used as
the name of the generated key. If no name is specified,
the default is <code class="constant">tsig-key</code>.
</p>
-<p>
- When run as <span><strong class="command">ddns-confgen</strong></span>, the generated
+
+ <p>
+ When run as <span class="command"><strong>ddns-confgen</strong></span>, the generated
key is accompanied by configuration text and instructions
- that can be used with <span><strong class="command">nsupdate</strong></span> and
- <span><strong class="command">named</strong></span> when setting up dynamic DNS,
- including an example <span><strong class="command">update-policy</strong></span>
+ that can be used with <span class="command"><strong>nsupdate</strong></span> and
+ <span class="command"><strong>named</strong></span> when setting up dynamic DNS,
+ including an example <span class="command"><strong>update-policy</strong></span>
statement. (This usage similar to the
- <span><strong class="command">rndc-confgen</strong></span> command for setting
+ <span class="command"><strong>rndc-confgen</strong></span> command for setting
up command channel security.)
</p>
-<p>
- Note that <span><strong class="command">named</strong></span> itself can configure a
- local DDNS key for use with <span><strong class="command">nsupdate -l</strong></span>:
+
+ <p>
+ Note that <span class="command"><strong>named</strong></span> itself can configure a
+ local DDNS key for use with <span class="command"><strong>nsupdate -l</strong></span>:
it does this when a zone is configured with
- <span><strong class="command">update-policy local;</strong></span>.
- <span><strong class="command">ddns-confgen</strong></span> is only needed when a
+ <span class="command"><strong>update-policy local;</strong></span>.
+ <span class="command"><strong>ddns-confgen</strong></span> is only needed when a
more elaborate configuration is required: for instance,
- if <span><strong class="command">nsupdate</strong></span> is to be used from a remote
+ if <span class="command"><strong>nsupdate</strong></span> is to be used from a remote
system.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2719696"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.26.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the algorithm to use for the TSIG key. Available
choices are: hmac-md5, hmac-sha1, hmac-sha224, hmac-sha256,
hmac-sha384 and hmac-sha512. The default is hmac-sha256.
Options are case-insensitive, and the "hmac-" prefix
may be omitted.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints a short summary of options and arguments.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-k <em class="replaceable"><code>keyname</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the key name of the DDNS authentication key.
The default is <code class="constant">ddns-key</code> when neither
the <code class="option">-s</code> nor <code class="option">-z</code> option is
<code class="constant">ddns-key.example.com.</code>
The key name must have the format of a valid domain name,
consisting of letters, digits, hyphens and periods.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-q</span></dt>
-<dd><p>
- (<span><strong class="command">ddns-confgen</strong></span> only.) Quiet mode: Print
+<dd>
+ <p>
+ (<span class="command"><strong>ddns-confgen</strong></span> only.) Quiet mode: Print
only the key, with no explanatory text or usage examples;
- This is essentially identical to <span><strong class="command">tsig-keygen</strong></span>.
- </p></dd>
+ This is essentially identical to <span class="command"><strong>tsig-keygen</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-r <em class="replaceable"><code>randomfile</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies a source of random data for generating the
authorization. If the operating system does not provide a
<code class="filename">/dev/random</code> or equivalent device, the
instead of the default. The special value
<code class="filename">keyboard</code> indicates that keyboard input
should be used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s <em class="replaceable"><code>name</code></em></span></dt>
-<dd><p>
- (<span><strong class="command">ddns-confgen</strong></span> only.)
+<dd>
+ <p>
+ (<span class="command"><strong>ddns-confgen</strong></span> only.)
Generate configuration example to allow dynamic updates
- of a single hostname. The example <span><strong class="command">named.conf</strong></span>
+ of a single hostname. The example <span class="command"><strong>named.conf</strong></span>
text shows how to set an update policy for the specified
<em class="replaceable"><code>name</code></em>
using the "name" nametype. The default key name is
Note that the "self" nametype cannot be used, since
the name to be updated may differ from the key name.
This option cannot be used with the <code class="option">-z</code> option.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-z <em class="replaceable"><code>zone</code></em></span></dt>
-<dd><p>
- (<span><strong class="command">ddns-confgen</strong></span> only.)
+<dd>
+ <p>
+ (<span class="command"><strong>ddns-confgen</strong></span> only.)
Generate configuration example to allow dynamic updates
- of a zone: The example <span><strong class="command">named.conf</strong></span> text
+ of a zone: The example <span class="command"><strong>named.conf</strong></span> text
shows how to set an update policy for the specified
<em class="replaceable"><code>zone</code></em>
using the "zonesub" nametype, allowing updates to
all subdomain names within that
<em class="replaceable"><code>zone</code></em>.
This option cannot be used with the <code class="option">-s</code> option.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745512"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">nsupdate</span>(1)</span>,
- <span class="citerefentry"><span class="refentrytitle">named.conf</span>(5)</span>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.26.9"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">nsupdate</span>(1)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named.conf</span>(5)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745550"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>delv</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.host.html" title="host">
<link rel="next" href="man.dnssec-checkds.html" title="dnssec-checkds">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.delv"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p>delv — DNS lookup and validation utility</p>
+<p>
+ delv
+ — DNS lookup and validation utility
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">delv</code> [@server] [<code class="option">-4</code>] [<code class="option">-6</code>] [<code class="option">-a <em class="replaceable"><code>anchor-file</code></em></code>] [<code class="option">-b <em class="replaceable"><code>address</code></em></code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-d <em class="replaceable"><code>level</code></em></code>] [<code class="option">-i</code>] [<code class="option">-m</code>] [<code class="option">-p <em class="replaceable"><code>port#</code></em></code>] [<code class="option">-q <em class="replaceable"><code>name</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-x <em class="replaceable"><code>addr</code></em></code>] [name] [type] [class] [queryopt...]</p></div>
-<div class="cmdsynopsis"><p><code class="command">delv</code> [<code class="option">-h</code>]</p></div>
-<div class="cmdsynopsis"><p><code class="command">delv</code> [<code class="option">-v</code>]</p></div>
-<div class="cmdsynopsis"><p><code class="command">delv</code> [queryopt...] [query...]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2619310"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">delv</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">delv</code>
+ [@server]
+ [<code class="option">-4</code>]
+ [<code class="option">-6</code>]
+ [<code class="option">-a <em class="replaceable"><code>anchor-file</code></em></code>]
+ [<code class="option">-b <em class="replaceable"><code>address</code></em></code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-d <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-i</code>]
+ [<code class="option">-m</code>]
+ [<code class="option">-p <em class="replaceable"><code>port#</code></em></code>]
+ [<code class="option">-q <em class="replaceable"><code>name</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>type</code></em></code>]
+ [<code class="option">-x <em class="replaceable"><code>addr</code></em></code>]
+ [name]
+ [type]
+ [class]
+ [queryopt...]
+ </p></div>
+
+ <div class="cmdsynopsis"><p>
+ <code class="command">delv</code>
+ [<code class="option">-h</code>]
+ </p></div>
+
+ <div class="cmdsynopsis"><p>
+ <code class="command">delv</code>
+ [<code class="option">-v</code>]
+ </p></div>
+
+ <div class="cmdsynopsis"><p>
+ <code class="command">delv</code>
+ [queryopt...]
+ [query...]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.4.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>delv</strong></span>
(Domain Entity Lookup & Validation) is a tool for sending
DNS queries and validating the results, using the same internal
- resolver and validator logic as <span><strong class="command">named</strong></span>.
+ resolver and validator logic as <span class="command"><strong>named</strong></span>.
</p>
-<p>
- <span><strong class="command">delv</strong></span> will send to a specified name server all
+ <span class="command"><strong>delv</strong></span> will send to a specified name server all
queries needed to fetch and validate the requested data; this
includes the original requested query, subsequent queries to follow
CNAME or DNAME chains, and queries for DNSKEY, DS and DLV records
behavior of a name server configured for DNSSEC validating and
forwarding.
</p>
-<p>
By default, responses are validated using built-in DNSSEC trust
anchors for the root zone (".") and for the ISC DNSSEC lookaside
validation zone ("dlv.isc.org"). Records returned by
- <span><strong class="command">delv</strong></span> are either fully validated or
+ <span class="command"><strong>delv</strong></span> are either fully validated or
were not signed. If validation fails, an explanation of
the failure is included in the output; the validation process
- can be traced in detail. Because <span><strong class="command">delv</strong></span> does
+ can be traced in detail. Because <span class="command"><strong>delv</strong></span> does
not rely on an external server to carry out validation, it can
be used to check the validity of DNS responses in environments
where local name servers may not be trustworthy.
</p>
-<p>
Unless it is told to query a specific name server,
- <span><strong class="command">delv</strong></span> will try each of the servers listed in
+ <span class="command"><strong>delv</strong></span> will try each of the servers listed in
<code class="filename">/etc/resolv.conf</code>. If no usable server
- addresses are found, <span><strong class="command">delv</strong></span> will send
+ addresses are found, <span class="command"><strong>delv</strong></span> will send
queries to the localhost addresses (127.0.0.1 for IPv4, ::1
for IPv6).
</p>
-<p>
When no command line arguments or options are given,
- <span><strong class="command">delv</strong></span> will perform an NS query for "."
+ <span class="command"><strong>delv</strong></span> will perform an NS query for "."
(the root zone).
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2619451"></a><h2>SIMPLE USAGE</h2>
-<p>
- A typical invocation of <span><strong class="command">delv</strong></span> looks like:
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.4.8"></a><h2>SIMPLE USAGE</h2>
+
+
+ <p>
+ A typical invocation of <span class="command"><strong>delv</strong></span> looks like:
</p>
<pre class="programlisting"> delv @server name type </pre>
<p>
where:
</p>
-<div class="variablelist"><dl>
+<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="constant">server</code></span></dt>
<dd>
-<p>
is the name or IP address of the name server to query. This
can be an IPv4 address in dotted-decimal notation or an IPv6
address in colon-delimited notation. When the supplied
<em class="parameter"><code>server</code></em> argument is a hostname,
- <span><strong class="command">delv</strong></span> resolves that name before
+ <span class="command"><strong>delv</strong></span> resolves that name before
querying that name server (note, however, that this
initial lookup is <span class="emphasis"><em>not</em></span> validated
by DNSSEC).
</p>
-<p>
If no <em class="parameter"><code>server</code></em> argument is
- provided, <span><strong class="command">delv</strong></span> consults
+ provided, <span class="command"><strong>delv</strong></span> consults
<code class="filename">/etc/resolv.conf</code>; if an
address is found there, it queries the name server at
that address. If either of the <code class="option">-4</code> or
<code class="option">-6</code> options are in use, then
only addresses for the corresponding transport
will be tried. If no usable addresses are found,
- <span><strong class="command">delv</strong></span> will send queries to
+ <span class="command"><strong>delv</strong></span> will send queries to
the localhost addresses (127.0.0.1 for IPv4,
::1 for IPv6).
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="constant">name</code></span></dt>
-<dd><p>
+<dd>
+ <p>
is the domain name to be looked up.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="constant">type</code></span></dt>
-<dd><p>
+<dd>
+ <p>
indicates what type of query is required —
ANY, A, MX, etc.
<em class="parameter"><code>type</code></em> can be any valid query
type. If no
<em class="parameter"><code>type</code></em> argument is supplied,
- <span><strong class="command">delv</strong></span> will perform a lookup for an
+ <span class="command"><strong>delv</strong></span> will perform a lookup for an
A record.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
<p>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620129"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.4.9"></a><h2>OPTIONS</h2>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-a <em class="replaceable"><code>anchor-file</code></em></span></dt>
<dd>
-<p>
Specifies a file from which to read DNSSEC trust anchors.
The default is <code class="filename">/etc/bind.keys</code>, which
is included with <acronym class="acronym">BIND</acronym> 9 and contains
trust anchors for the root zone (".") and for the ISC
DNSSEC lookaside validation zone ("dlv.isc.org").
</p>
-<p>
Keys that do not match the root or DLV trust-anchor
names are ignored; these key names can be overridden
using the <code class="option">+dlv=NAME</code> or
<code class="option">+root=NAME</code> options.
</p>
-<p>
Note: When reading the trust anchor file,
- <span><strong class="command">delv</strong></span> treats <code class="option">managed-keys</code>
+ <span class="command"><strong>delv</strong></span> treats <code class="option">managed-keys</code>
statements and <code class="option">trusted-keys</code> statements
identically. That is, for a managed key, it is the
<span class="emphasis"><em>initial</em></span> key that is trusted; RFC 5011
- key management is not supported. <span><strong class="command">delv</strong></span>
+ key management is not supported. <span class="command"><strong>delv</strong></span>
will not consult the managed-keys database maintained by
- <span><strong class="command">named</strong></span>. This means that if either of the
+ <span class="command"><strong>named</strong></span>. This means that if either of the
keys in <code class="filename">/etc/bind.keys</code> is revoked
and rolled over, it will be necessary to update
<code class="filename">/etc/bind.keys</code> to use DNSSEC
- validation in <span><strong class="command">delv</strong></span>.
+ validation in <span class="command"><strong>delv</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term">-b <em class="replaceable"><code>address</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the source IP address of the query to
<em class="parameter"><code>address</code></em>. This must be a valid address
on one of the host's network interfaces or "0.0.0.0" or "::".
An optional source port may be specified by appending
"#<port>"
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the query class for the requested data. Currently,
- only class "IN" is supported in <span><strong class="command">delv</strong></span>
+ only class "IN" is supported in <span class="command"><strong>delv</strong></span>
and any other value is ignored.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-d <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the systemwide debug level to <code class="option">level</code>.
The allowed range is from 0 to 99.
The default is 0 (no debugging).
- Debugging traces from <span><strong class="command">delv</strong></span> become
+ Debugging traces from <span class="command"><strong>delv</strong></span> become
more verbose as the debug level increases.
See the <code class="option">+mtrace</code>, <code class="option">+rtrace</code>,
and <code class="option">+vtrace</code> options below for additional
debugging details.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
- Display the <span><strong class="command">delv</strong></span> help usage output and exit.
- </p></dd>
+<dd>
+ <p>
+ Display the <span class="command"><strong>delv</strong></span> help usage output and exit.
+ </p>
+ </dd>
<dt><span class="term">-i</span></dt>
-<dd><p>
+<dd>
+ <p>
Insecure mode. This disables internal DNSSEC validation.
(Note, however, this does not set the CD bit on upstream
queries. If the server being queried is performing DNSSEC
validation, then it will not return invalid data; this
- can cause <span><strong class="command">delv</strong></span> to time out. When it
+ can cause <span class="command"><strong>delv</strong></span> to time out. When it
is necessary to examine invalid data to debug a DNSSEC
- problem, use <span><strong class="command">dig +cd</strong></span>.)
- </p></dd>
+ problem, use <span class="command"><strong>dig +cd</strong></span>.)
+ </p>
+ </dd>
<dt><span class="term">-m</span></dt>
-<dd><p>
+<dd>
+ <p>
Enables memory usage debugging.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>port#</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies a destination port to use for queries instead of
the standard DNS port number 53. This option would be used
with a name server that has been configured to listen
for queries on a non-standard port number.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-q <em class="replaceable"><code>name</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the query name to <em class="parameter"><code>name</code></em>.
While the query name can be specified without using the
<code class="option">-q</code>, it is sometimes necessary to disambiguate
names from types or classes (for example, when looking up the
name "ns", which could be misinterpreted as the type NS,
or "ch", which could be misinterpreted as class CH).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>type</code></em></span></dt>
<dd>
-<p>
Sets the query type to <em class="parameter"><code>type</code></em>, which
can be any valid query type supported in BIND 9 except
for zone transfer types AXFR and IXFR. As with
query name type or class when they are ambiguous.
it is sometimes necessary to disambiguate names from types.
</p>
-<p>
The default query type is "A", unless the <code class="option">-x</code>
option is supplied to indicate a reverse lookup, in which case
it is "PTR".
</p>
-</dd>
+ </dd>
<dt><span class="term">-v</span></dt>
-<dd><p>
- Print the <span><strong class="command">delv</strong></span> version and exit.
- </p></dd>
+<dd>
+ <p>
+ Print the <span class="command"><strong>delv</strong></span> version and exit.
+ </p>
+ </dd>
<dt><span class="term">-x <em class="replaceable"><code>addr</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Performs a reverse lookup, mapping an addresses to
a name. <em class="parameter"><code>addr</code></em> is an IPv4 address in
dotted-decimal notation, or a colon-delimited IPv6 address.
When <code class="option">-x</code> is used, there is no need to provide
the <em class="parameter"><code>name</code></em> or <em class="parameter"><code>type</code></em>
- arguments. <span><strong class="command">delv</strong></span> automatically performs a
+ arguments. <span class="command"><strong>delv</strong></span> automatically performs a
lookup for a name like <code class="literal">11.12.13.10.in-addr.arpa</code>
and sets the query type to PTR. IPv6 addresses are looked up
using nibble format under the IP6.ARPA domain.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-4</span></dt>
-<dd><p>
- Forces <span><strong class="command">delv</strong></span> to only use IPv4.
- </p></dd>
+<dd>
+ <p>
+ Forces <span class="command"><strong>delv</strong></span> to only use IPv4.
+ </p>
+ </dd>
<dt><span class="term">-6</span></dt>
-<dd><p>
- Forces <span><strong class="command">delv</strong></span> to only use IPv6.
- </p></dd>
+<dd>
+ <p>
+ Forces <span class="command"><strong>delv</strong></span> to only use IPv6.
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2675155"></a><h2>QUERY OPTIONS</h2>
-<p><span><strong class="command">delv</strong></span>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.4.10"></a><h2>QUERY OPTIONS</h2>
+
+
+ <p><span class="command"><strong>delv</strong></span>
provides a number of query options which affect the way results are
displayed, and in some cases the way lookups are performed.
</p>
-<p>
+
+ <p>
Each query option is identified by a keyword preceded by a plus sign
(<code class="literal">+</code>). Some keywords set or reset an
option. These may be preceded by the string
The query options are:
</p>
-<div class="variablelist"><dl>
+<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="option">+[no]cdflag</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Controls whether to set the CD (checking disabled) bit in
- queries sent by <span><strong class="command">delv</strong></span>. This may be useful
+ queries sent by <span class="command"><strong>delv</strong></span>. This may be useful
when troubleshooting DNSSEC problems from behind a validating
resolver. A validating resolver will block invalid responses,
making it difficult to retrieve them for analysis. Setting
the CD flag on queries will cause the resolver to return
- invalid responses, which <span><strong class="command">delv</strong></span> can then
+ invalid responses, which <span class="command"><strong>delv</strong></span> can then
validate internally and report the errors in detail.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]class</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Controls whether to display the CLASS when printing
a record. The default is to display the CLASS.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]ttl</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Controls whether to display the TTL when printing
a record. The default is to display the TTL.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]rtrace</code></span></dt>
<dd>
-<p>
Toggle resolver fetch logging. This reports the
- name and type of each query sent by <span><strong class="command">delv</strong></span>
+ name and type of each query sent by <span class="command"><strong>delv</strong></span>
in the process of carrying out the resolution and validation
process: this includes including the original query and
all subsequent queries to follow CNAMEs and to establish a
chain of trust for DNSSEC validation.
</p>
-<p>
This is equivalent to setting the debug level to 1 in
the "resolver" logging category. Setting the systemwide
debug level to 1 using the <code class="option">-d</code> option will
product the same output (but will affect other logging
categories as well).
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="option">+[no]mtrace</code></span></dt>
<dd>
-<p>
Toggle message logging. This produces a detailed dump of
- the responses received by <span><strong class="command">delv</strong></span> in the
+ the responses received by <span class="command"><strong>delv</strong></span> in the
process of carrying out the resolution and validation process.
</p>
-<p>
This is equivalent to setting the debug level to 10
for the "packets" module of the "resolver" logging
category. Setting the systemwide debug level to 10 using
the <code class="option">-d</code> option will produce the same output
(but will affect other logging categories as well).
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="option">+[no]vtrace</code></span></dt>
<dd>
-<p>
Toggle validation logging. This shows the internal
process of the validator as it determines whether an
answer is validly signed, unsigned, or invalid.
</p>
-<p>
This is equivalent to setting the debug level to 3
for the "validator" module of the "dnssec" logging
category. Setting the systemwide debug level to 3 using
the <code class="option">-d</code> option will produce the same output
(but will affect other logging categories as well).
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="option">+[no]short</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Provide a terse answer. The default is to print the answer in a
verbose form.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]comments</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggle the display of comment lines in the output. The default
is to print comments.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]rrcomments</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggle the display of per-record comments in the output (for
example, human-readable key information about DNSKEY records).
The default is to print per-record comments.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]crypto</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggle the display of cryptographic fields in DNSSEC records.
The contents of these field are unnecessary to debug most DNSSEC
validation failures and removing them makes it easier to see
When omitted they are replaced by the string "[omitted]" or
in the DNSKEY case the key id is displayed as the replacement,
e.g. "[ key id = value ]".
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]trust</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Controls whether to display the trust level when printing
a record. The default is to display the trust level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]split[=W]</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Split long hex- or base64-formatted fields in resource
records into chunks of <em class="parameter"><code>W</code></em> characters
(where <em class="parameter"><code>W</code></em> is rounded up to the nearest
<em class="parameter"><code>+split=0</code></em> causes fields not to be
split at all. The default is 56 characters, or 44 characters
when multiline mode is active.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]all</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set or clear the display options
<code class="option">+[no]comments</code>,
<code class="option">+[no]rrcomments</code>, and
<code class="option">+[no]trust</code> as a group.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]multiline</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Print long records (such as RRSIG, DNSKEY, and SOA records)
in a verbose multi-line format with human-readable comments.
The default is to print each record on a single line, to
- facilitate machine parsing of the <span><strong class="command">delv</strong></span>
+ facilitate machine parsing of the <span class="command"><strong>delv</strong></span>
output.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]dnssec</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Indicates whether to display RRSIG records in the
- <span><strong class="command">delv</strong></span> output. The default is to
- do so. Note that (unlike in <span><strong class="command">dig</strong></span>)
+ <span class="command"><strong>delv</strong></span> output. The default is to
+ do so. Note that (unlike in <span class="command"><strong>dig</strong></span>)
this does <span class="emphasis"><em>not</em></span> control whether to
request DNSSEC records or whether to validate them.
DNSSEC records are always requested, and validation
will always occur unless suppressed by the use of
<code class="option">-i</code> or <code class="option">+noroot</code> and
<code class="option">+nodlv</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]root[=ROOT]</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Indicates whether to perform conventional (non-lookaside)
DNSSEC validation, and if so, specifies the
name of a trust anchor. The default is to validate using
a built-in key. If specifying a different trust anchor,
then <code class="option">-a</code> must be used to specify a file
containing the key.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]dlv[=DLV]</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Indicates whether to perform DNSSEC lookaside validation,
and if so, specifies the name of the DLV trust anchor.
The default is to perform lookaside validation using
built-in key. If specifying a different name, then
<code class="option">-a</code> must be used to specify a file
containing the DLV key.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]tcp</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Controls whether to use TCP when sending queries.
The default is to use UDP unless a truncated
response has been received.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
<p>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2675685"></a><h2>FILES</h2>
-<p><code class="filename">/etc/bind.keys</code></p>
-<p><code class="filename">/etc/resolv.conf</code></p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2675704"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dig</span>(1)</span>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.4.11"></a><h2>FILES</h2>
+
+ <p><code class="filename">/etc/bind.keys</code></p>
+ <p><code class="filename">/etc/resolv.conf</code></p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.4.12"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dig</span>(1)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
<em class="citetitle">RFC4034</em>,
<em class="citetitle">RFC4035</em>,
<em class="citetitle">RFC4431</em>,
<em class="citetitle">RFC5074</em>,
<em class="citetitle">RFC5155</em>.
</p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dig</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="next" href="man.host.html" title="host">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dig"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p>dig — DNS lookup utility</p>
+<p>
+ dig
+ — DNS lookup utility
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dig</code> [@server] [<code class="option">-b <em class="replaceable"><code>address</code></em></code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-f <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-k <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-m</code>] [<code class="option">-p <em class="replaceable"><code>port#</code></em></code>] [<code class="option">-q <em class="replaceable"><code>name</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-v</code>] [<code class="option">-x <em class="replaceable"><code>addr</code></em></code>] [<code class="option">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]name:key</code></em></code>] [<code class="option">-4</code>] [<code class="option">-6</code>] [name] [type] [class] [queryopt...]</p></div>
-<div class="cmdsynopsis"><p><code class="command">dig</code> [<code class="option">-h</code>]</p></div>
-<div class="cmdsynopsis"><p><code class="command">dig</code> [global-queryopt...] [query...]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2617245"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dig</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dig</code>
+ [@server]
+ [<code class="option">-b <em class="replaceable"><code>address</code></em></code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>filename</code></em></code>]
+ [<code class="option">-k <em class="replaceable"><code>filename</code></em></code>]
+ [<code class="option">-m</code>]
+ [<code class="option">-p <em class="replaceable"><code>port#</code></em></code>]
+ [<code class="option">-q <em class="replaceable"><code>name</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>type</code></em></code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-x <em class="replaceable"><code>addr</code></em></code>]
+ [<code class="option">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]name:key</code></em></code>]
+ [<code class="option">-4</code>]
+ [<code class="option">-6</code>]
+ [name]
+ [type]
+ [class]
+ [queryopt...]
+ </p></div>
+
+ <div class="cmdsynopsis"><p>
+ <code class="command">dig</code>
+ [<code class="option">-h</code>]
+ </p></div>
+
+ <div class="cmdsynopsis"><p>
+ <code class="command">dig</code>
+ [global-queryopt...]
+ [query...]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dig</strong></span>
(domain information groper) is a flexible tool
for interrogating DNS name servers. It performs DNS lookups and
displays the answers that are returned from the name server(s) that
- were queried. Most DNS administrators use <span><strong class="command">dig</strong></span> to
+ were queried. Most DNS administrators use <span class="command"><strong>dig</strong></span> to
troubleshoot DNS problems because of its flexibility, ease of use and
clarity of output. Other lookup tools tend to have less functionality
- than <span><strong class="command">dig</strong></span>.
+ than <span class="command"><strong>dig</strong></span>.
</p>
-<p>
- Although <span><strong class="command">dig</strong></span> is normally used with
+
+ <p>
+ Although <span class="command"><strong>dig</strong></span> is normally used with
command-line
arguments, it also has a batch mode of operation for reading lookup
requests from a file. A brief summary of its command-line arguments
and options is printed when the <code class="option">-h</code> option is given.
Unlike earlier versions, the BIND 9 implementation of
- <span><strong class="command">dig</strong></span> allows multiple lookups to be issued
+ <span class="command"><strong>dig</strong></span> allows multiple lookups to be issued
from the
command line.
</p>
-<p>
+
+ <p>
Unless it is told to query a specific name server,
- <span><strong class="command">dig</strong></span> will try each of the servers listed in
+ <span class="command"><strong>dig</strong></span> will try each of the servers listed in
<code class="filename">/etc/resolv.conf</code>. If no usable server addresses
- are found, <span><strong class="command">dig</strong></span> will send the query to the local
+ are found, <span class="command"><strong>dig</strong></span> will send the query to the local
host.
</p>
-<p>
+
+ <p>
When no command line arguments or options are given,
- <span><strong class="command">dig</strong></span> will perform an NS query for "." (the root).
+ <span class="command"><strong>dig</strong></span> will perform an NS query for "." (the root).
</p>
-<p>
- It is possible to set per-user defaults for <span><strong class="command">dig</strong></span> via
+
+ <p>
+ It is possible to set per-user defaults for <span class="command"><strong>dig</strong></span> via
<code class="filename">${HOME}/.digrc</code>. This file is read and
any options in it
are applied before the command line arguments.
</p>
-<p>
+
+ <p>
The IN and CH class names overlap with the IN and CH top level
domain names. Either use the <code class="option">-t</code> and
<code class="option">-c</code> options to specify the type and class,
use the <code class="option">-q</code> the specify the domain name, or
use "IN." and "CH." when looking up these top level domains.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2617348"></a><h2>SIMPLE USAGE</h2>
-<p>
- A typical invocation of <span><strong class="command">dig</strong></span> looks like:
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.8"></a><h2>SIMPLE USAGE</h2>
+
+
+ <p>
+ A typical invocation of <span class="command"><strong>dig</strong></span> looks like:
</p>
<pre class="programlisting"> dig @server name type </pre>
<p>
where:
</p>
-<div class="variablelist"><dl>
+<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="constant">server</code></span></dt>
<dd>
-<p>
is the name or IP address of the name server to query. This
can be an IPv4 address in dotted-decimal notation or an IPv6
address in colon-delimited notation. When the supplied
<em class="parameter"><code>server</code></em> argument is a hostname,
- <span><strong class="command">dig</strong></span> resolves that name before querying
+ <span class="command"><strong>dig</strong></span> resolves that name before querying
that name server.
</p>
-<p>
If no <em class="parameter"><code>server</code></em> argument is
- provided, <span><strong class="command">dig</strong></span> consults
+ provided, <span class="command"><strong>dig</strong></span> consults
<code class="filename">/etc/resolv.conf</code>; if an
address is found there, it queries the name server at
that address. If either of the <code class="option">-4</code> or
<code class="option">-6</code> options are in use, then
only addresses for the corresponding transport
will be tried. If no usable addresses are found,
- <span><strong class="command">dig</strong></span> will send the query to the
+ <span class="command"><strong>dig</strong></span> will send the query to the
local host. The reply from the name server that
responds is displayed.
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="constant">name</code></span></dt>
-<dd><p>
+<dd>
+ <p>
is the name of the resource record that is to be looked up.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="constant">type</code></span></dt>
-<dd><p>
+<dd>
+ <p>
indicates what type of query is required —
ANY, A, MX, SIG, etc.
<em class="parameter"><code>type</code></em> can be any valid query
type. If no
<em class="parameter"><code>type</code></em> argument is supplied,
- <span><strong class="command">dig</strong></span> will perform a lookup for an
+ <span class="command"><strong>dig</strong></span> will perform a lookup for an
A record.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
<p>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2617474"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.9"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-4</span></dt>
-<dd><p>
+<dd>
+ <p>
Use IPv4 only.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-6</span></dt>
-<dd><p>
+<dd>
+ <p>
Use IPv6 only.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-b <em class="replaceable"><code>address[<span class="optional">#port</span>]</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the source IP address of the query.
The <em class="parameter"><code>address</code></em> must be a valid address on
one of the host's network interfaces, or "0.0.0.0" or "::". An
optional port may be specified by appending "#<port>"
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the query class. The
default <em class="parameter"><code>class</code></em> is IN; other classes
are HS for Hesiod records or CH for Chaosnet records.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-f <em class="replaceable"><code>file</code></em></span></dt>
-<dd><p>
- Batch mode: <span><strong class="command">dig</strong></span> reads a list of lookup
+<dd>
+ <p>
+ Batch mode: <span class="command"><strong>dig</strong></span> reads a list of lookup
requests to process from the
given <em class="parameter"><code>file</code></em>. Each line in the file
should be organized in the same way they would be
presented as queries to
- <span><strong class="command">dig</strong></span> using the command-line interface.
- </p></dd>
+ <span class="command"><strong>dig</strong></span> using the command-line interface.
+ </p>
+ </dd>
<dt><span class="term">-i</span></dt>
-<dd><p>
+<dd>
+ <p>
Do reverse IPv6 lookups using the obsolete RFC1886 IP6.INT
domain, which is no longer in use. Obsolete bit string
label queries (RFC2874) are not attempted.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-k <em class="replaceable"><code>keyfile</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sign queries using TSIG using a key read from the given file.
Key files can be generated using
- <span class="citerefentry"><span class="refentrytitle">tsig-keygen</span>(8)</span>.
- When using TSIG authentication with <span><strong class="command">dig</strong></span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">tsig-keygen</span>(8)
+ </span>.
+ When using TSIG authentication with <span class="command"><strong>dig</strong></span>,
the name server that is queried needs to know the key and
algorithm that is being used. In BIND, this is done by
- providing appropriate <span><strong class="command">key</strong></span>
- and <span><strong class="command">server</strong></span> statements in
+ providing appropriate <span class="command"><strong>key</strong></span>
+ and <span class="command"><strong>server</strong></span> statements in
<code class="filename">named.conf</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-m</span></dt>
-<dd><p>
+<dd>
+ <p>
Enable memory usage debugging.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Send the query to a non-standard port on the server,
instead of the defaut port 53. This option would be used
to test a name server that has been configured to listen
for queries on a non-standard port number.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-q <em class="replaceable"><code>name</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The domain name to query. This is useful to distinguish
the <em class="parameter"><code>name</code></em> from other arguments.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>type</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The resource record type to query. It can be any valid query type
which is
supported in BIND 9. The default query type is "A", unless the
made to the zone since the serial number in the zone's SOA
record was
<em class="parameter"><code>N</code></em>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v</span></dt>
-<dd><p>
+<dd>
+ <p>
Print the version number and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-x <em class="replaceable"><code>addr</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Simplified reverse lookups, for mapping addresses to
names. The <em class="parameter"><code>addr</code></em> is an IPv4 address
in dotted-decimal notation, or a colon-delimited IPv6
need to provide
the <em class="parameter"><code>name</code></em>, <em class="parameter"><code>class</code></em>
and <em class="parameter"><code>type</code></em>
- arguments. <span><strong class="command">dig</strong></span> automatically performs a
+ arguments. <span class="command"><strong>dig</strong></span> automatically performs a
lookup for a name like
<code class="literal">94.2.0.192.in-addr.arpa</code> and sets the
query type and class to PTR and IN respectively. IPv6
addresses are looked up using nibble format under the
IP6.ARPA domain (but see also the <code class="option">-i</code>
option).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]keyname:secret</code></em></span></dt>
<dd>
-<p>
Sign queries using TSIG with the given authentication key.
<em class="parameter"><code>keyname</code></em> is the name of the key, and
<em class="parameter"><code>secret</code></em> is the base64 encoded shared secret.
<code class="literal">hmac-sha512</code>. If <em class="parameter"><code>hmac</code></em>
is not specified, the default is <code class="literal">hmac-md5</code>.
</p>
-<p>
NOTE: You should use the <code class="option">-k</code> option and
avoid the <code class="option">-y</code> option, because
with <code class="option">-y</code> the shared secret is supplied as
a command line argument in clear text. This may be visible
in the output from
- <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
+ <span class="citerefentry">
+ <span class="refentrytitle">ps</span>(1)
+ </span>
or in a history file maintained by the user's shell.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2668916"></a><h2>QUERY OPTIONS</h2>
-<p><span><strong class="command">dig</strong></span>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.10"></a><h2>QUERY OPTIONS</h2>
+
+
+ <p><span class="command"><strong>dig</strong></span>
provides a number of query options which affect
the way in which lookups are made and the results displayed. Some of
these set or reset flag bits in the query header, some determine which
sections of the answer get printed, and others determine the timeout
and retry strategies.
</p>
-<p>
+
+ <p>
Each query option is identified by a keyword preceded by a plus sign
(<code class="literal">+</code>). Some keywords set or reset an
option. These may be preceded
The query options are:
</p>
-<div class="variablelist"><dl>
+<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="option">+[no]aaflag</code></span></dt>
-<dd><p>
+<dd>
+ <p>
A synonym for <em class="parameter"><code>+[no]aaonly</code></em>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]aaonly</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the "aa" flag in the query.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]additional</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Display [do not display] the additional section of a
reply. The default is to display it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]adflag</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set [do not set] the AD (authentic data) bit in the
query. This requests the server to return whether
all of the answer and authority sections have all
from a OPT-OUT range. AD=0 indicate that some part
of the answer was insecure or not validated. This
bit is set by default.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]all</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set or clear all display flags.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]answer</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Display [do not display] the answer section of a
reply. The default is to display it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]authority</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Display [do not display] the authority section of a
reply. The default is to display it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]badcookie</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Retry lookup with the new server cookie if a
BADCOOKIE response is received.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]besteffort</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Attempt to display the contents of messages which are
malformed. The default is to not display malformed
answers.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+bufsize=B</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the UDP message buffer size advertised using EDNS0
to <em class="parameter"><code>B</code></em> bytes. The maximum and
minimum sizes of this buffer are 65535 and 0 respectively.
Values outside this range are rounded up or down
appropriately. Values other than zero will cause a
EDNS query to be sent.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]cdflag</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set [do not set] the CD (checking disabled) bit in
the query. This requests the server to not perform
DNSSEC validation of responses.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]class</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Display [do not display] the CLASS when printing the
record.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]cmd</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggles the printing of the initial comment in the
- output identifying the version of <span><strong class="command">dig</strong></span>
+ output identifying the version of <span class="command"><strong>dig</strong></span>
and the query options that have been applied. This
comment is printed by default.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]comments</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggle the display of comment lines in the output.
The default is to print comments.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]cookie[<span class="optional">=####</span>]</code></span></dt>
<dd>
-<p>
Send a COOKIE EDNS option, with optional
value. Replaying a COOKIE from a previous response will
allow the server to identify a previous client. The
default is <code class="option">+cookie</code>.
</p>
-<p>
- <span><strong class="command">+cookie</strong></span> is also set when +trace
+ <span class="command"><strong>+cookie</strong></span> is also set when +trace
is set to better emulate the default queries from a
nameserver.
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="option">+[no]crypto</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggle the display of cryptographic fields in DNSSEC
records. The contents of these field are unnecessary
to debug most DNSSEC validation failures and removing
are replaced by the string "[omitted]" or in the
DNSKEY case the key id is displayed as the replacement,
e.g. "[ key id = value ]".
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]defname</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Deprecated, treated as a synonym for
<em class="parameter"><code>+[no]search</code></em>
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]dnssec</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Requests DNSSEC records be sent by setting the DNSSEC
OK bit (DO) in the OPT record in the additional section
of the query.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+domain=somename</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the search list to contain the single domain
<em class="parameter"><code>somename</code></em>, as if specified in
- a <span><strong class="command">domain</strong></span> directive in
+ a <span class="command"><strong>domain</strong></span> directive in
<code class="filename">/etc/resolv.conf</code>, and enable
search list processing as if the
<em class="parameter"><code>+search</code></em> option were given.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+dscp=value</code></span></dt>
-<dd><p>
+<dd>
+ <p>
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 explicitly set.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]edns[=#]</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the EDNS version to query with. Valid values
are 0 to 255. Setting the EDNS version will cause
a EDNS query to be sent. <code class="option">+noedns</code>
clears the remembered EDNS version. EDNS is set to
0 by default.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]ednsflags[=#]</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the must-be-zero EDNS flags bits (Z bits) to the
specified value. Decimal, hex and octal encodings are
accepted. Setting a named flag (e.g. DO) will silently be
ignored. By default, no Z bits are set.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]ednsnegotiation</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Enable / disable EDNS version negotiation. By default
EDNS version negotiation is enabled.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]ednsopt[=code[:value]]</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify EDNS option with code point <code class="option">code</code>
and optionally payload of <code class="option">value</code> as a
hexadecimal string. <code class="option">+noednsopt</code>
clears the EDNS options to be sent.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]expire</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Send an EDNS Expire option.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]fail</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Do not try the next server if you receive a SERVFAIL.
The default is to not try the next server which is
the reverse of normal stub resolver behavior.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]header-only</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Send a query with a DNS header without a question section.
The default is to add a question section. The query type
and query name are ignored when this is set.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]identify</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Show [or do not show] the IP address and port number
that supplied the answer when the
<em class="parameter"><code>+short</code></em> option is enabled. If
short form answers are requested, the default is not
to show the source address and port number of the
server that provided the answer.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]ignore</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Ignore truncation in UDP responses instead of retrying
with TCP. By default, TCP retries are performed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]keepopen</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Keep the TCP socket open between queries and reuse
it rather than creating a new TCP socket for each
lookup. The default is <code class="option">+nokeepopen</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]multiline</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Print records like the SOA records in a verbose
multi-line format with human-readable comments. The
default is to print each record on a single line, to
- facilitate machine parsing of the <span><strong class="command">dig</strong></span>
+ facilitate machine parsing of the <span class="command"><strong>dig</strong></span>
output.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+ndots=D</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the number of dots that have to appear in
<em class="parameter"><code>name</code></em> to <em class="parameter"><code>D</code></em>
for it to be considered absolute. The default value
or <code class="option">domain</code> directive in
<code class="filename">/etc/resolv.conf</code> if
<code class="option">+search</code> is set.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]nsid</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Include an EDNS name server ID request when sending
a query.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]nssearch</code></span></dt>
-<dd><p>
- When this option is set, <span><strong class="command">dig</strong></span>
+<dd>
+ <p>
+ When this option is set, <span class="command"><strong>dig</strong></span>
attempts to find the authoritative name servers for
the zone containing the name being looked up and
display the SOA record that each name server has for
the zone.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]onesoa</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Print only one (starting) SOA record when performing
an AXFR. The default is to print both the starting
and ending SOA records.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]opcode=value</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set [restore] the DNS message opcode to the specified
value. The default value is QUERY (0).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]qr</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Print [do not print] the query as it is sent. By
default, the query is not printed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]question</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Print [do not print] the question section of a query
when an answer is returned. The default is to print
the question section as a comment.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]rdflag</code></span></dt>
-<dd><p>
+<dd>
+ <p>
A synonym for <em class="parameter"><code>+[no]recurse</code></em>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]recurse</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggle the setting of the RD (recursion desired) bit
in the query. This bit is set by default, which means
- <span><strong class="command">dig</strong></span> normally sends recursive
+ <span class="command"><strong>dig</strong></span> normally sends recursive
queries. Recursion is automatically disabled when
the <em class="parameter"><code>+nssearch</code></em> or
<em class="parameter"><code>+trace</code></em> query options are used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+retry=T</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the number of times to retry UDP queries to
server to <em class="parameter"><code>T</code></em> instead of the
default, 2. Unlike <em class="parameter"><code>+tries</code></em>,
this does not include the initial query.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]rrcomments</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Toggle the display of per-record comments in the
output (for example, human-readable key information
about DNSKEY records). The default is not to print
record comments unless multiline mode is active.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]search</code></span></dt>
<dd>
-<p>
Use [do not use] the search list defined by the
searchlist or domain directive in
<code class="filename">resolv.conf</code> (if any). The search
list is not used by default.
</p>
-<p>
'ndots' from <code class="filename">resolv.conf</code> (default 1)
which may be overridden by <em class="parameter"><code>+ndots</code></em>
determines if the name will be treated as relative
or not and hence whether a search is eventually
performed or not.
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="option">+[no]short</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Provide a terse answer. The default is to print the
answer in a verbose form.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]showsearch</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Perform [do not perform] a search showing intermediate
results.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]sigchase</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Chase DNSSEC signature chains. Requires dig be
compiled with -DDIG_SIGCHASE.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+split=W</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Split long hex- or base64-formatted fields in resource
records into chunks of <em class="parameter"><code>W</code></em>
characters (where <em class="parameter"><code>W</code></em> is rounded
<em class="parameter"><code>+split=0</code></em> causes fields not to
be split at all. The default is 56 characters, or
44 characters when multiline mode is active.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]stats</code></span></dt>
-<dd><p>
+<dd>
+ <p>
This query option toggles the printing of statistics:
when the query was made, the size of the reply and
so on. The default behavior is to print the query
statistics.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]subnet=addr/prefix</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Send an EDNS Client Subnet option with the specified
IP address or network prefix.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]tcp</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Use [do not use] TCP when querying name servers. The
default behavior is to use UDP unless an
<code class="literal">ixfr=N</code> query is requested, in which
case the default is TCP. AXFR queries always use
TCP.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+timeout=T</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the timeout for a query to
<em class="parameter"><code>T</code></em> seconds. The default
An attempt to set <em class="parameter"><code>T</code></em> to less
than 1 will result
in a query timeout of 1 second being applied.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]topdown</code></span></dt>
-<dd><p>
+<dd>
+ <p>
When chasing DNSSEC signature chains perform a top-down
validation. Requires dig be compiled with -DDIG_SIGCHASE.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]trace</code></span></dt>
<dd>
-<p>
Toggle tracing of the delegation path from the root
name servers for the name being looked up. Tracing
is disabled by default. When tracing is enabled,
- <span><strong class="command">dig</strong></span> makes iterative queries to
+ <span class="command"><strong>dig</strong></span> makes iterative queries to
resolve the name being looked up. It will follow
referrals from the root servers, showing the answer
from each server that was used to resolve the lookup.
- </p>
-<p>
+ </p> <p>
If @server is also specified, it affects only the
initial query for the root zone name servers.
- </p>
-<p>
- <span><strong class="command">+dnssec</strong></span> is also set when +trace
+ </p> <p>
+ <span class="command"><strong>+dnssec</strong></span> is also set when +trace
is set to better emulate the default queries from a
nameserver.
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="option">+tries=T</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the number of times to try UDP queries to server
to <em class="parameter"><code>T</code></em> instead of the default,
3. If <em class="parameter"><code>T</code></em> is less than or equal
to zero, the number of tries is silently rounded up
to 1.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+trusted-key=####</code></span></dt>
<dd>
-<p>
Specifies a file containing trusted keys to be used
with <code class="option">+sigchase</code>. Each DNSKEY record
must be on its own line.
- </p>
-<p>
- If not specified, <span><strong class="command">dig</strong></span> will look
+ </p> <p>
+ If not specified, <span class="command"><strong>dig</strong></span> will look
for <code class="filename">/etc/trusted-key.key</code> then
<code class="filename">trusted-key.key</code> in the current
directory.
- </p>
-<p>
+ </p> <p>
Requires dig be compiled with -DDIG_SIGCHASE.
</p>
-</dd>
+ </dd>
<dt><span class="term"><code class="option">+[no]ttlid</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Display [do not display] the TTL when printing the
record.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]ttlunits</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Display [do not display] the TTL in friendly human-readable
time units of "s", "m", "h", "d", and "w", representing
seconds, minutes, hours, days and weeks. Implies +ttlid.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]vc</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Use [do not use] TCP when querying name servers. This
alternate syntax to <em class="parameter"><code>+[no]tcp</code></em>
is provided for backwards compatibility. The "vc"
stands for "virtual circuit".
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="option">+[no]zflag</code></span></dt>
-<dd><p>
+<dd>
+ <p>
Set [do not set] the last unassigned DNS header flag in a
DNS query. This flag is off by default.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
<p>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2670341"></a><h2>MULTIPLE QUERIES</h2>
-<p>
- The BIND 9 implementation of <span><strong class="command">dig </strong></span>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.11"></a><h2>MULTIPLE QUERIES</h2>
+
+
+ <p>
+ The BIND 9 implementation of <span class="command"><strong>dig </strong></span>
supports
specifying multiple queries on the command line (in addition to
supporting the <code class="option">-f</code> batch file option). Each of those
queries can be supplied with its own set of flags, options and query
options.
</p>
-<p>
+
+ <p>
In this case, each <em class="parameter"><code>query</code></em> argument
represent an
individual query in the command-line syntax described above. Each
looked up, an optional query type and class and any query options that
should be applied to that query.
</p>
-<p>
+
+ <p>
A global set of query options, which should be applied to all queries,
can also be supplied. These global query options must precede the
first tuple of name, class, type, options, flags, and query options
dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
</pre>
<p>
- shows how <span><strong class="command">dig</strong></span> could be used from the
+ shows how <span class="command"><strong>dig</strong></span> could be used from the
command line
to make three lookups: an ANY query for <code class="literal">www.isc.org</code>, a
reverse lookup of 127.0.0.1 and a query for the NS records of
A global query option of <em class="parameter"><code>+qr</code></em> is
applied, so
- that <span><strong class="command">dig</strong></span> shows the initial query it made
+ that <span class="command"><strong>dig</strong></span> shows the initial query it made
for each
lookup. The final query has a local query option of
- <em class="parameter"><code>+noqr</code></em> which means that <span><strong class="command">dig</strong></span>
+ <em class="parameter"><code>+noqr</code></em> which means that <span class="command"><strong>dig</strong></span>
will not print the initial query when it looks up the NS records for
<code class="literal">isc.org</code>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2670426"></a><h2>IDN SUPPORT</h2>
-<p>
- If <span><strong class="command">dig</strong></span> has been built with IDN (internationalized
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.12"></a><h2>IDN SUPPORT</h2>
+
+ <p>
+ If <span class="command"><strong>dig</strong></span> has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
- <span><strong class="command">dig</strong></span> appropriately converts character encoding of
+ <span class="command"><strong>dig</strong></span> appropriately converts character encoding of
domain name before sending a request to DNS server or displaying a
reply from the server.
If you'd like to turn off the IDN support for some reason, defines
the <code class="envar">IDN_DISABLE</code> environment variable.
The IDN support is disabled if the variable is set when
- <span><strong class="command">dig</strong></span> runs.
+ <span class="command"><strong>dig</strong></span> runs.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2673937"></a><h2>FILES</h2>
-<p><code class="filename">/etc/resolv.conf</code>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.13"></a><h2>FILES</h2>
+
+ <p><code class="filename">/etc/resolv.conf</code>
</p>
-<p><code class="filename">${HOME}/.digrc</code>
+
<p><code class="filename">${HOME}/.digrc</code>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2673958"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">host</span>(1)</span>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.14"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">host</span>(1)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
<em class="citetitle">RFC1035</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2673995"></a><h2>BUGS</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.2.15"></a><h2>BUGS</h2>
+
+ <p>
There are probably too many query options.
</p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-checkds</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.delv.html" title="delv">
<link rel="next" href="man.dnssec-coverage.html" title="dnssec-coverage">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-checkds"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-checkds</span> — A DNSSEC delegation consistency checking tool.</p>
+<p>
+ <span class="application">dnssec-checkds</span>
+ — A DNSSEC delegation consistency checking tool.
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-checkds</code> [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-f <em class="replaceable"><code>file</code></em></code>] [<code class="option">-d <em class="replaceable"><code>dig path</code></em></code>] [<code class="option">-D <em class="replaceable"><code>dsfromkey path</code></em></code>] {zone}</p></div>
-<div class="cmdsynopsis"><p><code class="command">dnssec-dsfromkey</code> [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-f <em class="replaceable"><code>file</code></em></code>] [<code class="option">-d <em class="replaceable"><code>dig path</code></em></code>] [<code class="option">-D <em class="replaceable"><code>dsfromkey path</code></em></code>] {zone}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620605"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-checkds</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-checkds</code>
+ [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>file</code></em></code>]
+ [<code class="option">-d <em class="replaceable"><code>dig path</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>dsfromkey path</code></em></code>]
+ {zone}
+ </p></div>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-dsfromkey</code>
+ [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>file</code></em></code>]
+ [<code class="option">-d <em class="replaceable"><code>dig path</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>dsfromkey path</code></em></code>]
+ {zone}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.5.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-checkds</strong></span>
verifies the correctness of Delegation Signer (DS) or DNSSEC
Lookaside Validation (DLV) resource records for keys in a specified
zone.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620619"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.5.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-f <em class="replaceable"><code>file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
If a <code class="option">file</code> is specified, then the zone is
read from that file to find the DNSKEY records. If not,
then the DNSKEY records for the zone are looked up in the DNS.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Check for a DLV record in the specified lookaside domain,
instead of checking for a DS record in the zone's parent.
For example, to check for DLV records for "example.com"
in ISC's DLV zone, use:
- <span><strong class="command">dnssec-checkds -l dlv.isc.org example.com</strong></span>
- </p></dd>
+ <span class="command"><strong>dnssec-checkds -l dlv.isc.org example.com</strong></span>
+ </p>
+ </dd>
<dt><span class="term">-d <em class="replaceable"><code>dig path</code></em></span></dt>
-<dd><p>
- Specifies a path to a <span><strong class="command">dig</strong></span> binary. Used
+<dd>
+ <p>
+ Specifies a path to a <span class="command"><strong>dig</strong></span> binary. Used
for testing.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D <em class="replaceable"><code>dsfromkey path</code></em></span></dt>
-<dd><p>
- Specifies a path to a <span><strong class="command">dnssec-dsfromkey</strong></span> binary.
+<dd>
+ <p>
+ Specifies a path to a <span class="command"><strong>dnssec-dsfromkey</strong></span> binary.
Used for testing.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620722"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-dsfromkey</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.5.9"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-dsfromkey</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>,
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620756"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-coverage</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-checkds.html" title="dnssec-checkds">
<link rel="next" href="man.dnssec-dsfromkey.html" title="dnssec-dsfromkey">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-coverage"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-coverage</span> — checks future DNSKEY coverage for a zone</p>
+<p>
+ <span class="application">dnssec-coverage</span>
+ — checks future DNSKEY coverage for a zone
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-coverage</code> [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-l <em class="replaceable"><code>length</code></em></code>] [<code class="option">-f <em class="replaceable"><code>file</code></em></code>] [<code class="option">-d <em class="replaceable"><code>DNSKEY TTL</code></em></code>] [<code class="option">-m <em class="replaceable"><code>max TTL</code></em></code>] [<code class="option">-r <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-c <em class="replaceable"><code>compilezone path</code></em></code>] [<code class="option">-k</code>] [<code class="option">-z</code>] [zone]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620899"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-coverage</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-coverage</code>
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-l <em class="replaceable"><code>length</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>file</code></em></code>]
+ [<code class="option">-d <em class="replaceable"><code>DNSKEY TTL</code></em></code>]
+ [<code class="option">-m <em class="replaceable"><code>max TTL</code></em></code>]
+ [<code class="option">-r <em class="replaceable"><code>interval</code></em></code>]
+ [<code class="option">-c <em class="replaceable"><code>compilezone path</code></em></code>]
+ [<code class="option">-k</code>]
+ [<code class="option">-z</code>]
+ [zone]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.6.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-coverage</strong></span>
verifies that the DNSSEC keys for a given zone or a set of zones
have timing metadata set properly to ensure no future lapses in DNSSEC
coverage.
</p>
-<p>
If <code class="option">zone</code> is specified, then keys found in
the key repository matching that zone are scanned, and an ordered
list is generated of the events scheduled for that key (i.e.,
key is rolled, and cached data signed by the prior key has not had
time to expire from resolver caches.
</p>
-<p>
If <code class="option">zone</code> is not specified, then all keys in the
key repository will be scanned, and all zones for which there are
keys will be analyzed. (Note: This method of reporting is only
accurate if all the zones that have keys in a given repository
share the same TTL parameters.)
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620925"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.6.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the directory in which keys can be found. Defaults to the
current working directory.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-f <em class="replaceable"><code>file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
If a <code class="option">file</code> is specified, then the zone is
read from that file; the largest TTL and the DNSKEY TTL are
determined directly from the zone data, and the
<code class="option">-m</code> and <code class="option">-d</code> options do
not need to be specified on the command line.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-l <em class="replaceable"><code>duration</code></em></span></dt>
<dd>
-<p>
The length of time to check for DNSSEC coverage. Key events
scheduled further into the future than <code class="option">duration</code>
will be ignored, and assumed to be correct.
</p>
-<p>
The value of <code class="option">duration</code> can be set in seconds,
or in larger units of time by adding a suffix: 'mi' for minutes,
'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months,
'y' for years.
</p>
-</dd>
+ </dd>
<dt><span class="term">-m <em class="replaceable"><code>maximum TTL</code></em></span></dt>
<dd>
-<p>
Sets the value to be used as the maximum TTL for the zone or
zones being analyzed when determining whether there is a
possibility of validation failure. When a zone-signing key is
before that key can be purged from the DNSKEY RRset. If that
condition does not apply, a warning will be generated.
</p>
-<p>
The length of the TTL can be set in seconds, or in larger units
of time by adding a suffix: 'mi' for minutes, 'h' for hours,
'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.
</p>
-<p>
This option is mandatory unless the <code class="option">-f</code> has
been used to specify a zone file. (If <code class="option">-f</code> has
been specified, this option may still be used; it will override
the value found in the file.)
</p>
-</dd>
+ </dd>
<dt><span class="term">-d <em class="replaceable"><code>DNSKEY TTL</code></em></span></dt>
<dd>
-<p>
Sets the value to be used as the DNSKEY TTL for the zone or
zones being analyzed when determining whether there is a
possibility of validation failure. When a key is rolled (that
signatures. If that condition does not apply, a warning
will be generated.
</p>
-<p>
The length of the TTL can be set in seconds, or in larger units
of time by adding a suffix: 'mi' for minutes, 'h' for hours,
'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.
</p>
-<p>
This option is mandatory unless the <code class="option">-f</code> has
been used to specify a zone file, or a default key TTL was
set with the <code class="option">-L</code> to
- <span><strong class="command">dnssec-keygen</strong></span>. (If either of those is true,
+ <span class="command"><strong>dnssec-keygen</strong></span>. (If either of those is true,
this option may still be used; it will override the value found
in the zone or key file.)
</p>
-</dd>
+ </dd>
<dt><span class="term">-r <em class="replaceable"><code>resign interval</code></em></span></dt>
<dd>
-<p>
Sets the value to be used as the resign interval for the zone
or zones being analyzed when determining whether there is a
possibility of validation failure. This value defaults to
22.5 days, which is also the default in
- <span><strong class="command">named</strong></span>. However, if it has been changed
+ <span class="command"><strong>named</strong></span>. However, if it has been changed
by the <code class="option">sig-validity-interval</code> option in
<code class="filename">named.conf</code>, then it should also be
changed here.
</p>
-<p>
The length of the interval can be set in seconds, or in larger
units of time by adding a suffix: 'mi' for minutes, 'h' for hours,
'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.
</p>
-</dd>
+ </dd>
<dt><span class="term">-k</span></dt>
-<dd><p>
+<dd>
+ <p>
Only check KSK coverage; ignore ZSK events. Cannot be
used with <code class="option">-z</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-z</span></dt>
-<dd><p>
+<dd>
+ <p>
Only check ZSK coverage; ignore KSK events. Cannot be
used with <code class="option">-k</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>compilezone path</code></em></span></dt>
-<dd><p>
- Specifies a path to a <span><strong class="command">named-compilezone</strong></span> binary.
+<dd>
+ <p>
+ Specifies a path to a <span class="command"><strong>named-compilezone</strong></span> binary.
Used for testing.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2621508"></a><h2>SEE ALSO</h2>
-<p>
- <span class="citerefentry"><span class="refentrytitle">dnssec-checkds</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-dsfromkey</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.6.9"></a><h2>SEE ALSO</h2>
+
+ <p>
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-checkds</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-dsfromkey</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2621552"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-dsfromkey</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-coverage.html" title="dnssec-coverage">
<link rel="next" href="man.dnssec-importkey.html" title="dnssec-importkey">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-dsfromkey"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-dsfromkey</span> — DNSSEC DS RR generation tool</p>
+<p>
+ <span class="application">dnssec-dsfromkey</span>
+ — DNSSEC DS RR generation tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-dsfromkey</code> [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-1</code>] [<code class="option">-2</code>] [<code class="option">-a <em class="replaceable"><code>alg</code></em></code>] [<code class="option">-C</code>] [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-T <em class="replaceable"><code>TTL</code></em></code>] {keyfile}</p></div>
-<div class="cmdsynopsis"><p><code class="command">dnssec-dsfromkey</code> {-s} [<code class="option">-1</code>] [<code class="option">-2</code>] [<code class="option">-a <em class="replaceable"><code>alg</code></em></code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-s</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-T <em class="replaceable"><code>TTL</code></em></code>] [<code class="option">-f <em class="replaceable"><code>file</code></em></code>] [<code class="option">-A</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] {dnsname}</p></div>
-<div class="cmdsynopsis"><p><code class="command">dnssec-dsfromkey</code> [<code class="option">-h</code>] [<code class="option">-V</code>]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2622525"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-dsfromkey</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-dsfromkey</code>
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-1</code>]
+ [<code class="option">-2</code>]
+ [<code class="option">-a <em class="replaceable"><code>alg</code></em></code>]
+ [<code class="option">-C</code>]
+ [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>]
+ [<code class="option">-T <em class="replaceable"><code>TTL</code></em></code>]
+ {keyfile}
+ </p></div>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-dsfromkey</code>
+ {-s}
+ [<code class="option">-1</code>]
+ [<code class="option">-2</code>]
+ [<code class="option">-a <em class="replaceable"><code>alg</code></em></code>]
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>]
+ [<code class="option">-s</code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-T <em class="replaceable"><code>TTL</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>file</code></em></code>]
+ [<code class="option">-A</code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ {dnsname}
+ </p></div>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-dsfromkey</code>
+ [<code class="option">-h</code>]
+ [<code class="option">-V</code>]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.7.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-dsfromkey</strong></span>
outputs the Delegation Signer (DS) resource record (RR), as defined in
RFC 3658 and RFC 4509, for the given key(s).
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2622539"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.7.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-1</span></dt>
-<dd><p>
+<dd>
+ <p>
Use SHA-1 as the digest algorithm (the default is to use
both SHA-1 and SHA-256).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-2</span></dt>
-<dd><p>
+<dd>
+ <p>
Use SHA-256 as the digest algorithm.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Select the digest algorithm. The value of
<code class="option">algorithm</code> must be one of SHA-1 (SHA1),
SHA-256 (SHA256), GOST or SHA-384 (SHA384).
These values are case insensitive.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-C</span></dt>
-<dd><p>
+<dd>
+ <p>
Generate CDS records rather than DS records. This is mutually
exclusive with generating lookaside records.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-T <em class="replaceable"><code>TTL</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the TTL of the DS records.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Look for key files (or, in keyset mode,
<code class="filename">keyset-</code> files) in
<code class="option">directory</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-f <em class="replaceable"><code>file</code></em></span></dt>
<dd>
-<p>
Zone file mode: in place of the keyfile name, the argument is
the DNS domain name of a zone master file, which can be read
from <code class="option">file</code>. If the zone name is the same as
<code class="option">file</code>, then it may be omitted.
</p>
-<p>
If <code class="option">file</code> is set to <code class="literal">"-"</code>, then
the zone data is read from the standard input. This makes it
- possible to use the output of the <span><strong class="command">dig</strong></span>
+ possible to use the output of the <span class="command"><strong>dig</strong></span>
command as input, as in:
</p>
-<p>
<strong class="userinput"><code>dig dnskey example.com | dnssec-dsfromkey -f - example.com</code></strong>
</p>
-</dd>
+ </dd>
<dt><span class="term">-A</span></dt>
-<dd><p>
+<dd>
+ <p>
Include ZSKs when generating DS records. Without this option,
only keys which have the KSK flag set will be converted to DS
records and printed. Useful only in zone file mode.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Generate a DLV set instead of a DS set. The specified
<code class="option">domain</code> is appended to the name for each
record in the set.
The DNSSEC Lookaside Validation (DLV) RR is described
in RFC 4431. This is mutually exclusive with generating
CDS records.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s</span></dt>
-<dd><p>
+<dd>
+ <p>
Keyset mode: in place of the keyfile name, the argument is
the DNS domain name of a keyset file.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the DNS class (default is IN). Useful only
in keyset or zone file mode.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints usage information.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2622814"></a><h2>EXAMPLE</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.7.9"></a><h2>EXAMPLE</h2>
+
+ <p>
To build the SHA-256 DS RR from the
<strong class="userinput"><code>Kexample.com.+003+26160</code></strong>
keyfile name, the following command would be issued:
</p>
-<p><strong class="userinput"><code>dnssec-dsfromkey -2 Kexample.com.+003+26160</code></strong>
+
<p><strong class="userinput"><code>dnssec-dsfromkey -2 Kexample.com.+003+26160</code></strong>
</p>
-<p>
The command would print something like:
</p>
-<p><strong class="userinput"><code>example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94</code></strong>
+
<p><strong class="userinput"><code>example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94</code></strong>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2622851"></a><h2>FILES</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.7.10"></a><h2>FILES</h2>
+
+ <p>
The keyfile can be designed by the key identification
<code class="filename">Knnnn.+aaa+iiiii</code> or the full file name
<code class="filename">Knnnn.+aaa+iiiii.key</code> as generated by
<span class="refentrytitle">dnssec-keygen</span>(8).
</p>
-<p>
The keyset file name is built from the <code class="option">directory</code>,
the string <code class="filename">keyset-</code> and the
<code class="option">dnsname</code>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623916"></a><h2>CAVEAT</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.7.11"></a><h2>CAVEAT</h2>
+
+ <p>
A keyfile error can give a "file not found" even if the file exists.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623926"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.7.12"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 3658</em>,
<em class="citetitle">RFC 4431</em>.
<em class="citetitle">RFC 4509</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2624238"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-importkey</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-dsfromkey.html" title="dnssec-dsfromkey">
<link rel="next" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-importkey"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-importkey</span> — Import DNSKEY records from external systems so they can be managed.</p>
+<p>
+ <span class="application">dnssec-importkey</span>
+ — Import DNSKEY records from external systems so they can be managed.
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-importkey</code> [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-h</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] {<code class="option">keyfile</code>}</p></div>
-<div class="cmdsynopsis"><p><code class="command">dnssec-importkey</code> {<code class="option">-f <em class="replaceable"><code>filename</code></em></code>} [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-h</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">dnsname</code>]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623081"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-importkey</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-importkey</code>
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-V</code>]
+ {<code class="option">keyfile</code>}
+ </p></div>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-importkey</code>
+ {<code class="option">-f <em class="replaceable"><code>filename</code></em></code>}
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-V</code>]
+ [<code class="option">dnsname</code>]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.8.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-importkey</strong></span>
reads a public DNSKEY record and generates a pair of
.key/.private files. The DNSKEY record may be read from an
existing .key file, in which case a corresponding .private file
from the standard input, in which case both .key and .private
files will be generated.
</p>
-<p>
The newly-created .private file does <span class="emphasis"><em>not</em></span>
contain private key data, and cannot be used for signing.
However, having a .private file makes it possible to set
public key can be added to and removed from the DNSKEY RRset
on schedule even if the true private key is stored offline.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623109"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.8.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-f <em class="replaceable"><code>filename</code></em></span></dt>
<dd>
-<p>
Zone file mode: instead of a public keyfile name, the argument
is the DNS domain name of a zone master file, which can be read
from <code class="option">file</code>. If the domain name is the same as
<code class="option">file</code>, then it may be omitted.
</p>
-<p>
If <code class="option">file</code> is set to <code class="literal">"-"</code>, then
the zone data is read from the standard input.
</p>
-</dd>
+ </dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the directory in which the key files are to reside.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the default TTL to use for this key when it is converted
into a DNSKEY RR. If the key is imported into a zone,
this is the TTL that will be used for it, unless there was
already a DNSKEY RRset in place, in which case the existing TTL
would take precedence. Setting the default TTL to
<code class="literal">0</code> or <code class="literal">none</code> removes it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Emit usage message and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623451"></a><h2>TIMING OPTIONS</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.8.9"></a><h2>TIMING OPTIONS</h2>
+
+ <p>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
an offset from the present time. For convenience, if such an offset
is computed in seconds. To explicitly prevent a date from being
set, use 'none' or 'never'.
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which a key is to be published to the zone.
After that date, the key will be included in the zone but will
not be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be deleted. After that
date, the key will no longer be included in the zone. (It
may remain in the key repository, however.)
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623498"></a><h2>FILES</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.8.10"></a><h2>FILES</h2>
+
+ <p>
A keyfile can be designed by the key identification
<code class="filename">Knnnn.+aaa+iiiii</code> or the full file name
<code class="filename">Knnnn.+aaa+iiiii.key</code> as generated by
<span class="refentrytitle">dnssec-keygen</span>(8).
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623524"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.8.11"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 5011</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2623557"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keyfromlabel</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-importkey.html" title="dnssec-importkey">
<link rel="next" href="man.dnssec-keygen.html" title="dnssec-keygen">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-keyfromlabel"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-keyfromlabel</span> — DNSSEC key generation tool</p>
+<p>
+ <span class="application">dnssec-keyfromlabel</span>
+ — DNSSEC key generation tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-keyfromlabel</code> {-l <em class="replaceable"><code>label</code></em>} [<code class="option">-3</code>] [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-f <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-G</code>] [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-k</code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-n <em class="replaceable"><code>nametype</code></em></code>] [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-p <em class="replaceable"><code>protocol</code></em></code>] [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-S <em class="replaceable"><code>key</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">-y</code>] {name}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2624571"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-keyfromlabel</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-keyfromlabel</code>
+ {-l <em class="replaceable"><code>label</code></em>}
+ [<code class="option">-3</code>]
+ [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>]
+ [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>flag</code></em></code>]
+ [<code class="option">-G</code>]
+ [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>]
+ [<code class="option">-k</code>]
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-n <em class="replaceable"><code>nametype</code></em></code>]
+ [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-p <em class="replaceable"><code>protocol</code></em></code>]
+ [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-S <em class="replaceable"><code>key</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>type</code></em></code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-y</code>]
+ {name}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.9.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-keyfromlabel</strong></span>
generates a key pair of files that referencing a key object stored
in a cryptographic hardware service module (HSM). The private key
file can be used for DNSSEC signing of zone data as if it were a
- conventional signing key created by <span><strong class="command">dnssec-keygen</strong></span>,
+ conventional signing key created by <span class="command"><strong>dnssec-keygen</strong></span>,
but the key material is stored within the HSM, and the actual signing
takes place there.
</p>
-<p>
The <code class="option">name</code> of the key is specified on the command
line. This must match the name of the zone for which the key is
being generated.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2624802"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.9.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
<dd>
-<p>
Selects the cryptographic algorithm. The value of
<code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
ECDSAP256SHA256 or ECDSAP384SHA384.
These values are case insensitive.
</p>
-<p>
If no algorithm is specified, then RSASHA1 will be used by
default, unless the <code class="option">-3</code> option is specified,
in which case NSEC3RSASHA1 will be used instead. (If
<code class="option">-3</code> is used and an algorithm is specified,
that algorithm will be checked for compatibility with NSEC3.)
</p>
-<p>
Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
algorithm, and DSA is recommended.
</p>
-<p>
Note 2: DH automatically sets the -k flag.
</p>
-</dd>
+ </dd>
<dt><span class="term">-3</span></dt>
-<dd><p>
+<dd>
+ <p>
Use an NSEC3-capable algorithm to generate a DNSSEC key.
If this option is used and no algorithm is explicitly
set on the command line, NSEC3RSASHA1 will be used by
default.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd>
-<p>
Specifies the cryptographic hardware to use.
</p>
-<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
-</dd>
+ </dd>
<dt><span class="term">-l <em class="replaceable"><code>label</code></em></span></dt>
<dd>
-<p>
Specifies the label for a key pair in the crypto hardware.
</p>
-<p>
When <acronym class="acronym">BIND</acronym> 9 is built with OpenSSL-based
PKCS#11 support, the label is an arbitrary string that
identifies a particular key. It may be preceded by an
optional OpenSSL engine name, followed by a colon, as in
"pkcs11:<em class="replaceable"><code>keylabel</code></em>".
</p>
-<p>
When <acronym class="acronym">BIND</acronym> 9 is built with native PKCS#11
support, the label is a PKCS#11 URI string in the format
"pkcs11:<code class="option">keyword</code>=<em class="replaceable"><code>value</code></em>[<span class="optional">;<code class="option">keyword</code>=<em class="replaceable"><code>value</code></em>;...</span>]"
which the HSM's PIN code can be obtained. The label will be
stored in the on-disk "private" file.
</p>
-<p>
If the label contains a
<code class="option">pin-source</code> field, tools using the generated
key files will be able to use the HSM for signing and other
may reduce the security advantage of using an HSM; be sure
this is what you want to do before making use of this feature.
</p>
-</dd>
+ </dd>
<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the owner type of the key. The value of
<code class="option">nametype</code> must either be ZONE (for a DNSSEC
zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
a host (KEY)),
USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
These values are case insensitive.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-C</span></dt>
-<dd><p>
+<dd>
+ <p>
Compatibility mode: generates an old-style key, without
- any metadata. By default, <span><strong class="command">dnssec-keyfromlabel</strong></span>
+ any metadata. By default, <span class="command"><strong>dnssec-keyfromlabel</strong></span>
will include the key's creation date in the metadata stored
with the private key, and other dates may be set there as well
(publication date, activation date, etc). Keys that include
this data may be incompatible with older versions of BIND; the
<code class="option">-C</code> option suppresses them.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Indicates that the DNS record containing the key should have
the specified class. If not specified, class IN is used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-f <em class="replaceable"><code>flag</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the specified flag in the flag field of the KEY/DNSKEY record.
The only recognized flags are KSK (Key Signing Key) and REVOKE.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-G</span></dt>
-<dd><p>
+<dd>
+ <p>
Generate a key, but do not publish it or sign with it. This
option is incompatible with -P and -A.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints a short summary of the options and arguments to
- <span><strong class="command">dnssec-keyfromlabel</strong></span>.
- </p></dd>
+ <span class="command"><strong>dnssec-keyfromlabel</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the directory in which the key files are to be written.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-k</span></dt>
-<dd><p>
+<dd>
+ <p>
Generate KEY records rather than DNSKEY records.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the default TTL to use for this key when it is converted
into a DNSKEY RR. If the key is imported into a zone,
this is the TTL that will be used for it, unless there was
already a DNSKEY RRset in place, in which case the existing TTL
would take precedence. Setting the default TTL to
<code class="literal">0</code> or <code class="literal">none</code> removes it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>protocol</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the protocol value for the key. The protocol
is a number between 0 and 255. The default is 3 (DNSSEC).
Other possible values for this argument are listed in
RFC 2535 and its successors.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-S <em class="replaceable"><code>key</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Generate a key as an explicit successor to an existing key.
The name, algorithm, size, and type of the key will be set
to match the predecessor. The activation date of the new
one. The publication date will be set to the activation
date minus the prepublication interval, which defaults to
30 days.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>type</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Indicates the use of the key. <code class="option">type</code> must be
one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default
is AUTHCONF. AUTH refers to the ability to authenticate
data, and CONF the ability to encrypt data.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-y</span></dt>
-<dd><p>
+<dd>
+ <p>
Allows DNSSEC key files to be generated even if the key ID
would collide with that of an existing key, in the event of
either key being revoked. (This is only safe to use if you
are sure you won't be using RFC 5011 trust anchor maintenance
with either of the keys involved.)
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2675856"></a><h2>TIMING OPTIONS</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.9.9"></a><h2>TIMING OPTIONS</h2>
+
+
+ <p>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
an offset from the present time. For convenience, if such an offset
is computed in seconds. To explicitly prevent a date from being
set, use 'none' or 'never'.
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which a key is to be published to the zone.
After that date, the key will be included in the zone but will
not be used to sign it. If not set, and if the -G option has
not been used, the default is "now".
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-A <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be activated. After that
date, the key will be included in the zone and used to sign
it. If not set, and if the -G option has not been used, the
default is "now".
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-R <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be revoked. After that
date, the key will be flagged as revoked. It will be included
in the zone and will be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-I <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be retired. After that
date, the key will still be included in the zone, but it
will not be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be deleted. After that
date, the key will no longer be included in the zone. (It
may remain in the key repository, however.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
<dd>
-<p>
Sets the prepublication interval for a key. If set, then
the publication and activation dates must be separated by at least
this much time. If the activation date is specified but the
the publication date is specified but activation date isn't,
then activation will be set to this much time after publication.
</p>
-<p>
If the key is being created as an explicit successor to another
key, then the default prepublication interval is 30 days;
otherwise it is zero.
</p>
-<p>
As with date offsets, if the argument is followed by one of
the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
interval is measured in years, months, weeks, days, hours,
or minutes, respectively. Without a suffix, the interval is
measured in seconds.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2676182"></a><h2>GENERATED KEY FILES</h2>
-<p>
- When <span><strong class="command">dnssec-keyfromlabel</strong></span> completes
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.9.10"></a><h2>GENERATED KEY FILES</h2>
+
+ <p>
+ When <span class="command"><strong>dnssec-keyfromlabel</strong></span> completes
successfully,
it prints a string of the form <code class="filename">Knnnn.+aaa+iiiii</code>
to the standard output. This is an identification string for
the key files it has generated.
</p>
-<div class="itemizedlist"><ul type="disc">
-<li><p><code class="filename">nnnn</code> is the key name.
- </p></li>
-<li><p><code class="filename">aaa</code> is the numeric representation
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p><code class="filename">nnnn</code> is the key name.
+ </p>
+ </li>
+<li class="listitem">
+ <p><code class="filename">aaa</code> is the numeric representation
of the algorithm.
- </p></li>
-<li><p><code class="filename">iiiii</code> is the key identifier (or
+ </p>
+ </li>
+<li class="listitem">
+ <p><code class="filename">iiiii</code> is the key identifier (or
footprint).
- </p></li>
+ </p>
+ </li>
</ul></div>
-<p><span><strong class="command">dnssec-keyfromlabel</strong></span>
+ <p><span class="command"><strong>dnssec-keyfromlabel</strong></span>
creates two files, with names based
on the printed string. <code class="filename">Knnnn.+aaa+iiiii.key</code>
contains the public key, and
<code class="filename">Knnnn.+aaa+iiiii.private</code> contains the
private key.
</p>
-<p>
The <code class="filename">.key</code> file contains a DNS KEY record
that
can be inserted into a zone file (directly or with a $INCLUDE
statement).
</p>
-<p>
The <code class="filename">.private</code> file contains
algorithm-specific
fields. For obvious security reasons, this file does not have
general read permission.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2676344"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.9.11"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 4034</em>,
<em class="citetitle">The PKCS#11 URI Scheme (draft-pechanec-pkcs11uri-13)</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2676381"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keygen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel">
<link rel="next" href="man.dnssec-revoke.html" title="dnssec-revoke">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-keygen"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-keygen</span> — DNSSEC key generation tool</p>
+<p>
+ <span class="application">dnssec-keygen</span>
+ — DNSSEC key generation tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-keygen</code> [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-b <em class="replaceable"><code>keysize</code></em></code>] [<code class="option">-n <em class="replaceable"><code>nametype</code></em></code>] [<code class="option">-3</code>] [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-C</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-f <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-G</code>] [<code class="option">-g <em class="replaceable"><code>generator</code></em></code>] [<code class="option">-h</code>] [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-k</code>] [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-p <em class="replaceable"><code>protocol</code></em></code>] [<code class="option">-q</code>] [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-S <em class="replaceable"><code>key</code></em></code>] [<code class="option">-s <em class="replaceable"><code>strength</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">-z</code>] {name}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2628421"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-keygen</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-keygen</code>
+ [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>]
+ [<code class="option">-b <em class="replaceable"><code>keysize</code></em></code>]
+ [<code class="option">-n <em class="replaceable"><code>nametype</code></em></code>]
+ [<code class="option">-3</code>]
+ [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-C</code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>flag</code></em></code>]
+ [<code class="option">-G</code>]
+ [<code class="option">-g <em class="replaceable"><code>generator</code></em></code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>]
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-k</code>]
+ [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-p <em class="replaceable"><code>protocol</code></em></code>]
+ [<code class="option">-q</code>]
+ [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>]
+ [<code class="option">-S <em class="replaceable"><code>key</code></em></code>]
+ [<code class="option">-s <em class="replaceable"><code>strength</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>type</code></em></code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-z</code>]
+ {name}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.10.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-keygen</strong></span>
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
and RFC 4034. It can also generate keys for use with
TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY
(Transaction Key) as defined in RFC 2930.
</p>
-<p>
The <code class="option">name</code> of the key is specified on the command
line. For DNSSEC keys, this must match the name of the zone for
which the key is being generated.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2628441"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.10.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
<dd>
-<p>
Selects the cryptographic algorithm. For DNSSEC keys, the value
of <code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
HMAC-SHA256, HMAC-SHA384, or HMAC-SHA512. These values are
case insensitive.
</p>
-<p>
If no algorithm is specified, then RSASHA1 will be used by
default, unless the <code class="option">-3</code> option is specified,
in which case NSEC3RSASHA1 will be used instead. (If
<code class="option">-3</code> is used and an algorithm is specified,
that algorithm will be checked for compatibility with NSEC3.)
</p>
-<p>
Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
algorithm, and DSA is recommended. For TSIG, HMAC-MD5 is
mandatory.
</p>
-<p>
Note 2: DH, HMAC-MD5, and HMAC-SHA1 through HMAC-SHA512
automatically set the -T KEY option.
</p>
-</dd>
+ </dd>
<dt><span class="term">-b <em class="replaceable"><code>keysize</code></em></span></dt>
<dd>
-<p>
Specifies the number of bits in the key. The choice of key
size depends on the algorithm used. RSA keys must be
between 512 and 2048 bits. Diffie Hellman keys must be between
between 1 and 512 bits. Elliptic curve algorithms don't need
this parameter.
</p>
-<p>
The key size does not need to be specified if using a default
algorithm. The default key size is 1024 bits for zone signing
keys (ZSKs) and 2048 bits for key signing keys (KSKs,
then there is no default key size, and the <code class="option">-b</code>
must be used.
</p>
-</dd>
+ </dd>
<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the owner type of the key. The value of
<code class="option">nametype</code> must either be ZONE (for a DNSSEC
zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
These values are case insensitive. Defaults to ZONE for DNSKEY
generation.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-3</span></dt>
-<dd><p>
+<dd>
+ <p>
Use an NSEC3-capable algorithm to generate a DNSSEC key.
If this option is used and no algorithm is explicitly
set on the command line, NSEC3RSASHA1 will be used by
default. Note that RSASHA256, RSASHA512, ECCGOST,
ECDSAP256SHA256 and ECDSAP384SHA384 algorithms
are NSEC3-capable.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-C</span></dt>
-<dd><p>
+<dd>
+ <p>
Compatibility mode: generates an old-style key, without
- any metadata. By default, <span><strong class="command">dnssec-keygen</strong></span>
+ any metadata. By default, <span class="command"><strong>dnssec-keygen</strong></span>
will include the key's creation date in the metadata stored
with the private key, and other dates may be set there as well
(publication date, activation date, etc). Keys that include
this data may be incompatible with older versions of BIND; the
<code class="option">-C</code> option suppresses them.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Indicates that the DNS record containing the key should have
the specified class. If not specified, class IN is used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd>
-<p>
Specifies the cryptographic hardware to use, when applicable.
</p>
-<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
-</dd>
+ </dd>
<dt><span class="term">-f <em class="replaceable"><code>flag</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the specified flag in the flag field of the KEY/DNSKEY record.
The only recognized flags are KSK (Key Signing Key) and REVOKE.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-G</span></dt>
-<dd><p>
+<dd>
+ <p>
Generate a key, but do not publish it or sign with it. This
option is incompatible with -P and -A.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-g <em class="replaceable"><code>generator</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
If generating a Diffie Hellman key, use this generator.
Allowed values are 2 and 5. If no generator
is specified, a known prime from RFC 2539 will be used
if possible; otherwise the default is 2.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints a short summary of the options and arguments to
- <span><strong class="command">dnssec-keygen</strong></span>.
- </p></dd>
+ <span class="command"><strong>dnssec-keygen</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the directory in which the key files are to be written.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-k</span></dt>
-<dd><p>
+<dd>
+ <p>
Deprecated in favor of -T KEY.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the default TTL to use for this key when it is converted
into a DNSKEY RR. If the key is imported into a zone,
this is the TTL that will be used for it, unless there was
is no existing DNSKEY RRset, the TTL will default to the
SOA TTL. Setting the default TTL to <code class="literal">0</code>
or <code class="literal">none</code> is the same as leaving it unset.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>protocol</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the protocol value for the generated key. The protocol
is a number between 0 and 255. The default is 3 (DNSSEC).
Other possible values for this argument are listed in
RFC 2535 and its successors.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-q</span></dt>
-<dd><p>
+<dd>
+ <p>
Quiet mode: Suppresses unnecessary output, including
progress indication. Without this option, when
- <span><strong class="command">dnssec-keygen</strong></span> is run interactively
+ <span class="command"><strong>dnssec-keygen</strong></span> is run interactively
to generate an RSA or DSA key pair, it will print a string
of symbols to <code class="filename">stderr</code> indicating the
progress of the key generation. A '.' indicates that a
round of the Miller-Rabin primality test; a space
means that the number has passed all the tests and is
a satisfactory key.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-r <em class="replaceable"><code>randomdev</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the source of randomness. If the operating
system does not provide a <code class="filename">/dev/random</code>
or equivalent device, the default source of randomness
data to be used instead of the default. The special value
<code class="filename">keyboard</code> indicates that keyboard
input should be used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-S <em class="replaceable"><code>key</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Create a new key which is an explicit successor to an
existing key. The name, algorithm, size, and type of the
key will be set to match the existing key. The activation
the existing one. The publication date will be set to the
activation date minus the prepublication interval, which
defaults to 30 days.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s <em class="replaceable"><code>strength</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the strength value of the key. The strength is
a number between 0 and 15, and currently has no defined
purpose in DNSSEC.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-T <em class="replaceable"><code>rrtype</code></em></span></dt>
<dd>
-<p>
Specifies the resource record type to use for the key.
<code class="option">rrtype</code> must be either DNSKEY or KEY. The
default is DNSKEY when using a DNSSEC algorithm, but it can be
Using any TSIG algorithm (HMAC-* or DH) forces this option
to KEY.
</p>
-</dd>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>type</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Indicates the use of the key. <code class="option">type</code> must be
one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default
is AUTHCONF. AUTH refers to the ability to authenticate
data, and CONF the ability to encrypt data.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2676913"></a><h2>TIMING OPTIONS</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.10.9"></a><h2>TIMING OPTIONS</h2>
+
+
+ <p>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
an offset from the present time. For convenience, if such an offset
is computed in seconds. To explicitly prevent a date from being
set, use 'none' or 'never'.
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which a key is to be published to the zone.
After that date, the key will be included in the zone but will
not be used to sign it. If not set, and if the -G option has
not been used, the default is "now".
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-A <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be activated. After that
date, the key will be included in the zone and used to sign
it. If not set, and if the -G option has not been used, the
default is "now". If set, if and -P is not set, then
the publication date will be set to the activation date
minus the prepublication interval.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-R <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be revoked. After that
date, the key will be flagged as revoked. It will be included
in the zone and will be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-I <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be retired. After that
date, the key will still be included in the zone, but it
will not be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be deleted. After that
date, the key will no longer be included in the zone. (It
may remain in the key repository, however.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
<dd>
-<p>
Sets the prepublication interval for a key. If set, then
the publication and activation dates must be separated by at least
this much time. If the activation date is specified but the
the publication date is specified but activation date isn't,
then activation will be set to this much time after publication.
</p>
-<p>
If the key is being created as an explicit successor to another
key, then the default prepublication interval is 30 days;
otherwise it is zero.
</p>
-<p>
As with date offsets, if the argument is followed by one of
the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
interval is measured in years, months, weeks, days, hours,
or minutes, respectively. Without a suffix, the interval is
measured in seconds.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2677102"></a><h2>GENERATED KEYS</h2>
-<p>
- When <span><strong class="command">dnssec-keygen</strong></span> completes
+ </div>
+
+
+ <div class="refsection">
+<a name="id-1.14.10.10"></a><h2>GENERATED KEYS</h2>
+
+ <p>
+ When <span class="command"><strong>dnssec-keygen</strong></span> completes
successfully,
it prints a string of the form <code class="filename">Knnnn.+aaa+iiiii</code>
to the standard output. This is an identification string for
the key it has generated.
</p>
-<div class="itemizedlist"><ul type="disc">
-<li><p><code class="filename">nnnn</code> is the key name.
- </p></li>
-<li><p><code class="filename">aaa</code> is the numeric representation
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p><code class="filename">nnnn</code> is the key name.
+ </p>
+ </li>
+<li class="listitem">
+ <p><code class="filename">aaa</code> is the numeric representation
of the
algorithm.
- </p></li>
-<li><p><code class="filename">iiiii</code> is the key identifier (or
+ </p>
+ </li>
+<li class="listitem">
+ <p><code class="filename">iiiii</code> is the key identifier (or
footprint).
- </p></li>
+ </p>
+ </li>
</ul></div>
-<p><span><strong class="command">dnssec-keygen</strong></span>
+ <p><span class="command"><strong>dnssec-keygen</strong></span>
creates two files, with names based
on the printed string. <code class="filename">Knnnn.+aaa+iiiii.key</code>
contains the public key, and
private
key.
</p>
-<p>
The <code class="filename">.key</code> file contains a DNS KEY record
that
can be inserted into a zone file (directly or with a $INCLUDE
statement).
</p>
-<p>
The <code class="filename">.private</code> file contains
algorithm-specific
fields. For obvious security reasons, this file does not have
general read permission.
</p>
-<p>
Both <code class="filename">.key</code> and <code class="filename">.private</code>
files are generated for symmetric encryption algorithms such as
HMAC-MD5, even though the public and private key are equivalent.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2677278"></a><h2>EXAMPLE</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.10.11"></a><h2>EXAMPLE</h2>
+
+ <p>
To generate a 768-bit DSA key for the domain
<strong class="userinput"><code>example.com</code></strong>, the following command would be
issued:
</p>
-<p><strong class="userinput"><code>dnssec-keygen -a DSA -b 768 -n ZONE example.com</code></strong>
+
<p><strong class="userinput"><code>dnssec-keygen -a DSA -b 768 -n ZONE example.com</code></strong>
</p>
-<p>
The command would print a string of the form:
</p>
-<p><strong class="userinput"><code>Kexample.com.+003+26160</code></strong>
+
<p><strong class="userinput"><code>Kexample.com.+003+26160</code></strong>
</p>
-<p>
- In this example, <span><strong class="command">dnssec-keygen</strong></span> creates
+ In this example, <span class="command"><strong>dnssec-keygen</strong></span> creates
the files <code class="filename">Kexample.com.+003+26160.key</code>
and
<code class="filename">Kexample.com.+003+26160.private</code>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2677335"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.10.12"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 2539</em>,
<em class="citetitle">RFC 2845</em>,
<em class="citetitle">RFC 4034</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2677366"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-revoke</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-keygen.html" title="dnssec-keygen">
<link rel="next" href="man.dnssec-settime.html" title="dnssec-settime">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-revoke"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-revoke</span> — Set the REVOKED bit on a DNSSEC key</p>
+<p>
+ <span class="application">dnssec-revoke</span>
+ — Set the REVOKED bit on a DNSSEC key
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-revoke</code> [<code class="option">-hr</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-f</code>] [<code class="option">-R</code>] {keyfile}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2634745"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-revoke</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-revoke</code>
+ [<code class="option">-hr</code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
+ [<code class="option">-f</code>]
+ [<code class="option">-R</code>]
+ {keyfile}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.11.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-revoke</strong></span>
reads a DNSSEC key file, sets the REVOKED bit on the key as defined
in RFC 5011, and creates a new pair of key files containing the
now-revoked key.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2634759"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.11.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Emit usage message and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the directory in which the key files are to reside.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-r</span></dt>
-<dd><p>
+<dd>
+ <p>
After writing the new keyset files remove the original keyset
files.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd>
-<p>
Specifies the cryptographic hardware to use, when applicable.
</p>
-<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
-</dd>
+ </dd>
<dt><span class="term">-f</span></dt>
-<dd><p>
- Force overwrite: Causes <span><strong class="command">dnssec-revoke</strong></span> to
+<dd>
+ <p>
+ Force overwrite: Causes <span class="command"><strong>dnssec-revoke</strong></span> to
write the new key pair even if a file already exists matching
the algorithm and key ID of the revoked key.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-R</span></dt>
-<dd><p>
+<dd>
+ <p>
Print the key tag of the key with the REVOKE bit set but do
not revoke the key.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2634897"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.11.9"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 5011</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2634921"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-settime</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-revoke.html" title="dnssec-revoke">
<link rel="next" href="man.dnssec-signzone.html" title="dnssec-signzone">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-settime"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-settime</span> — Set the key timing metadata for a DNSSEC key</p>
+<p>
+ <span class="application">dnssec-settime</span>
+ — Set the key timing metadata for a DNSSEC key
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-settime</code> [<code class="option">-f</code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-h</code>] [<code class="option">-V</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] {keyfile}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2641798"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-settime</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-settime</code>
+ [<code class="option">-f</code>]
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
+ {keyfile}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.12.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-settime</strong></span>
reads a DNSSEC private key file and sets the key timing metadata
as specified by the <code class="option">-P</code>, <code class="option">-A</code>,
<code class="option">-R</code>, <code class="option">-I</code>, and <code class="option">-D</code>
options. The metadata can then be used by
- <span><strong class="command">dnssec-signzone</strong></span> or other signing software to
+ <span class="command"><strong>dnssec-signzone</strong></span> or other signing software to
determine when a key is to be published, whether it should be
used for signing a zone, etc.
</p>
-<p>
If none of these options is set on the command line,
- then <span><strong class="command">dnssec-settime</strong></span> simply prints the key timing
+ then <span class="command"><strong>dnssec-settime</strong></span> simply prints the key timing
metadata already stored in the key.
</p>
-<p>
When key metadata fields are changed, both files of a key
pair (<code class="filename">Knnnn.+aaa+iiiii.key</code> and
<code class="filename">Knnnn.+aaa+iiiii.private</code>) are regenerated.
file. The private file's permissions are always set to be
inaccessible to anyone other than the owner (mode 0600).
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2642266"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.12.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-f</span></dt>
-<dd><p>
+<dd>
+ <p>
Force an update of an old-format key with no metadata fields.
- Without this option, <span><strong class="command">dnssec-settime</strong></span> will
+ Without this option, <span class="command"><strong>dnssec-settime</strong></span> will
fail when attempting to update a legacy key. With this option,
the key will be recreated in the new format, but with the
original key data retained. The key's creation date will be
set to the present time. If no other values are specified,
then the key's publication and activation dates will also
be set to the present time.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the directory in which the key files are to reside.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the default TTL to use for this key when it is converted
into a DNSKEY RR. If the key is imported into a zone,
this is the TTL that will be used for it, unless there was
is no existing DNSKEY RRset, the TTL will default to the
SOA TTL. Setting the default TTL to <code class="literal">0</code>
or <code class="literal">none</code> removes it from the key.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Emit usage message and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd>
-<p>
Specifies the cryptographic hardware to use, when applicable.
</p>
-<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2642406"></a><h2>TIMING OPTIONS</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.12.9"></a><h2>TIMING OPTIONS</h2>
+
+ <p>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
an offset from the present time. For convenience, if such an offset
days, hours, or minutes, respectively. Without a suffix, the offset
is computed in seconds. To unset a date, use 'none' or 'never'.
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which a key is to be published to the zone.
After that date, the key will be included in the zone but will
not be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-A <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be activated. After that
date, the key will be included in the zone and used to sign
it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-R <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be revoked. After that
date, the key will be flagged as revoked. It will be included
in the zone and will be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-I <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be retired. After that
date, the key will still be included in the zone, but it
will not be used to sign it.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the date on which the key is to be deleted. After that
date, the key will no longer be included in the zone. (It
may remain in the key repository, however.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-S <em class="replaceable"><code>predecessor key</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Select a key for which the key being modified will be an
explicit successor. The name, algorithm, size, and type of the
predecessor key must exactly match those of the key being
to the inactivation date of the predecessor. The publication
date will be set to the activation date minus the prepublication
interval, which defaults to 30 days.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
<dd>
-<p>
Sets the prepublication interval for a key. If set, then
the publication and activation dates must be separated by at least
this much time. If the activation date is specified but the
the publication date is specified but activation date isn't,
then activation will be set to this much time after publication.
</p>
-<p>
If the key is being set to be an explicit successor to another
key, then the default prepublication interval is 30 days;
otherwise it is zero.
</p>
-<p>
As with date offsets, if the argument is followed by one of
the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
interval is measured in years, months, weeks, days, hours,
or minutes, respectively. Without a suffix, the interval is
measured in seconds.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2646572"></a><h2>PRINTING OPTIONS</h2>
-<p>
- <span><strong class="command">dnssec-settime</strong></span> can also be used to print the
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.12.10"></a><h2>PRINTING OPTIONS</h2>
+
+ <p>
+ <span class="command"><strong>dnssec-settime</strong></span> can also be used to print the
timing metadata associated with a key.
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-u</span></dt>
-<dd><p>
+<dd>
+ <p>
Print times in UNIX epoch format.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>C/P/A/R/I/D/all</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Print a specific metadata value or set of metadata values.
The <code class="option">-p</code> option may be followed by one or more
of the following letters to indicate which value or values to print:
<code class="option">I</code> for the inactivation date, or
<code class="option">D</code> for the deletion date.
To print all of the metadata, use <code class="option">-p all</code>.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2646652"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.12.11"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 5011</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2646685"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-signzone</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-settime.html" title="dnssec-settime">
<link rel="next" href="man.dnssec-verify.html" title="dnssec-verify">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-signzone"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-signzone</span> — DNSSEC zone signing tool</p>
+<p>
+ <span class="application">dnssec-signzone</span>
+ — DNSSEC zone signing tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-signzone</code> [<code class="option">-a</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-d <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-D</code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-e <em class="replaceable"><code>end-time</code></em></code>] [<code class="option">-f <em class="replaceable"><code>output-file</code></em></code>] [<code class="option">-g</code>] [<code class="option">-h</code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-k <em class="replaceable"><code>key</code></em></code>] [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>] [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-M <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>] [<code class="option">-j <em class="replaceable"><code>jitter</code></em></code>] [<code class="option">-N <em class="replaceable"><code>soa-serial-format</code></em></code>] [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>] [<code class="option">-O <em class="replaceable"><code>output-format</code></em></code>] [<code class="option">-P</code>] [<code class="option">-p</code>] [<code class="option">-Q</code>] [<code class="option">-R</code>] [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-S</code>] [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>] [<code class="option">-T <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-t</code>] [<code class="option">-u</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">-X <em class="replaceable"><code>extended end-time</code></em></code>] [<code class="option">-x</code>] [<code class="option">-z</code>] [<code class="option">-3 <em class="replaceable"><code>salt</code></em></code>] [<code class="option">-H <em class="replaceable"><code>iterations</code></em></code>] [<code class="option">-A</code>] {zonefile} [key...]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2646342"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-signzone</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-signzone</code>
+ [<code class="option">-a</code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-d <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-D</code>]
+ [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
+ [<code class="option">-e <em class="replaceable"><code>end-time</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>output-file</code></em></code>]
+ [<code class="option">-g</code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-k <em class="replaceable"><code>key</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>]
+ [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>]
+ [<code class="option">-M <em class="replaceable"><code>domain</code></em></code>]
+ [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>]
+ [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>]
+ [<code class="option">-j <em class="replaceable"><code>jitter</code></em></code>]
+ [<code class="option">-N <em class="replaceable"><code>soa-serial-format</code></em></code>]
+ [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>]
+ [<code class="option">-O <em class="replaceable"><code>output-format</code></em></code>]
+ [<code class="option">-P</code>]
+ [<code class="option">-p</code>]
+ [<code class="option">-Q</code>]
+ [<code class="option">-R</code>]
+ [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>]
+ [<code class="option">-S</code>]
+ [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>]
+ [<code class="option">-T <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-t</code>]
+ [<code class="option">-u</code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-X <em class="replaceable"><code>extended end-time</code></em></code>]
+ [<code class="option">-x</code>]
+ [<code class="option">-z</code>]
+ [<code class="option">-3 <em class="replaceable"><code>salt</code></em></code>]
+ [<code class="option">-H <em class="replaceable"><code>iterations</code></em></code>]
+ [<code class="option">-A</code>]
+ {zonefile}
+ [key...]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.13.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-signzone</strong></span>
signs a zone. It generates
NSEC and RRSIG records and produces a signed version of the
zone. The security status of delegations from the signed zone
determined by the presence or absence of a
<code class="filename">keyset</code> file for each child zone.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2646361"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.13.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-a</span></dt>
-<dd><p>
+<dd>
+ <p>
Verify all generated signatures.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the DNS class of the zone.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-C</span></dt>
-<dd><p>
+<dd>
+ <p>
Compatibility mode: Generate a
<code class="filename">keyset-<em class="replaceable"><code>zonename</code></em></code>
file in addition to
<code class="filename">dsset-<em class="replaceable"><code>zonename</code></em></code>
when signing a zone, for use by older versions of
- <span><strong class="command">dnssec-signzone</strong></span>.
- </p></dd>
+ <span class="command"><strong>dnssec-signzone</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Look for <code class="filename">dsset-</code> or
<code class="filename">keyset-</code> files in <code class="option">directory</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D</span></dt>
-<dd><p>
+<dd>
+ <p>
Output only those record types automatically managed by
- <span><strong class="command">dnssec-signzone</strong></span>, i.e. RRSIG, NSEC,
+ <span class="command"><strong>dnssec-signzone</strong></span>, i.e. RRSIG, NSEC,
NSEC3 and NSEC3PARAM records. If smart signing
(<code class="option">-S</code>) is used, DNSKEY records are also
included. The resulting file can be included in the original
- zone file with <span><strong class="command">$INCLUDE</strong></span>. This option
+ zone file with <span class="command"><strong>$INCLUDE</strong></span>. This option
cannot be combined with <code class="option">-O raw</code>,
<code class="option">-O map</code>, or serial number updating.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd>
-<p>
When applicable, specifies the hardware to use for
cryptographic operations, such as a secure key store used
for signing.
</p>
-<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
-</dd>
+ </dd>
<dt><span class="term">-g</span></dt>
-<dd><p>
+<dd>
+ <p>
Generate DS records for child zones from
<code class="filename">dsset-</code> or <code class="filename">keyset-</code>
file. Existing DS records will be removed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Key repository: Specify a directory to search for DNSSEC keys.
If not specified, defaults to the current directory.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Treat specified key as a key signing key ignoring any
key flags. This option may be specified multiple times.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Generate a DLV set in addition to the key (DNSKEY) and DS sets.
The domain is appended to the name of the records.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-M <em class="replaceable"><code>maxttl</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the maximum TTL for the signed zone.
Any TTL higher than <em class="replaceable"><code>maxttl</code></em> in the
input zone will be reduced to <em class="replaceable"><code>maxttl</code></em>
<code class="option">max-zone-ttl</code> in <code class="filename">named.conf</code>.
(Note: This option is incompatible with <code class="option">-D</code>,
because it modifies non-DNSSEC data in the output zone.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s <em class="replaceable"><code>start-time</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the date and time when the generated RRSIG records
become valid. This can be either an absolute or relative
time. An absolute start time is indicated by a number
indicated by +N, which is N seconds from the current time.
If no <code class="option">start-time</code> is specified, the current
time minus 1 hour (to allow for clock skew) is used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-e <em class="replaceable"><code>end-time</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the date and time when the generated RRSIG records
expire. As with <code class="option">start-time</code>, an absolute
time is indicated in YYYYMMDDHHMMSS notation. A time relative
specified, 30 days from the start time is used as a default.
<code class="option">end-time</code> must be later than
<code class="option">start-time</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-X <em class="replaceable"><code>extended end-time</code></em></span></dt>
<dd>
-<p>
Specify the date and time when the generated RRSIG records
for the DNSKEY RRset will expire. This is to be used in cases
when the DNSKEY signatures need to persist longer than
of the KSK is kept offline and the KSK signature is to be
refreshed manually.
</p>
-<p>
As with <code class="option">start-time</code>, an absolute
time is indicated in YYYYMMDDHHMMSS notation. A time relative
to the start time is indicated with +N, which is N seconds from
30 days from the start time.) <code class="option">extended end-time</code>
must be later than <code class="option">start-time</code>.
</p>
-</dd>
+ </dd>
<dt><span class="term">-f <em class="replaceable"><code>output-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The name of the output file containing the signed zone. The
default is to append <code class="filename">.signed</code> to
the input filename. If <code class="option">output-file</code> is
set to <code class="literal">"-"</code>, then the signed zone is
written to the standard output, with a default output
format of "full".
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints a short summary of the options and arguments to
- <span><strong class="command">dnssec-signzone</strong></span>.
- </p></dd>
+ <span class="command"><strong>dnssec-signzone</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
<dd>
-<p>
When a previously-signed zone is passed as input, records
may be resigned. The <code class="option">interval</code> option
specifies the cycle interval as an offset from the current
cycle interval, it is retained. Otherwise, it is considered
to be expiring soon, and it will be replaced.
</p>
-<p>
The default cycle interval is one quarter of the difference
between the signature end and start times. So if neither
<code class="option">end-time</code> or <code class="option">start-time</code>
- are specified, <span><strong class="command">dnssec-signzone</strong></span>
+ are specified, <span class="command"><strong>dnssec-signzone</strong></span>
generates
signatures that are valid for 30 days, with a cycle
interval of 7.5 days. Therefore, if any existing RRSIG records
are due to expire in less than 7.5 days, they would be
replaced.
</p>
-</dd>
+ </dd>
<dt><span class="term">-I <em class="replaceable"><code>input-format</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The format of the input zone file.
- Possible formats are <span><strong class="command">"text"</strong></span> (default),
- <span><strong class="command">"raw"</strong></span>, and <span><strong class="command">"map"</strong></span>.
+ Possible formats are <span class="command"><strong>"text"</strong></span> (default),
+ <span class="command"><strong>"raw"</strong></span>, and <span class="command"><strong>"map"</strong></span>.
This option is primarily intended to be used for dynamic
signed zones so that the dumped zone file in a non-text
format containing updates can be signed directly.
The use of this option does not make much sense for
non-dynamic zones.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-j <em class="replaceable"><code>jitter</code></em></span></dt>
<dd>
-<p>
When signing a zone with a fixed signature lifetime, all
RRSIG records issued at the time of signing expires
simultaneously. If the zone is incrementally signed, i.e.
expire time, thus spreading incremental signature
regeneration over time.
</p>
-<p>
Signature lifetime jitter also to some extent benefits
validators and servers by spreading out cache expiration,
i.e. if large numbers of RRSIGs don't expire at the same time
from all caches there will be less congestion than if all
validators need to refetch at mostly the same time.
</p>
-</dd>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>serial</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
When writing a signed zone to "raw" or "map" format, set the
"source serial" value in the header to the specified serial
number. (This is expected to be used primarily for testing
purposes.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-n <em class="replaceable"><code>ncpus</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the number of threads to use. By default, one
thread is started for each detected CPU.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-N <em class="replaceable"><code>soa-serial-format</code></em></span></dt>
<dd>
-<p>
The SOA serial number format of the signed zone.
- Possible formats are <span><strong class="command">"keep"</strong></span> (default),
- <span><strong class="command">"increment"</strong></span>, <span><strong class="command">"unixtime"</strong></span>,
- and <span><strong class="command">"date"</strong></span>.
- </p>
-<div class="variablelist"><dl>
-<dt><span class="term"><span><strong class="command">"keep"</strong></span></span></dt>
-<dd><p>Do not modify the SOA serial number.</p></dd>
-<dt><span class="term"><span><strong class="command">"increment"</strong></span></span></dt>
-<dd><p>Increment the SOA serial number using RFC 1982
- arithmetics.</p></dd>
-<dt><span class="term"><span><strong class="command">"unixtime"</strong></span></span></dt>
-<dd><p>Set the SOA serial number to the number of seconds
- since epoch.</p></dd>
-<dt><span class="term"><span><strong class="command">"date"</strong></span></span></dt>
-<dd><p>Set the SOA serial number to today's date in
- YYYYMMDDNN format.</p></dd>
+ Possible formats are <span class="command"><strong>"keep"</strong></span> (default),
+ <span class="command"><strong>"increment"</strong></span>, <span class="command"><strong>"unixtime"</strong></span>,
+ and <span class="command"><strong>"date"</strong></span>.
+ </p>
+
+ <div class="variablelist"><dl class="variablelist">
+<dt><span class="term"><span class="command"><strong>"keep"</strong></span></span></dt>
+<dd>
+ <p>Do not modify the SOA serial number.</p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>"increment"</strong></span></span></dt>
+<dd>
+ <p>Increment the SOA serial number using RFC 1982
+ arithmetics.</p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>"unixtime"</strong></span></span></dt>
+<dd>
+ <p>Set the SOA serial number to the number of seconds
+ since epoch.</p>
+ </dd>
+<dt><span class="term"><span class="command"><strong>"date"</strong></span></span></dt>
+<dd>
+ <p>Set the SOA serial number to today's date in
+ YYYYMMDDNN format.</p>
+ </dd>
</dl></div>
-</dd>
+
+ </dd>
<dt><span class="term">-o <em class="replaceable"><code>origin</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The zone origin. If not specified, the name of the zone file
is assumed to be the origin.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-O <em class="replaceable"><code>output-format</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The format of the output file containing the signed zone.
- Possible formats are <span><strong class="command">"text"</strong></span> (default),
+ Possible formats are <span class="command"><strong>"text"</strong></span> (default),
which is the standard textual representation of the zone;
- <span><strong class="command">"full"</strong></span>, which is text output in a
+ <span class="command"><strong>"full"</strong></span>, which is text output in a
format suitable for processing by external scripts;
- and <span><strong class="command">"map"</strong></span>, <span><strong class="command">"raw"</strong></span>,
- and <span><strong class="command">"raw=N"</strong></span>, which store the zone in
- binary formats for rapid loading by <span><strong class="command">named</strong></span>.
- <span><strong class="command">"raw=N"</strong></span> specifies the format version of
+ and <span class="command"><strong>"map"</strong></span>, <span class="command"><strong>"raw"</strong></span>,
+ and <span class="command"><strong>"raw=N"</strong></span>, which store the zone in
+ binary formats for rapid loading by <span class="command"><strong>named</strong></span>.
+ <span class="command"><strong>"raw=N"</strong></span> specifies the format version of
the raw zone file: if N is 0, the raw file can be read by
- any version of <span><strong class="command">named</strong></span>; if N is 1, the file
+ any version of <span class="command"><strong>named</strong></span>; if N is 1, the file
can be read by release 9.9.0 or higher; the default is 1.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p</span></dt>
-<dd><p>
+<dd>
+ <p>
Use pseudo-random data when signing the zone. This is faster,
but less secure, than using real random data. This option
may be useful when signing large zones or when the entropy
source is limited.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-P</span></dt>
<dd>
-<p>
Disable post sign verification tests.
</p>
-<p>
The post sign verification test ensures that for each algorithm
in use there is at least one non revoked self signed KSK key,
that all revoked KSK keys are self signed, and that all records
in the zone are signed by the algorithm.
This option skips these tests.
</p>
-</dd>
+ </dd>
<dt><span class="term">-Q</span></dt>
<dd>
-<p>
Remove signatures from keys that are no longer active.
</p>
-<p>
Normally, when a previously-signed zone is passed as input
to the signer, and a DNSKEY record has been removed and
replaced with a new one, signatures from the old key
that are still within their validity period are retained.
This allows the zone to continue to validate with cached
copies of the old DNSKEY RRset. The <code class="option">-Q</code>
- forces <span><strong class="command">dnssec-signzone</strong></span> to remove
+ forces <span class="command"><strong>dnssec-signzone</strong></span> to remove
signatures from keys that are no longer active. This
enables ZSK rollover using the procedure described in
RFC 4641, section 4.2.1.1 ("Pre-Publish Key Rollover").
</p>
-</dd>
+ </dd>
<dt><span class="term">-R</span></dt>
<dd>
-<p>
Remove signatures from keys that are no longer published.
</p>
-<p>
This option is similar to <code class="option">-Q</code>, except it
- forces <span><strong class="command">dnssec-signzone</strong></span> to signatures from
+ forces <span class="command"><strong>dnssec-signzone</strong></span> to signatures from
keys that are no longer published. This enables ZSK rollover
using the procedure described in RFC 4641, section 4.2.1.2
("Double Signature Zone Signing Key Rollover").
</p>
-</dd>
+ </dd>
<dt><span class="term">-r <em class="replaceable"><code>randomdev</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the source of randomness. If the operating
system does not provide a <code class="filename">/dev/random</code>
or equivalent device, the default source of randomness
data to be used instead of the default. The special value
<code class="filename">keyboard</code> indicates that keyboard
input should be used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-S</span></dt>
<dd>
-<p>
- Smart signing: Instructs <span><strong class="command">dnssec-signzone</strong></span> to
+ Smart signing: Instructs <span class="command"><strong>dnssec-signzone</strong></span> to
search the key repository for keys that match the zone being
signed, and to include them in the zone if appropriate.
</p>
-<p>
When a key is found, its timing metadata is examined to
determine how it should be used, according to the following
rules. Each successive rule takes priority over the prior
ones:
</p>
-<div class="variablelist"><dl>
+ <div class="variablelist"><dl class="variablelist">
<dt></dt>
-<dd><p>
+<dd>
+ <p>
If no timing metadata has been set for the key, the key is
published in the zone and used to sign the zone.
- </p></dd>
+ </p>
+ </dd>
<dt></dt>
-<dd><p>
+<dd>
+ <p>
If the key's publication date is set and is in the past, the
key is published in the zone.
- </p></dd>
+ </p>
+ </dd>
<dt></dt>
-<dd><p>
+<dd>
+ <p>
If the key's activation date is set and in the past, the
key is published (regardless of publication date) and
used to sign the zone.
- </p></dd>
+ </p>
+ </dd>
<dt></dt>
-<dd><p>
+<dd>
+ <p>
If the key's revocation date is set and in the past, and the
key is published, then the key is revoked, and the revoked key
is used to sign the zone.
- </p></dd>
+ </p>
+ </dd>
<dt></dt>
-<dd><p>
+<dd>
+ <p>
If either of the key's unpublication or deletion dates are set
and in the past, the key is NOT published or used to sign the
zone, regardless of any other metadata.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</dd>
+ </dd>
<dt><span class="term">-T <em class="replaceable"><code>ttl</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies a TTL to be used for new DNSKEY records imported
into the zone from the key repository. If not
specified, the default is the TTL value from the zone's SOA
them, or if any of the imported DNSKEY records had a default
TTL value. In the event of a a conflict between TTL values in
imported keys, the shortest one is used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-t</span></dt>
-<dd><p>
+<dd>
+ <p>
Print statistics at completion.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-u</span></dt>
-<dd><p>
+<dd>
+ <p>
Update NSEC/NSEC3 chain when re-signing a previously signed
zone. With this option, a zone signed with NSEC can be
switched to NSEC3, or a zone signed with NSEC3 can
be switch to NSEC or to NSEC3 with different parameters.
- Without this option, <span><strong class="command">dnssec-signzone</strong></span> will
+ Without this option, <span class="command"><strong>dnssec-signzone</strong></span> will
retain the existing chain when re-signing.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-x</span></dt>
-<dd><p>
+<dd>
+ <p>
Only sign the DNSKEY RRset with key-signing keys, and omit
signatures from zone-signing keys. (This is similar to the
- <span><strong class="command">dnssec-dnskey-kskonly yes;</strong></span> zone option in
- <span><strong class="command">named</strong></span>.)
- </p></dd>
+ <span class="command"><strong>dnssec-dnskey-kskonly yes;</strong></span> zone option in
+ <span class="command"><strong>named</strong></span>.)
+ </p>
+ </dd>
<dt><span class="term">-z</span></dt>
-<dd><p>
+<dd>
+ <p>
Ignore KSK flag on key when determining what to sign. This
causes KSK-flagged keys to sign all records, not just the
DNSKEY RRset. (This is similar to the
- <span><strong class="command">update-check-ksk no;</strong></span> zone option in
- <span><strong class="command">named</strong></span>.)
- </p></dd>
+ <span class="command"><strong>update-check-ksk no;</strong></span> zone option in
+ <span class="command"><strong>named</strong></span>.)
+ </p>
+ </dd>
<dt><span class="term">-3 <em class="replaceable"><code>salt</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Generate an NSEC3 chain with the given hex encoded salt.
A dash (<em class="replaceable"><code>salt</code></em>) can
be used to indicate that no salt is to be used when generating the NSEC3 chain.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-H <em class="replaceable"><code>iterations</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
When generating an NSEC3 chain, use this many iterations. The
default is 10.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-A</span></dt>
<dd>
-<p>
When generating an NSEC3 chain set the OPTOUT flag on all
NSEC3 records and do not generate NSEC3 records for insecure
delegations.
</p>
-<p>
Using this option twice (i.e., <code class="option">-AA</code>)
turns the OPTOUT flag off for all records. This is useful
when using the <code class="option">-u</code> option to modify an NSEC3
chain which previously had OPTOUT set.
</p>
-</dd>
+ </dd>
<dt><span class="term">zonefile</span></dt>
-<dd><p>
+<dd>
+ <p>
The file containing the zone to be signed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">key</span></dt>
-<dd><p>
+<dd>
+ <p>
Specify which keys should be used to sign the zone. If
no keys are specified, then the zone will be examined
for DNSKEY records at the zone apex. If these are found and
there are matching private keys, in the current directory,
then these will be used for signing.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2678967"></a><h2>EXAMPLE</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.13.9"></a><h2>EXAMPLE</h2>
+
+ <p>
The following command signs the <strong class="userinput"><code>example.com</code></strong>
- zone with the DSA key generated by <span><strong class="command">dnssec-keygen</strong></span>
- (Kexample.com.+003+17247). Because the <span><strong class="command">-S</strong></span> option
+ zone with the DSA key generated by <span class="command"><strong>dnssec-keygen</strong></span>
+ (Kexample.com.+003+17247). Because the <span class="command"><strong>-S</strong></span> option
is not being used, the zone's keys must be in the master file
(<code class="filename">db.example.com</code>). This invocation looks
for <code class="filename">dsset</code> files, in the current directory,
- so that DS records can be imported from them (<span><strong class="command">-g</strong></span>).
+ so that DS records can be imported from them (<span class="command"><strong>-g</strong></span>).
</p>
<pre class="programlisting">% dnssec-signzone -g -o example.com db.example.com \
Kexample.com.+003+17247
db.example.com.signed
%</pre>
-<p>
- In the above example, <span><strong class="command">dnssec-signzone</strong></span> creates
+ In the above example, <span class="command"><strong>dnssec-signzone</strong></span> creates
the file <code class="filename">db.example.com.signed</code>. This
file should be referenced in a zone statement in a
<code class="filename">named.conf</code> file.
</p>
-<p>
This example re-signs a previously signed zone with default parameters.
The private keys are assumed to be in the current directory.
</p>
% dnssec-signzone -o example.com db.example.com
db.example.com.signed
%</pre>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2679046"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.13.10"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 4033</em>, <em class="citetitle">RFC 4641</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2679074"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-verify</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-signzone.html" title="dnssec-signzone">
-<link rel="next" href="man.named-checkconf.html" title="named-checkconf">
+<link rel="next" href="man.lwresd.html" title="lwresd">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<td width="20%" align="left">
<a accesskey="p" href="man.dnssec-signzone.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
-<td width="20%" align="right"> <a accesskey="n" href="man.named-checkconf.html">Next</a>
+<td width="20%" align="right"> <a accesskey="n" href="man.lwresd.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnssec-verify"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnssec-verify</span> — DNSSEC zone verification tool</p>
+<p>
+ <span class="application">dnssec-verify</span>
+ — DNSSEC zone verification tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnssec-verify</code> [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>] [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">-x</code>] [<code class="option">-z</code>] {zonefile}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2646843"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">dnssec-verify</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnssec-verify</code>
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
+ [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>]
+ [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>]
+ [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-x</code>]
+ [<code class="option">-z</code>]
+ {zonefile}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.14.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>dnssec-verify</strong></span>
verifies that a zone is fully signed for each algorithm found
in the DNSKEY RRset for the zone, and that the NSEC / NSEC3
chains are complete.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2646857"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.14.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the DNS class of the zone.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd>
-<p>
Specifies the cryptographic hardware to use, when applicable.
</p>
-<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
-</dd>
+ </dd>
<dt><span class="term">-I <em class="replaceable"><code>input-format</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The format of the input zone file.
- Possible formats are <span><strong class="command">"text"</strong></span> (default)
- and <span><strong class="command">"raw"</strong></span>.
+ Possible formats are <span class="command"><strong>"text"</strong></span> (default)
+ and <span class="command"><strong>"raw"</strong></span>.
This option is primarily intended to be used for dynamic
signed zones so that the dumped zone file in a non-text
format containing updates can be verified independently.
The use of this option does not make much sense for
non-dynamic zones.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-o <em class="replaceable"><code>origin</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The zone origin. If not specified, the name of the zone file
is assumed to be the origin.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets the debugging level.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints version information.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-x</span></dt>
-<dd><p>
+<dd>
+ <p>
Only verify that the DNSKEY RRset is signed with key-signing
keys. Without this flag, it is assumed that the DNSKEY RRset
will be signed by all active keys. When this flag is set,
it will not be an error if the DNSKEY RRset is not signed
by zone-signing keys. This corresponds to the <code class="option">-x</code>
- option in <span><strong class="command">dnssec-signzone</strong></span>.
- </p></dd>
+ option in <span class="command"><strong>dnssec-signzone</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-z</span></dt>
<dd>
-<p>
Ignore the KSK flag on the keys when determining whether
the zone if correctly signed. Without this flag it is
assumed that there will be a non-revoked, self-signed
that RRsets other than DNSKEY RRset will be signed with
a different DNSKEY without the KSK flag set.
</p>
-<p>
With this flag set, we only require that for each algorithm,
there will be at least one non-revoked, self-signed DNSKEY,
regardless of the KSK flag state, and that other RRsets
will be signed by a non-revoked key for the same algorithm
that includes the self-signed key; the same key may be used
for both purposes. This corresponds to the <code class="option">-z</code>
- option in <span><strong class="command">dnssec-signzone</strong></span>.
+ option in <span class="command"><strong>dnssec-signzone</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term">zonefile</span></dt>
-<dd><p>
+<dd>
+ <p>
The file containing the zone to be signed.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2647109"></a><h2>SEE ALSO</h2>
-<p>
- <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.14.9"></a><h2>SEE ALSO</h2>
+
+ <p>
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-signzone</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 4033</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2647134"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<td width="40%" align="left">
<a accesskey="p" href="man.dnssec-signzone.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
-<td width="40%" align="right"> <a accesskey="n" href="man.named-checkconf.html">Next</a>
+<td width="40%" align="right"> <a accesskey="n" href="man.lwresd.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">dnssec-signzone</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
-<td width="40%" align="right" valign="top"> <span class="application">named-checkconf</span>
+<td width="40%" align="right" valign="top"> <span class="application">lwresd</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnstap-read</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.arpaname.html" title="arpaname">
<link rel="next" href="man.genrandom.html" title="genrandom">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.dnstap-read"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">dnstap-read</span> — print dnstap data in human-readable form</p>
+<p>
+ <span class="application">dnstap-read</span>
+ — print dnstap data in human-readable form
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">dnstap-read</code> [<code class="option">-m</code>] [<code class="option">-p</code>] [<code class="option">-y</code>] {<em class="replaceable"><code>file</code></em>}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745265"></a><h2>DESCRIPTION</h2>
-<p>
- <span><strong class="command">dnstap-read</strong></span>
- reads <span><strong class="command">dnstap</strong></span> data from a specified file
+ <div class="cmdsynopsis"><p>
+ <code class="command">dnstap-read</code>
+ [<code class="option">-m</code>]
+ [<code class="option">-p</code>]
+ [<code class="option">-y</code>]
+ {<em class="replaceable"><code>file</code></em>}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.28.7"></a><h2>DESCRIPTION</h2>
+
+ <p>
+ <span class="command"><strong>dnstap-read</strong></span>
+ reads <span class="command"><strong>dnstap</strong></span> data from a specified file
and prints it in a human-readable format. By default,
- <span><strong class="command">dnstap</strong></span> data is printed in a short summary
+ <span class="command"><strong>dnstap</strong></span> data is printed in a short summary
format, but if the <code class="option">-y</code> option is specified,
then a longer and more detailed YAML format is used instead.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746114"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.28.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-m</span></dt>
-<dd><p>
+<dd>
+ <p>
Trace memory allocations; used for debugging memory leaks.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p</span></dt>
-<dd><p>
- After printing the <span><strong class="command">dnstap</strong></span> data, print
+<dd>
+ <p>
+ After printing the <span class="command"><strong>dnstap</strong></span> data, print
the text form of the DNS message that was encapsulated in the
- <span><strong class="command">dnstap</strong></span> frame.
- </p></dd>
+ <span class="command"><strong>dnstap</strong></span> frame.
+ </p>
+ </dd>
<dt><span class="term">-y</span></dt>
-<dd><p>
- Print <span><strong class="command">dnstap</strong></span> data in a detailed YAML
+<dd>
+ <p>
+ Print <span class="command"><strong>dnstap</strong></span> data in a detailed YAML
format. Implies <code class="option">-p</code>.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746183"></a><h2>SEE ALSO</h2>
-<p>
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">nsupdate</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.28.9"></a><h2>SEE ALSO</h2>
+
+ <p>
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">nsupdate</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746214"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>genrandom</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnstap-read.html" title="dnstap-read">
<link rel="next" href="man.isc-hmac-fixup.html" title="isc-hmac-fixup">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.genrandom"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">genrandom</span> — generate a file containing random data</p>
+<p>
+ <span class="application">genrandom</span>
+ — generate a file containing random data
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">genrandom</code> [<code class="option">-n <em class="replaceable"><code>number</code></em></code>] {<em class="replaceable"><code>size</code></em>} {<em class="replaceable"><code>filename</code></em>}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746392"></a><h2>DESCRIPTION</h2>
-<p>
- <span><strong class="command">genrandom</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">genrandom</code>
+ [<code class="option">-n <em class="replaceable"><code>number</code></em></code>]
+ {<em class="replaceable"><code>size</code></em>}
+ {<em class="replaceable"><code>filename</code></em>}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.29.7"></a><h2>DESCRIPTION</h2>
+
+ <p>
+ <span class="command"><strong>genrandom</strong></span>
generates a file or a set of files containing a specified quantity
of pseudo-random data, which can be used as a source of entropy for
other commands on systems with no random device.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746407"></a><h2>ARGUMENTS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.29.8"></a><h2>ARGUMENTS</h2>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-n <em class="replaceable"><code>number</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
In place of generating one file, generates <code class="option">number</code>
(from 2 to 9) files, appending <code class="option">number</code> to the name.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">size</span></dt>
-<dd><p>
+<dd>
+ <p>
The size of the file, in kilobytes, to generate.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">filename</span></dt>
-<dd><p>
+<dd>
+ <p>
The file name into which random data should be written.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746468"></a><h2>SEE ALSO</h2>
-<p>
- <span class="citerefentry"><span class="refentrytitle">rand</span>(3)</span>,
- <span class="citerefentry"><span class="refentrytitle">arc4random</span>(3)</span>
- </p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746494"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.29.9"></a><h2>SEE ALSO</h2>
+
+ <p>
+ <span class="citerefentry">
+ <span class="refentrytitle">rand</span>(3)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">arc4random</span>(3)
+ </span>
</p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>host</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dig.html" title="dig">
<link rel="next" href="man.delv.html" title="delv">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.host"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p>host — DNS lookup utility</p>
+<p>
+ host
+ — DNS lookup utility
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">host</code> [<code class="option">-aCdlnrsTwv</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-N <em class="replaceable"><code>ndots</code></em></code>] [<code class="option">-R <em class="replaceable"><code>number</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-W <em class="replaceable"><code>wait</code></em></code>] [<code class="option">-m <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-4</code>] [<code class="option">-6</code>] [<code class="option">-v</code>] [<code class="option">-V</code>] {name} [server]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2617856"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">host</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">host</code>
+ [<code class="option">-aCdlnrsTwv</code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-N <em class="replaceable"><code>ndots</code></em></code>]
+ [<code class="option">-R <em class="replaceable"><code>number</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>type</code></em></code>]
+ [<code class="option">-W <em class="replaceable"><code>wait</code></em></code>]
+ [<code class="option">-m <em class="replaceable"><code>flag</code></em></code>]
+ [<code class="option">-4</code>]
+ [<code class="option">-6</code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-V</code>]
+ {name}
+ [server]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.3.7"></a><h2>DESCRIPTION</h2>
+
+
+ <p><span class="command"><strong>host</strong></span>
is a simple utility for performing DNS lookups.
It is normally used to convert names to IP addresses and vice versa.
When no arguments or options are given,
- <span><strong class="command">host</strong></span>
+ <span class="command"><strong>host</strong></span>
prints a short summary of its command line arguments and options.
</p>
-<p><em class="parameter"><code>name</code></em> is the domain name that is to be
+
+ <p><em class="parameter"><code>name</code></em> is the domain name that is to be
looked
up. It can also be a dotted-decimal IPv4 address or a colon-delimited
- IPv6 address, in which case <span><strong class="command">host</strong></span> will by
+ IPv6 address, in which case <span class="command"><strong>host</strong></span> will by
default
perform a reverse lookup for that address.
<em class="parameter"><code>server</code></em> is an optional argument which
is either
- the name or IP address of the name server that <span><strong class="command">host</strong></span>
+ the name or IP address of the name server that <span class="command"><strong>host</strong></span>
should query instead of the server or servers listed in
<code class="filename">/etc/resolv.conf</code>.
</p>
-<p>
+
+ <p>
The <code class="option">-a</code> (all) option is equivalent to setting the
- <code class="option">-v</code> option and asking <span><strong class="command">host</strong></span> to make
+ <code class="option">-v</code> option and asking <span class="command"><strong>host</strong></span> to make
a query of type ANY.
</p>
-<p>
- When the <code class="option">-C</code> option is used, <span><strong class="command">host</strong></span>
+
+ <p>
+ When the <code class="option">-C</code> option is used, <span class="command"><strong>host</strong></span>
will attempt to display the SOA records for zone
<em class="parameter"><code>name</code></em> from all the listed
authoritative name
servers for that zone. The list of name servers is defined by the NS
records that are found for the zone.
</p>
-<p>
+
+ <p>
The <code class="option">-c</code> option instructs to make a DNS query of class
<em class="parameter"><code>class</code></em>. This can be used to lookup
Hesiod or
Chaosnet class resource records. The default class is IN (Internet).
</p>
-<p>
- Verbose output is generated by <span><strong class="command">host</strong></span> when
+
+ <p>
+ Verbose output is generated by <span class="command"><strong>host</strong></span> when
the
<code class="option">-d</code> or <code class="option">-v</code> option is used. The two
options are equivalent. They have been provided for backwards
<em class="parameter"><code>debug</code></em> option in
<code class="filename">/etc/resolv.conf</code>.
</p>
-<p>
+
+ <p>
List mode is selected by the <code class="option">-l</code> option. This makes
- <span><strong class="command">host</strong></span> perform a zone transfer for zone
+ <span class="command"><strong>host</strong></span> perform a zone transfer for zone
<em class="parameter"><code>name</code></em>. Transfer the zone printing out
the NS, PTR
and address records (A/AAAA). If combined with <code class="option">-a</code>
all records will be printed.
</p>
-<p>
+
+ <p>
The <code class="option">-i</code>
option specifies that reverse lookups of IPv6 addresses should
use the IP6.INT domain as defined in RFC1886.
The default is to use IP6.ARPA.
</p>
-<p>
+
+ <p>
The <code class="option">-N</code> option sets the number of dots that have to be
in <em class="parameter"><code>name</code></em> for it to be considered
absolute. The
or <span class="type">domain</span> directive in
<code class="filename">/etc/resolv.conf</code>.
</p>
-<p>
+
+ <p>
The number of UDP retries for a lookup can be changed with the
<code class="option">-R</code> option. <em class="parameter"><code>number</code></em>
indicates
- how many times <span><strong class="command">host</strong></span> will repeat a query
+ how many times <span class="command"><strong>host</strong></span> will repeat a query
that does
not get answered. If
<em class="parameter"><code>number</code></em> is negative or zero, the
the value of the <em class="parameter"><code>attempts</code></em> option in
<code class="filename">/etc/resolv.conf</code>, if set.
</p>
-<p>
+
+ <p>
Non-recursive queries can be made via the <code class="option">-r</code> option.
Setting this option clears the <span class="type">RD</span> — recursion
- desired — bit in the query which <span><strong class="command">host</strong></span> makes.
+ desired — bit in the query which <span class="command"><strong>host</strong></span> makes.
This should mean that the name server receiving the query will not
attempt to resolve <em class="parameter"><code>name</code></em>. The
- <code class="option">-r</code> option enables <span><strong class="command">host</strong></span>
+ <code class="option">-r</code> option enables <span class="command"><strong>host</strong></span>
to mimic
the behavior of a name server by making non-recursive queries and
expecting to receive answers to those queries that are usually
referrals to other name servers.
</p>
-<p>
- By default, <span><strong class="command">host</strong></span> uses UDP when making
+
+ <p>
+ By default, <span class="command"><strong>host</strong></span> uses UDP when making
queries. The
<code class="option">-T</code> option makes it use a TCP connection when querying
the name server. TCP will be automatically selected for queries that
require it, such as zone transfer (AXFR) requests.
</p>
-<p>
- The <code class="option">-4</code> option forces <span><strong class="command">host</strong></span> to only
+
+ <p>
+ The <code class="option">-4</code> option forces <span class="command"><strong>host</strong></span> to only
use IPv4 query transport. The <code class="option">-6</code> option forces
- <span><strong class="command">host</strong></span> to only use IPv6 query transport.
+ <span class="command"><strong>host</strong></span> to only use IPv6 query transport.
</p>
-<p>
+
+ <p>
The <code class="option">-t</code> option is used to select the query type.
<em class="parameter"><code>type</code></em> can be any recognized query
type: CNAME,
NS, SOA, SIG, KEY, AXFR, etc. When no query type is specified,
- <span><strong class="command">host</strong></span> automatically selects an appropriate
+ <span class="command"><strong>host</strong></span> automatically selects an appropriate
query
type. By default, it looks for A, AAAA, and MX records, but if the
<code class="option">-C</code> option was given, queries will be made for SOA
records, and if <em class="parameter"><code>name</code></em> is a
dotted-decimal IPv4
- address or colon-delimited IPv6 address, <span><strong class="command">host</strong></span> will
+ address or colon-delimited IPv6 address, <span class="command"><strong>host</strong></span> will
query for PTR records. If a query type of IXFR is chosen the starting
serial number can be specified by appending an equal followed by the
starting serial number (e.g. -t IXFR=12345678).
</p>
-<p>
+
+ <p>
The time to wait for a reply can be controlled through the
<code class="option">-W</code> and <code class="option">-w</code> options. The
- <code class="option">-W</code> option makes <span><strong class="command">host</strong></span>
+ <code class="option">-W</code> option makes <span class="command"><strong>host</strong></span>
wait for
<em class="parameter"><code>wait</code></em> seconds. If <em class="parameter"><code>wait</code></em>
is less than one, the wait interval is set to one second. When the
- <code class="option">-w</code> option is used, <span><strong class="command">host</strong></span>
+ <code class="option">-w</code> option is used, <span class="command"><strong>host</strong></span>
will
effectively wait forever for a reply. The time to wait for a response
will be set to the number of seconds given by the hardware's maximum
- value for an integer quantity. By default, <span><strong class="command">host</strong></span>
+ value for an integer quantity. By default, <span class="command"><strong>host</strong></span>
will wait for 5 seconds for UDP responses and 10 seconds for TCP
connections. These defaults can be overridden by the
<em class="parameter"><code>timeout</code></em> option in
<code class="filename">/etc/resolv.conf</code>.
</p>
-<p>
- The <code class="option">-s</code> option tells <span><strong class="command">host</strong></span>
+
+ <p>
+ The <code class="option">-s</code> option tells <span class="command"><strong>host</strong></span>
<span class="emphasis"><em>not</em></span> to send the query to the next nameserver
if any server responds with a SERVFAIL response, which is the
reverse of normal stub resolver behavior.
</p>
-<p>
+
+ <p>
The <code class="option">-m</code> can be used to set the memory usage debugging
flags
<em class="parameter"><code>record</code></em>, <em class="parameter"><code>usage</code></em> and
<em class="parameter"><code>trace</code></em>.
</p>
-<p>
- The <code class="option">-V</code> option causes <span><strong class="command">host</strong></span>
+
+ <p>
+ The <code class="option">-V</code> option causes <span class="command"><strong>host</strong></span>
to print the version number and exit.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2618828"></a><h2>IDN SUPPORT</h2>
-<p>
- If <span><strong class="command">host</strong></span> has been built with IDN (internationalized
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.3.8"></a><h2>IDN SUPPORT</h2>
+
+ <p>
+ If <span class="command"><strong>host</strong></span> has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
- <span><strong class="command">host</strong></span> appropriately converts character encoding of
+ <span class="command"><strong>host</strong></span> appropriately converts character encoding of
domain name before sending a request to DNS server or displaying a
reply from the server.
If you'd like to turn off the IDN support for some reason, defines
the <code class="envar">IDN_DISABLE</code> environment variable.
The IDN support is disabled if the variable is set when
- <span><strong class="command">host</strong></span> runs.
+ <span class="command"><strong>host</strong></span> runs.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620427"></a><h2>FILES</h2>
-<p><code class="filename">/etc/resolv.conf</code>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.3.9"></a><h2>FILES</h2>
+
+ <p><code class="filename">/etc/resolv.conf</code>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2620441"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">dig</span>(1)</span>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>.
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.3.10"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">dig</span>(1)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>.
</p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>isc-hmac-fixup</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.genrandom.html" title="genrandom">
-<link rel="next" href="man.named-journalprint.html" title="named-journalprint">
+<link rel="next" href="man.nsec3hash.html" title="nsec3hash">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<td width="20%" align="left">
<a accesskey="p" href="man.genrandom.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
-<td width="20%" align="right"> <a accesskey="n" href="man.named-journalprint.html">Next</a>
+<td width="20%" align="right"> <a accesskey="n" href="man.nsec3hash.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.isc-hmac-fixup"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">isc-hmac-fixup</span> — fixes HMAC keys generated by older versions of BIND</p>
+<p>
+ <span class="application">isc-hmac-fixup</span>
+ — fixes HMAC keys generated by older versions of BIND
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">isc-hmac-fixup</code> {<em class="replaceable"><code>algorithm</code></em>} {<em class="replaceable"><code>secret</code></em>}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745732"></a><h2>DESCRIPTION</h2>
-<p>
+ <div class="cmdsynopsis"><p>
+ <code class="command">isc-hmac-fixup</code>
+ {<em class="replaceable"><code>algorithm</code></em>}
+ {<em class="replaceable"><code>secret</code></em>}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.30.7"></a><h2>DESCRIPTION</h2>
+
+ <p>
Versions of BIND 9 up to and including BIND 9.6 had a bug causing
HMAC-SHA* TSIG keys which were longer than the digest length of the
hash algorithm (i.e., SHA1 keys longer than 160 bits, SHA256 keys
message authentication code that was incompatible with other DNS
implementations.
</p>
-<p>
This bug has been fixed in BIND 9.7. However, the fix may
cause incompatibility between older and newer versions of
- BIND, when using long keys. <span><strong class="command">isc-hmac-fixup</strong></span>
+ BIND, when using long keys. <span class="command"><strong>isc-hmac-fixup</strong></span>
modifies those keys to restore compatibility.
</p>
-<p>
- To modify a key, run <span><strong class="command">isc-hmac-fixup</strong></span> and
+ To modify a key, run <span class="command"><strong>isc-hmac-fixup</strong></span> and
specify the key's algorithm and secret on the command line. If the
secret is longer than the digest length of the algorithm (64 bytes
for SHA1 through SHA256, or 128 bytes for SHA384 and SHA512), then a
secret. (If the secret did not require conversion, then it will be
printed without modification.)
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746579"></a><h2>SECURITY CONSIDERATIONS</h2>
-<p>
- Secrets that have been converted by <span><strong class="command">isc-hmac-fixup</strong></span>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.30.8"></a><h2>SECURITY CONSIDERATIONS</h2>
+
+ <p>
+ Secrets that have been converted by <span class="command"><strong>isc-hmac-fixup</strong></span>
are shortened, but as this is how the HMAC protocol works in
operation anyway, it does not affect security. RFC 2104 notes,
"Keys longer than [the digest length] are acceptable but the
extra length would not significantly increase the function
strength."
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746595"></a><h2>SEE ALSO</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.30.9"></a><h2>SEE ALSO</h2>
+
+ <p>
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 2104</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746612"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<td width="40%" align="left">
<a accesskey="p" href="man.genrandom.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
-<td width="40%" align="right"> <a accesskey="n" href="man.named-journalprint.html">Next</a>
+<td width="40%" align="right"> <a accesskey="n" href="man.nsec3hash.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">genrandom</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
-<td width="40%" align="right" valign="top"> <span class="application">named-journalprint</span>
+<td width="40%" align="right" valign="top"> <span class="application">nsec3hash</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwresd</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
-<link rel="prev" href="man.named.conf.html" title="named.conf">
-<link rel="next" href="man.named-journalprint.html" title="named-journalprint">
+<link rel="prev" href="man.dnssec-verify.html" title="dnssec-verify">
+<link rel="next" href="man.named.html" title="named">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<tr><th colspan="3" align="center"><span class="application">lwresd</span></th></tr>
<tr>
<td width="20%" align="left">
-<a accesskey="p" href="man.named.conf.html">Prev</a> </td>
+<a accesskey="p" href="man.dnssec-verify.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
-<td width="20%" align="right"> <a accesskey="n" href="man.named-journalprint.html">Next</a>
+<td width="20%" align="right"> <a accesskey="n" href="man.named.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.lwresd"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">lwresd</span> — lightweight resolver daemon</p>
+<p>
+ <span class="application">lwresd</span>
+ — lightweight resolver daemon
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">lwresd</code> [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-C <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-d <em class="replaceable"><code>debug-level</code></em></code>] [<code class="option">-f</code>] [<code class="option">-g</code>] [<code class="option">-i <em class="replaceable"><code>pid-file</code></em></code>] [<code class="option">-m <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-n <em class="replaceable"><code>#cpus</code></em></code>] [<code class="option">-P <em class="replaceable"><code>port</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-s</code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-u <em class="replaceable"><code>user</code></em></code>] [<code class="option">-v</code>] [<code class="option">-4</code>] [<code class="option">-6</code>]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2660187"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">lwresd</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">lwresd</code>
+ [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>]
+ [<code class="option">-C <em class="replaceable"><code>config-file</code></em></code>]
+ [<code class="option">-d <em class="replaceable"><code>debug-level</code></em></code>]
+ [<code class="option">-f</code>]
+ [<code class="option">-g</code>]
+ [<code class="option">-i <em class="replaceable"><code>pid-file</code></em></code>]
+ [<code class="option">-m <em class="replaceable"><code>flag</code></em></code>]
+ [<code class="option">-n <em class="replaceable"><code>#cpus</code></em></code>]
+ [<code class="option">-P <em class="replaceable"><code>port</code></em></code>]
+ [<code class="option">-p <em class="replaceable"><code>port</code></em></code>]
+ [<code class="option">-s</code>]
+ [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-u <em class="replaceable"><code>user</code></em></code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-4</code>]
+ [<code class="option">-6</code>]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.15.7"></a><h2>DESCRIPTION</h2>
+
+
+ <p><span class="command"><strong>lwresd</strong></span>
is the daemon providing name lookup
services to clients that use the BIND 9 lightweight resolver
library. It is essentially a stripped-down, caching-only name
server that answers queries using the BIND 9 lightweight
resolver protocol rather than the DNS protocol.
</p>
-<p><span><strong class="command">lwresd</strong></span>
+
+ <p><span class="command"><strong>lwresd</strong></span>
listens for resolver queries on a
UDP port on the IPv4 loopback interface, 127.0.0.1. This
- means that <span><strong class="command">lwresd</strong></span> can only be used by
+ means that <span class="command"><strong>lwresd</strong></span> can only be used by
processes running on the local machine. By default, UDP port
number 921 is used for lightweight resolver requests and
responses.
</p>
-<p>
Incoming lightweight resolver requests are decoded by the
server which then resolves them using the DNS protocol. When
- the DNS lookup completes, <span><strong class="command">lwresd</strong></span> encodes
+ the DNS lookup completes, <span class="command"><strong>lwresd</strong></span> encodes
the answers in the lightweight resolver format and returns
them to the client that made the request.
</p>
-<p>
If <code class="filename">/etc/resolv.conf</code> contains any
- <code class="option">nameserver</code> entries, <span><strong class="command">lwresd</strong></span>
+ <code class="option">nameserver</code> entries, <span class="command"><strong>lwresd</strong></span>
sends recursive DNS queries to those servers. This is similar
to the use of forwarders in a caching name server. If no
<code class="option">nameserver</code> entries are present, or if
- forwarding fails, <span><strong class="command">lwresd</strong></span> resolves the
+ forwarding fails, <span class="command"><strong>lwresd</strong></span> resolves the
queries autonomously starting at the root name servers, using
a built-in list of root server hints.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2660249"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.15.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-4</span></dt>
-<dd><p>
+<dd>
+ <p>
Use IPv4 only even if the host machine is capable of IPv6.
<code class="option">-4</code> and <code class="option">-6</code> are mutually
exclusive.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-6</span></dt>
-<dd><p>
+<dd>
+ <p>
Use IPv6 only even if the host machine is capable of IPv4.
<code class="option">-4</code> and <code class="option">-6</code> are mutually
exclusive.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>config-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>config-file</code></em> as the
configuration file instead of the default,
<code class="filename">/etc/lwresd.conf</code>.
<code class="option">-c</code> can not be used with <code class="option">-C</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-C <em class="replaceable"><code>config-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>config-file</code></em> as the
configuration file instead of the default,
<code class="filename">/etc/resolv.conf</code>.
<code class="option">-C</code> can not be used with <code class="option">-c</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-d <em class="replaceable"><code>debug-level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the daemon's debug level to <em class="replaceable"><code>debug-level</code></em>.
- Debugging traces from <span><strong class="command">lwresd</strong></span> become
+ Debugging traces from <span class="command"><strong>lwresd</strong></span> become
more verbose as the debug level increases.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-f</span></dt>
-<dd><p>
+<dd>
+ <p>
Run the server in the foreground (i.e. do not daemonize).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-g</span></dt>
-<dd><p>
+<dd>
+ <p>
Run the server in the foreground and force all logging
to <code class="filename">stderr</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-i <em class="replaceable"><code>pid-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>pid-file</code></em> as the
PID file instead of the default,
<code class="filename">/var/run/lwresd/lwresd.pid</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-m <em class="replaceable"><code>flag</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Turn on memory usage debugging flags. Possible flags are
<em class="replaceable"><code>usage</code></em>,
<em class="replaceable"><code>trace</code></em>,
<em class="replaceable"><code>mctx</code></em>.
These correspond to the ISC_MEM_DEBUGXXXX flags described in
<code class="filename"><isc/mem.h></code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-n <em class="replaceable"><code>#cpus</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Create <em class="replaceable"><code>#cpus</code></em> worker threads
to take advantage of multiple CPUs. If not specified,
- <span><strong class="command">lwresd</strong></span> will try to determine the
+ <span class="command"><strong>lwresd</strong></span> will try to determine the
number of CPUs present and create one thread per CPU.
If it is unable to determine the number of CPUs, a
single worker thread will be created.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-P <em class="replaceable"><code>port</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Listen for lightweight resolver queries on port
<em class="replaceable"><code>port</code></em>. If
not specified, the default is port 921.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Send DNS lookups to port <em class="replaceable"><code>port</code></em>. If not
specified, the default is port 53. This provides a
way of testing the lightweight resolver daemon with a
name server that listens for queries on a non-standard
port number.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s</span></dt>
<dd>
-<p>
Write memory usage statistics to <code class="filename">stdout</code>
on exit.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
This option is mainly of interest to BIND 9 developers
and may be removed or changed in a future release.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>directory</code></em></span></dt>
<dd>
-<p>Chroot
to <em class="replaceable"><code>directory</code></em> after
processing the command line arguments, but before
reading the configuration file.
</p>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Warning</h3>
-<p>
This option should be used in conjunction with the
<code class="option">-u</code> option, as chrooting a process
running as root doesn't enhance security on most
defined allows a process with root privileges to
escape a chroot jail.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
<dt><span class="term">-u <em class="replaceable"><code>user</code></em></span></dt>
-<dd><p>Setuid
+<dd>
+ <p>Setuid
to <em class="replaceable"><code>user</code></em> after completing
privileged operations, such as creating sockets that
listen on privileged ports.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v</span></dt>
-<dd><p>
+<dd>
+ <p>
Report the version number and exit.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2661095"></a><h2>FILES</h2>
-<div class="variablelist"><dl>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.15.9"></a><h2>FILES</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="filename">/etc/resolv.conf</code></span></dt>
-<dd><p>
+<dd>
+ <p>
The default configuration file.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="filename">/var/run/lwresd.pid</code></span></dt>
-<dd><p>
+<dd>
+ <p>
The default process-id file.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2664279"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">lwres</span>(3)</span>,
- <span class="citerefentry"><span class="refentrytitle">resolver</span>(5)</span>.
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.15.10"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">lwres</span>(3)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">resolver</span>(5)
+ </span>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2664313"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
-<a accesskey="p" href="man.named.conf.html">Prev</a> </td>
+<a accesskey="p" href="man.dnssec-verify.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
-<td width="40%" align="right"> <a accesskey="n" href="man.named-journalprint.html">Next</a>
+<td width="40%" align="right"> <a accesskey="n" href="man.named.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
-<code class="filename">named.conf</code> </td>
+<span class="application">dnssec-verify</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
-<td width="40%" align="right" valign="top"> <span class="application">named-journalprint</span>
+<td width="40%" align="right" valign="top"> <span class="application">named</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-checkconf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
-<link rel="prev" href="man.dnssec-verify.html" title="dnssec-verify">
+<link rel="prev" href="man.named.conf.html" title="named.conf">
<link rel="next" href="man.named-checkzone.html" title="named-checkzone">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<tr><th colspan="3" align="center"><span class="application">named-checkconf</span></th></tr>
<tr>
<td width="20%" align="left">
-<a accesskey="p" href="man.dnssec-verify.html">Prev</a> </td>
+<a accesskey="p" href="man.named.conf.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right"> <a accesskey="n" href="man.named-checkzone.html">Next</a>
</td>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.named-checkconf"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">named-checkconf</span> — named configuration file syntax checking tool</p>
+<p>
+ <span class="application">named-checkconf</span>
+ — named configuration file syntax checking tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">named-checkconf</code> [<code class="option">-h</code>] [<code class="option">-v</code>] [<code class="option">-j</code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] {filename} [<code class="option">-p</code>] [<code class="option">-x</code>] [<code class="option">-z</code>]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2647314"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">named-checkconf</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named-checkconf</code>
+ [<code class="option">-h</code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-j</code>]
+ [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>]
+ {filename}
+ [<code class="option">-p</code>]
+ [<code class="option">-x</code>]
+ [<code class="option">-z</code>]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.18.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>named-checkconf</strong></span>
checks the syntax, but not the semantics, of a
- <span><strong class="command">named</strong></span> configuration file. The file is parsed
+ <span class="command"><strong>named</strong></span> configuration file. The file is parsed
and checked for syntax errors, along with all files included by it.
If no file is specified, <code class="filename">/etc/named.conf</code> is read
by default.
</p>
-<p>
- Note: files that <span><strong class="command">named</strong></span> reads in separate
+ Note: files that <span class="command"><strong>named</strong></span> reads in separate
parser contexts, such as <code class="filename">rndc.key</code> and
<code class="filename">bind.keys</code>, are not automatically read
- by <span><strong class="command">named-checkconf</strong></span>. Configuration
- errors in these files may cause <span><strong class="command">named</strong></span> to
- fail to run, even if <span><strong class="command">named-checkconf</strong></span> was
- successful. <span><strong class="command">named-checkconf</strong></span> can be run
+ by <span class="command"><strong>named-checkconf</strong></span>. Configuration
+ errors in these files may cause <span class="command"><strong>named</strong></span> to
+ fail to run, even if <span class="command"><strong>named-checkconf</strong></span> was
+ successful. <span class="command"><strong>named-checkconf</strong></span> can be run
on these files explicitly, however.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2647384"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.18.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Print the usage summary and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Chroot to <code class="filename">directory</code> so that include
directives in the configuration file are processed as if
- run by a similarly chrooted <span><strong class="command">named</strong></span>.
- </p></dd>
+ run by a similarly chrooted <span class="command"><strong>named</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-v</span></dt>
-<dd><p>
- Print the version of the <span><strong class="command">named-checkconf</strong></span>
+<dd>
+ <p>
+ Print the version of the <span class="command"><strong>named-checkconf</strong></span>
program and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p</span></dt>
-<dd><p>
+<dd>
+ <p>
Print out the <code class="filename">named.conf</code> and included files
in canonical form if no errors were detected.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-x</span></dt>
-<dd><p>
+<dd>
+ <p>
When printing the configuration files in canonical
form, obscure shared secrets by replacing them with
strings of question marks ('?'). This allows the
files to be shared — for example, when submitting
bug reports — without compromising private data.
This option cannot be used without <code class="option">-p</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-z</span></dt>
-<dd><p>
+<dd>
+ <p>
Perform a test load of all master zones found in
<code class="filename">named.conf</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-j</span></dt>
-<dd><p>
+<dd>
+ <p>
When loading a zonefile read the journal if it exists.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">filename</span></dt>
-<dd><p>
+<dd>
+ <p>
The name of the configuration file to be checked. If not
specified, it defaults to <code class="filename">/etc/named.conf</code>.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2648091"></a><h2>RETURN VALUES</h2>
-<p><span><strong class="command">named-checkconf</strong></span>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.18.9"></a><h2>RETURN VALUES</h2>
+
+ <p><span class="command"><strong>named-checkconf</strong></span>
returns an exit status of 1 if
errors were detected and 0 otherwise.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2648105"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">named-checkzone</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.18.10"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named-checkzone</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2648135"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
-<a accesskey="p" href="man.dnssec-verify.html">Prev</a> </td>
+<a accesskey="p" href="man.named.conf.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="man.named-checkzone.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
-<span class="application">dnssec-verify</span> </td>
+<code class="filename">named.conf</code> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top"> <span class="application">named-checkzone</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-checkzone</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-checkconf.html" title="named-checkconf">
-<link rel="next" href="man.named.html" title="named">
+<link rel="next" href="man.named-journalprint.html" title="named-journalprint">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<td width="20%" align="left">
<a accesskey="p" href="man.named-checkconf.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
-<td width="20%" align="right"> <a accesskey="n" href="man.named.html">Next</a>
+<td width="20%" align="right"> <a accesskey="n" href="man.named-journalprint.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.named-checkzone"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">named-checkzone</span>, <span class="application">named-compilezone</span> — zone file validity checking or converting tool</p>
+<p>
+ <span class="application">named-checkzone</span>,
+ <span class="application">named-compilezone</span>
+ — zone file validity checking or converting tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">named-checkzone</code> [<code class="option">-d</code>] [<code class="option">-h</code>] [<code class="option">-j</code>] [<code class="option">-q</code>] [<code class="option">-v</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-f <em class="replaceable"><code>format</code></em></code>] [<code class="option">-F <em class="replaceable"><code>format</code></em></code>] [<code class="option">-J <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-i <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-k <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-m <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-M <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-n <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-l <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>] [<code class="option">-o <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-r <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-s <em class="replaceable"><code>style</code></em></code>] [<code class="option">-S <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-T <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-w <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-D</code>] [<code class="option">-W <em class="replaceable"><code>mode</code></em></code>] {zonename} {filename}</p></div>
-<div class="cmdsynopsis"><p><code class="command">named-compilezone</code> [<code class="option">-d</code>] [<code class="option">-j</code>] [<code class="option">-q</code>] [<code class="option">-v</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-C <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-f <em class="replaceable"><code>format</code></em></code>] [<code class="option">-F <em class="replaceable"><code>format</code></em></code>] [<code class="option">-J <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-i <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-k <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-m <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-n <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-l <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>] [<code class="option">-r <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-s <em class="replaceable"><code>style</code></em></code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-T <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-w <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-D</code>] [<code class="option">-W <em class="replaceable"><code>mode</code></em></code>] {<code class="option">-o <em class="replaceable"><code>filename</code></em></code>} {zonename} {filename}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2679184"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">named-checkzone</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named-checkzone</code>
+ [<code class="option">-d</code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-j</code>]
+ [<code class="option">-q</code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>format</code></em></code>]
+ [<code class="option">-F <em class="replaceable"><code>format</code></em></code>]
+ [<code class="option">-J <em class="replaceable"><code>filename</code></em></code>]
+ [<code class="option">-i <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-k <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-m <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-M <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-n <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-l <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>]
+ [<code class="option">-o <em class="replaceable"><code>filename</code></em></code>]
+ [<code class="option">-r <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-s <em class="replaceable"><code>style</code></em></code>]
+ [<code class="option">-S <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-T <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-w <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-D</code>]
+ [<code class="option">-W <em class="replaceable"><code>mode</code></em></code>]
+ {zonename}
+ {filename}
+ </p></div>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named-compilezone</code>
+ [<code class="option">-d</code>]
+ [<code class="option">-j</code>]
+ [<code class="option">-q</code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
+ [<code class="option">-C <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-f <em class="replaceable"><code>format</code></em></code>]
+ [<code class="option">-F <em class="replaceable"><code>format</code></em></code>]
+ [<code class="option">-J <em class="replaceable"><code>filename</code></em></code>]
+ [<code class="option">-i <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-k <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-m <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-n <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-l <em class="replaceable"><code>ttl</code></em></code>]
+ [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>]
+ [<code class="option">-r <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-s <em class="replaceable"><code>style</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-T <em class="replaceable"><code>mode</code></em></code>]
+ [<code class="option">-w <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-D</code>]
+ [<code class="option">-W <em class="replaceable"><code>mode</code></em></code>]
+ {<code class="option">-o <em class="replaceable"><code>filename</code></em></code>}
+ {zonename}
+ {filename}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.19.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>named-checkzone</strong></span>
checks the syntax and integrity of a zone file. It performs the
- same checks as <span><strong class="command">named</strong></span> does when loading a
- zone. This makes <span><strong class="command">named-checkzone</strong></span> useful for
+ same checks as <span class="command"><strong>named</strong></span> does when loading a
+ zone. This makes <span class="command"><strong>named-checkzone</strong></span> useful for
checking zone files before configuring them into a name server.
</p>
-<p>
- <span><strong class="command">named-compilezone</strong></span> is similar to
- <span><strong class="command">named-checkzone</strong></span>, but it always dumps the
+ <span class="command"><strong>named-compilezone</strong></span> is similar to
+ <span class="command"><strong>named-checkzone</strong></span>, but it always dumps the
zone contents to a specified file in a specified format.
Additionally, it applies stricter check levels by default,
since the dump output will be used as an actual zone file
- loaded by <span><strong class="command">named</strong></span>.
+ loaded by <span class="command"><strong>named</strong></span>.
When manually specified otherwise, the check levels must at
least be as strict as those specified in the
- <span><strong class="command">named</strong></span> configuration file.
+ <span class="command"><strong>named</strong></span> configuration file.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2679234"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.19.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-d</span></dt>
-<dd><p>
+<dd>
+ <p>
Enable debugging.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Print the usage summary and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-q</span></dt>
-<dd><p>
+<dd>
+ <p>
Quiet mode - exit code only.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v</span></dt>
-<dd><p>
- Print the version of the <span><strong class="command">named-checkzone</strong></span>
+<dd>
+ <p>
+ Print the version of the <span class="command"><strong>named-checkzone</strong></span>
program and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-j</span></dt>
-<dd><p>
+<dd>
+ <p>
When loading a zone file, read the journal if it exists.
The journal file name is assumed to be the zone file name
appended with the string <code class="filename">.jnl</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-J <em class="replaceable"><code>filename</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
When loading the zone file read the journal from the given
file, if it exists. (Implies -j.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the class of the zone. If not specified, "IN" is assumed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-i <em class="replaceable"><code>mode</code></em></span></dt>
<dd>
-<p>
Perform post-load zone integrity checks. Possible modes are
- <span><strong class="command">"full"</strong></span> (default),
- <span><strong class="command">"full-sibling"</strong></span>,
- <span><strong class="command">"local"</strong></span>,
- <span><strong class="command">"local-sibling"</strong></span> and
- <span><strong class="command">"none"</strong></span>.
+ <span class="command"><strong>"full"</strong></span> (default),
+ <span class="command"><strong>"full-sibling"</strong></span>,
+ <span class="command"><strong>"local"</strong></span>,
+ <span class="command"><strong>"local-sibling"</strong></span> and
+ <span class="command"><strong>"none"</strong></span>.
</p>
-<p>
- Mode <span><strong class="command">"full"</strong></span> checks that MX records
+ Mode <span class="command"><strong>"full"</strong></span> checks that MX records
refer to A or AAAA record (both in-zone and out-of-zone
- hostnames). Mode <span><strong class="command">"local"</strong></span> only
+ hostnames). Mode <span class="command"><strong>"local"</strong></span> only
checks MX records which refer to in-zone hostnames.
</p>
-<p>
- Mode <span><strong class="command">"full"</strong></span> checks that SRV records
+ Mode <span class="command"><strong>"full"</strong></span> checks that SRV records
refer to A or AAAA record (both in-zone and out-of-zone
- hostnames). Mode <span><strong class="command">"local"</strong></span> only
+ hostnames). Mode <span class="command"><strong>"local"</strong></span> only
checks SRV records which refer to in-zone hostnames.
</p>
-<p>
- Mode <span><strong class="command">"full"</strong></span> checks that delegation NS
+ Mode <span class="command"><strong>"full"</strong></span> checks that delegation NS
records refer to A or AAAA record (both in-zone and out-of-zone
hostnames). It also checks that glue address records
in the zone match those advertised by the child.
- Mode <span><strong class="command">"local"</strong></span> only checks NS records which
+ Mode <span class="command"><strong>"local"</strong></span> only checks NS records which
refer to in-zone hostnames or that some required glue exists,
that is when the nameserver is in a child zone.
</p>
-<p>
- Mode <span><strong class="command">"full-sibling"</strong></span> and
- <span><strong class="command">"local-sibling"</strong></span> disable sibling glue
- checks but are otherwise the same as <span><strong class="command">"full"</strong></span>
- and <span><strong class="command">"local"</strong></span> respectively.
+ Mode <span class="command"><strong>"full-sibling"</strong></span> and
+ <span class="command"><strong>"local-sibling"</strong></span> disable sibling glue
+ checks but are otherwise the same as <span class="command"><strong>"full"</strong></span>
+ and <span class="command"><strong>"local"</strong></span> respectively.
</p>
-<p>
- Mode <span><strong class="command">"none"</strong></span> disables the checks.
+ Mode <span class="command"><strong>"none"</strong></span> disables the checks.
</p>
-</dd>
+ </dd>
<dt><span class="term">-f <em class="replaceable"><code>format</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the format of the zone file.
- Possible formats are <span><strong class="command">"text"</strong></span> (default),
- <span><strong class="command">"raw"</strong></span>, and <span><strong class="command">"map"</strong></span>.
- </p></dd>
+ Possible formats are <span class="command"><strong>"text"</strong></span> (default),
+ <span class="command"><strong>"raw"</strong></span>, and <span class="command"><strong>"map"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-F <em class="replaceable"><code>format</code></em></span></dt>
<dd>
-<p>
Specify the format of the output file specified.
- For <span><strong class="command">named-checkzone</strong></span>,
+ For <span class="command"><strong>named-checkzone</strong></span>,
this does not cause any effects unless it dumps the zone
contents.
</p>
-<p>
- Possible formats are <span><strong class="command">"text"</strong></span> (default),
+ Possible formats are <span class="command"><strong>"text"</strong></span> (default),
which is the standard textual representation of the zone,
- and <span><strong class="command">"map"</strong></span>, <span><strong class="command">"raw"</strong></span>,
- and <span><strong class="command">"raw=N"</strong></span>, which store the zone in a
- binary format for rapid loading by <span><strong class="command">named</strong></span>.
- <span><strong class="command">"raw=N"</strong></span> specifies the format version of
+ and <span class="command"><strong>"map"</strong></span>, <span class="command"><strong>"raw"</strong></span>,
+ and <span class="command"><strong>"raw=N"</strong></span>, which store the zone in a
+ binary format for rapid loading by <span class="command"><strong>named</strong></span>.
+ <span class="command"><strong>"raw=N"</strong></span> specifies the format version of
the raw zone file: if N is 0, the raw file can be read by
- any version of <span><strong class="command">named</strong></span>; if N is 1, the file
+ any version of <span class="command"><strong>named</strong></span>; if N is 1, the file
can be read by release 9.9.0 or higher; the default is 1.
</p>
-</dd>
+ </dd>
<dt><span class="term">-k <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
- Perform <span><strong class="command">"check-names"</strong></span> checks with the
+<dd>
+ <p>
+ Perform <span class="command"><strong>"check-names"</strong></span> checks with the
specified failure mode.
- Possible modes are <span><strong class="command">"fail"</strong></span>
- (default for <span><strong class="command">named-compilezone</strong></span>),
- <span><strong class="command">"warn"</strong></span>
- (default for <span><strong class="command">named-checkzone</strong></span>) and
- <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ Possible modes are <span class="command"><strong>"fail"</strong></span>
+ (default for <span class="command"><strong>named-compilezone</strong></span>),
+ <span class="command"><strong>"warn"</strong></span>
+ (default for <span class="command"><strong>named-checkzone</strong></span>) and
+ <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-l <em class="replaceable"><code>ttl</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Sets a maximum permissible TTL for the input file.
Any record with a TTL higher than this value will cause
the zone to be rejected. This is similar to using the
- <span><strong class="command">max-zone-ttl</strong></span> option in
+ <span class="command"><strong>max-zone-ttl</strong></span> option in
<code class="filename">named.conf</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>serial</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
When compiling a zone to "raw" or "map" format, set the
"source serial" value in the header to the specified serial
number. (This is expected to be used primarily for testing
purposes.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-m <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify whether MX records should be checked to see if they
- are addresses. Possible modes are <span><strong class="command">"fail"</strong></span>,
- <span><strong class="command">"warn"</strong></span> (default) and
- <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ are addresses. Possible modes are <span class="command"><strong>"fail"</strong></span>,
+ <span class="command"><strong>"warn"</strong></span> (default) and
+ <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-M <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Check if a MX record refers to a CNAME.
- Possible modes are <span><strong class="command">"fail"</strong></span>,
- <span><strong class="command">"warn"</strong></span> (default) and
- <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ Possible modes are <span class="command"><strong>"fail"</strong></span>,
+ <span class="command"><strong>"warn"</strong></span> (default) and
+ <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-n <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify whether NS records should be checked to see if they
are addresses.
- Possible modes are <span><strong class="command">"fail"</strong></span>
- (default for <span><strong class="command">named-compilezone</strong></span>),
- <span><strong class="command">"warn"</strong></span>
- (default for <span><strong class="command">named-checkzone</strong></span>) and
- <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ Possible modes are <span class="command"><strong>"fail"</strong></span>
+ (default for <span class="command"><strong>named-compilezone</strong></span>),
+ <span class="command"><strong>"warn"</strong></span>
+ (default for <span class="command"><strong>named-checkzone</strong></span>) and
+ <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-o <em class="replaceable"><code>filename</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Write zone output to <code class="filename">filename</code>.
If <code class="filename">filename</code> is <code class="filename">-</code> then
write to standard out.
- This is mandatory for <span><strong class="command">named-compilezone</strong></span>.
- </p></dd>
+ This is mandatory for <span class="command"><strong>named-compilezone</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-r <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Check for records that are treated as different by DNSSEC but
are semantically equal in plain DNS.
- Possible modes are <span><strong class="command">"fail"</strong></span>,
- <span><strong class="command">"warn"</strong></span> (default) and
- <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ Possible modes are <span class="command"><strong>"fail"</strong></span>,
+ <span class="command"><strong>"warn"</strong></span> (default) and
+ <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-s <em class="replaceable"><code>style</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the style of the dumped zone file.
- Possible styles are <span><strong class="command">"full"</strong></span> (default)
- and <span><strong class="command">"relative"</strong></span>.
+ Possible styles are <span class="command"><strong>"full"</strong></span> (default)
+ and <span class="command"><strong>"relative"</strong></span>.
The full format is most suitable for processing
automatically by a separate script.
On the other hand, the relative format is more
human-readable and is thus suitable for editing by hand.
- For <span><strong class="command">named-checkzone</strong></span>
+ For <span class="command"><strong>named-checkzone</strong></span>
this does not cause any effects unless it dumps the zone
contents.
It also does not have any meaning if the output format
is not text.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-S <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Check if a SRV record refers to a CNAME.
- Possible modes are <span><strong class="command">"fail"</strong></span>,
- <span><strong class="command">"warn"</strong></span> (default) and
- <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ Possible modes are <span class="command"><strong>"fail"</strong></span>,
+ <span class="command"><strong>"warn"</strong></span> (default) and
+ <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Chroot to <code class="filename">directory</code> so that
include
directives in the configuration file are processed as if
- run by a similarly chrooted <span><strong class="command">named</strong></span>.
- </p></dd>
+ run by a similarly chrooted <span class="command"><strong>named</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-T <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Check if Sender Policy Framework (SPF) records exist
and issues a warning if an SPF-formatted TXT record is
- not also present. Possible modes are <span><strong class="command">"warn"</strong></span>
- (default), <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ not also present. Possible modes are <span class="command"><strong>"warn"</strong></span>
+ (default), <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-w <em class="replaceable"><code>directory</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
chdir to <code class="filename">directory</code> so that
relative
filenames in master file $INCLUDE directives work. This
is similar to the directory clause in
<code class="filename">named.conf</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D</span></dt>
-<dd><p>
+<dd>
+ <p>
Dump zone file in canonical format.
- This is always enabled for <span><strong class="command">named-compilezone</strong></span>.
- </p></dd>
+ This is always enabled for <span class="command"><strong>named-compilezone</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-W <em class="replaceable"><code>mode</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specify whether to check for non-terminal wildcards.
Non-terminal wildcards are almost always the result of a
failure to understand the wildcard matching algorithm (RFC 1034).
- Possible modes are <span><strong class="command">"warn"</strong></span> (default)
+ Possible modes are <span class="command"><strong>"warn"</strong></span> (default)
and
- <span><strong class="command">"ignore"</strong></span>.
- </p></dd>
+ <span class="command"><strong>"ignore"</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">zonename</span></dt>
-<dd><p>
+<dd>
+ <p>
The domain name of the zone being checked.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">filename</span></dt>
-<dd><p>
+<dd>
+ <p>
The name of the zone file.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2680140"></a><h2>RETURN VALUES</h2>
-<p><span><strong class="command">named-checkzone</strong></span>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.19.9"></a><h2>RETURN VALUES</h2>
+
+ <p><span class="command"><strong>named-checkzone</strong></span>
returns an exit status of 1 if
errors were detected and 0 otherwise.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2680222"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">named-checkconf</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.19.10"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named-checkconf</span>(8)
+ </span>,
<em class="citetitle">RFC 1035</em>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2680256"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<td width="40%" align="left">
<a accesskey="p" href="man.named-checkconf.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
-<td width="40%" align="right"> <a accesskey="n" href="man.named.html">Next</a>
+<td width="40%" align="right"> <a accesskey="n" href="man.named-journalprint.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">named-checkconf</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
-<td width="40%" align="right" valign="top"> <span class="application">named</span>
+<td width="40%" align="right" valign="top"> <span class="application">named-journalprint</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-journalprint</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
-<link rel="prev" href="man.isc-hmac-fixup.html" title="isc-hmac-fixup">
+<link rel="prev" href="man.named-checkzone.html" title="named-checkzone">
<link rel="next" href="man.named-rrchecker.html" title="named-rrchecker">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<tr><th colspan="3" align="center"><span class="application">named-journalprint</span></th></tr>
<tr>
<td width="20%" align="left">
-<a accesskey="p" href="man.isc-hmac-fixup.html">Prev</a> </td>
+<a accesskey="p" href="man.named-checkzone.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right"> <a accesskey="n" href="man.named-rrchecker.html">Next</a>
</td>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.named-journalprint"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">named-journalprint</span> — print zone journal in human-readable form</p>
+<p>
+ <span class="application">named-journalprint</span>
+ — print zone journal in human-readable form
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">named-journalprint</code> {<em class="replaceable"><code>journal</code></em>}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2718420"></a><h2>DESCRIPTION</h2>
-<p>
- <span><strong class="command">named-journalprint</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named-journalprint</code>
+ {<em class="replaceable"><code>journal</code></em>}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.20.7"></a><h2>DESCRIPTION</h2>
+
+ <p>
+ <span class="command"><strong>named-journalprint</strong></span>
prints the contents of a zone journal file in a human-readable
form.
</p>
-<p>
- Journal files are automatically created by <span><strong class="command">named</strong></span>
+ Journal files are automatically created by <span class="command"><strong>named</strong></span>
when changes are made to dynamic zones (e.g., by
- <span><strong class="command">nsupdate</strong></span>). They record each addition
+ <span class="command"><strong>nsupdate</strong></span>). They record each addition
or deletion of a resource record, in binary format, allowing the
changes to be re-applied to the zone when the server is
restarted after a shutdown or crash. By default, the name of
<code class="filename">.jnl</code> to the name of the corresponding
zone file.
</p>
-<p>
- <span><strong class="command">named-journalprint</strong></span> converts the contents of a given
+ <span class="command"><strong>named-journalprint</strong></span> converts the contents of a given
journal file into a human-readable text format. Each line begins
with "add" or "del", to indicate whether the record was added or
deleted, and continues with the resource record in master-file
format.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745587"></a><h2>SEE ALSO</h2>
-<p>
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">nsupdate</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.20.8"></a><h2>SEE ALSO</h2>
+
+ <p>
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">nsupdate</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745650"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
-<a accesskey="p" href="man.isc-hmac-fixup.html">Prev</a> </td>
+<a accesskey="p" href="man.named-checkzone.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="man.named-rrchecker.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
-<span class="application">isc-hmac-fixup</span> </td>
+<span class="application">named-checkzone</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top"> <span class="application">named-rrchecker</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-rrchecker</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-journalprint.html" title="named-journalprint">
-<link rel="next" href="man.nsec3hash.html" title="nsec3hash">
+<link rel="next" href="man.nsupdate.html" title="nsupdate">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<td width="20%" align="left">
<a accesskey="p" href="man.named-journalprint.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
-<td width="20%" align="right"> <a accesskey="n" href="man.nsec3hash.html">Next</a>
+<td width="20%" align="right"> <a accesskey="n" href="man.nsupdate.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.named-rrchecker"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">named-rrchecker</span> — A syntax checker for individual DNS resource records</p>
+<p>
+ <span class="application">named-rrchecker</span>
+ — A syntax checker for individual DNS resource records
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">named-rrchecker</code> [<code class="option">-h</code>] [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>] [<code class="option">-p</code>] [<code class="option">-u</code>] [<code class="option">-C</code>] [<code class="option">-T</code>] [<code class="option">-P</code>]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746265"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">named-rrchecker</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named-rrchecker</code>
+ [<code class="option">-h</code>]
+ [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>]
+ [<code class="option">-p</code>]
+ [<code class="option">-u</code>]
+ [<code class="option">-C</code>]
+ [<code class="option">-T</code>]
+ [<code class="option">-P</code>]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.21.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>named-rrchecker</strong></span>
read a individual DNS resource record from standard input and checks if it
is syntactically correct.
</p>
-<p>
The <code class="option">-h</code> prints out the help menu.
</p>
-<p>
The <code class="option">-o <em class="replaceable"><code>origin</code></em></code>
option specifies a origin to be used when interpreting the record.
</p>
-<p>
The <code class="option">-p</code> prints out the resulting record in canonical
form. If there is no canonical form defined then the record will be
printed in unknown record format.
</p>
-<p>
The <code class="option">-u</code> prints out the resulting record in unknown record
form.
</p>
-<p>
The <code class="option">-C</code>, <code class="option">-T</code> and <code class="option">-P</code>
print out the known class, standard type and private type mnemonics
respectively.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746534"></a><h2>SEE ALSO</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.21.8"></a><h2>SEE ALSO</h2>
+
+ <p>
<em class="citetitle">RFC 1034</em>,
<em class="citetitle">RFC 1035</em>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>
</p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<td width="40%" align="left">
<a accesskey="p" href="man.named-journalprint.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
-<td width="40%" align="right"> <a accesskey="n" href="man.nsec3hash.html">Next</a>
+<td width="40%" align="right"> <a accesskey="n" href="man.nsupdate.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">named-journalprint</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
-<td width="40%" align="right" valign="top"> <span class="application">nsec3hash</span>
+<td width="40%" align="right" valign="top"> <span class="application">nsupdate</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named.conf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named.html" title="named">
-<link rel="next" href="man.lwresd.html" title="lwresd">
+<link rel="next" href="man.named-checkconf.html" title="named-checkconf">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<td width="20%" align="left">
<a accesskey="p" href="man.named.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
-<td width="20%" align="right"> <a accesskey="n" href="man.lwresd.html">Next</a>
+<td width="20%" align="right"> <a accesskey="n" href="man.named-checkconf.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.named.conf"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><code class="filename">named.conf</code> — configuration file for <span><strong class="command">named</strong></span></p>
+<p>
+ <code class="filename">named.conf</code>
+ — configuration file for <span class="command"><strong>named</strong></span>
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">named.conf</code> </p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2656756"></a><h2>DESCRIPTION</h2>
-<p><code class="filename">named.conf</code> is the configuration file
+ <div class="cmdsynopsis"><p>
+ <code class="command">named.conf</code>
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.7"></a><h2>DESCRIPTION</h2>
+
+ <p><code class="filename">named.conf</code> is the configuration file
for
- <span><strong class="command">named</strong></span>. Statements are enclosed
+ <span class="command"><strong>named</strong></span>. Statements are enclosed
in braces and terminated with a semi-colon. Clauses in
the statements are also semi-colon terminated. The usual
comment styles are supported:
</p>
-<p>
C style: /* */
</p>
-<p>
C++ style: // to end of line
</p>
-<p>
Unix style: # to end of line
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2656788"></a><h2>ACL</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.8"></a><h2>ACL</h2>
+
+ <div class="literallayout"><p><br>
acl <em class="replaceable"><code>string</code></em> { <em class="replaceable"><code>address_match_element</code></em>; ... };<br>
<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2656808"></a><h2>KEY</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.9"></a><h2>KEY</h2>
+
+ <div class="literallayout"><p><br>
key <em class="replaceable"><code>domain_name</code></em> {<br>
algorithm <em class="replaceable"><code>string</code></em>;<br>
secret <em class="replaceable"><code>string</code></em>;<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2656832"></a><h2>MASTERS</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.10"></a><h2>MASTERS</h2>
+
+ <div class="literallayout"><p><br>
masters <em class="replaceable"><code>string</code></em> [<span class="optional"> port <em class="replaceable"><code>integer</code></em> </span>] {<br>
( <em class="replaceable"><code>masters</code></em> | <em class="replaceable"><code>ipv4_address</code></em> [<span class="optional">port <em class="replaceable"><code>integer</code></em></span>] |<br>
<em class="replaceable"><code>ipv6_address</code></em> [<span class="optional">port <em class="replaceable"><code>integer</code></em></span>] ) [<span class="optional"> key <em class="replaceable"><code>string</code></em> </span>]; ...<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2656882"></a><h2>SERVER</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.11"></a><h2>SERVER</h2>
+
+ <div class="literallayout"><p><br>
server ( <em class="replaceable"><code>ipv4_address[<span class="optional">/prefixlen</span>]</code></em> | <em class="replaceable"><code>ipv6_address[<span class="optional">/prefixlen</span>]</code></em> ) {<br>
bogus <em class="replaceable"><code>boolean</code></em>;<br>
edns <em class="replaceable"><code>boolean</code></em>;<br>
support-ixfr <em class="replaceable"><code>boolean</code></em>; // obsolete<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2657299"></a><h2>TRUSTED-KEYS</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.12"></a><h2>TRUSTED-KEYS</h2>
+
+ <div class="literallayout"><p><br>
trusted-keys {<br>
<em class="replaceable"><code>domain_name</code></em> <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key</code></em>; ...<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2657329"></a><h2>MANAGED-KEYS</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.13"></a><h2>MANAGED-KEYS</h2>
+
+ <div class="literallayout"><p><br>
managed-keys {<br>
<em class="replaceable"><code>domain_name</code></em> <code class="constant">initial-key</code> <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key</code></em>; ...<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2657362"></a><h2>CONTROLS</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.14"></a><h2>CONTROLS</h2>
+
+ <div class="literallayout"><p><br>
controls {<br>
inet ( <em class="replaceable"><code>ipv4_address</code></em> | <em class="replaceable"><code>ipv6_address</code></em> | * )<br>
[<span class="optional"> port ( <em class="replaceable"><code>integer</code></em> | * ) </span>]<br>
unix <em class="replaceable"><code>unsupported</code></em>; // not implemented<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2657401"></a><h2>LOGGING</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.15"></a><h2>LOGGING</h2>
+
+ <div class="literallayout"><p><br>
logging {<br>
channel <em class="replaceable"><code>string</code></em> {<br>
file <em class="replaceable"><code>log_file</code></em>;<br>
category <em class="replaceable"><code>string</code></em> { <em class="replaceable"><code>string</code></em>; ... };<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2657444"></a><h2>LWRES</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.16"></a><h2>LWRES</h2>
+
+ <div class="literallayout"><p><br>
lwres {<br>
listen-on [<span class="optional"> port <em class="replaceable"><code>integer</code></em> </span>] {<br>
( <em class="replaceable"><code>ipv4_address</code></em> | <em class="replaceable"><code>ipv6_address</code></em> ) [<span class="optional"> port <em class="replaceable"><code>integer</code></em> </span>]; ...<br>
lwres-clients <em class="replaceable"><code>integer</code></em>;<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2659817"></a><h2>OPTIONS</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.17"></a><h2>OPTIONS</h2>
+
+ <div class="literallayout"><p><br>
options {<br>
avoid-v4-udp-ports { <em class="replaceable"><code>port</code></em>; ... };<br>
avoid-v6-udp-ports { <em class="replaceable"><code>port</code></em>; ... };<br>
use-id-pool <em class="replaceable"><code>boolean</code></em>; // obsolete<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2688312"></a><h2>VIEW</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.18"></a><h2>VIEW</h2>
+
+ <div class="literallayout"><p><br>
view <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>optional_class</code></em> {<br>
match-clients { <em class="replaceable"><code>address_match_element</code></em>; ... };<br>
match-destinations { <em class="replaceable"><code>address_match_element</code></em>; ... };<br>
max-ixfr-log-size <em class="replaceable"><code>size</code></em>; // obsolete<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2688980"></a><h2>ZONE</h2>
-<div class="literallayout"><p><br>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.19"></a><h2>ZONE</h2>
+
+ <div class="literallayout"><p><br>
zone <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>optional_class</code></em> {<br>
type ( master | slave | stub | hint | redirect |<br>
forward | delegation-only );<br>
pubkey <em class="replaceable"><code>integer</code></em> <em class="replaceable"><code>integer</code></em> <em class="replaceable"><code>integer</code></em> <em class="replaceable"><code>quoted_string</code></em>; // obsolete<br>
};<br>
</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2689305"></a><h2>FILES</h2>
-<p><code class="filename">/etc/named.conf</code>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.20"></a><h2>FILES</h2>
+
+ <p><code class="filename">/etc/named.conf</code>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2689319"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">named-checkconf</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.17.21"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named-checkconf</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">rndc</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<td width="40%" align="left">
<a accesskey="p" href="man.named.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
-<td width="40%" align="right"> <a accesskey="n" href="man.lwresd.html">Next</a>
+<td width="40%" align="right"> <a accesskey="n" href="man.named-checkconf.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">named</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
-<td width="40%" align="right" valign="top"> <span class="application">lwresd</span>
+<td width="40%" align="right" valign="top"> <span class="application">named-checkconf</span>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
-<link rel="prev" href="man.named-checkzone.html" title="named-checkzone">
+<link rel="prev" href="man.lwresd.html" title="lwresd">
<link rel="next" href="man.named.conf.html" title="named.conf">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<tr><th colspan="3" align="center"><span class="application">named</span></th></tr>
<tr>
<td width="20%" align="left">
-<a accesskey="p" href="man.named-checkzone.html">Prev</a> </td>
+<a accesskey="p" href="man.lwresd.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right"> <a accesskey="n" href="man.named.conf.html">Next</a>
</td>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.named"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">named</span> — Internet domain name server</p>
+<p>
+ <span class="application">named</span>
+ — Internet domain name server
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">named</code> [<code class="option">-4</code>] [<code class="option">-6</code>] [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-d <em class="replaceable"><code>debug-level</code></em></code>] [<code class="option">-D <em class="replaceable"><code>string</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine-name</code></em></code>] [<code class="option">-f</code>] [<code class="option">-g</code>] [<code class="option">-L <em class="replaceable"><code>logfile</code></em></code>] [<code class="option">-M <em class="replaceable"><code>option</code></em></code>] [<code class="option">-m <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-n <em class="replaceable"><code>#cpus</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-s</code>] [<code class="option">-S <em class="replaceable"><code>#max-socks</code></em></code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-U <em class="replaceable"><code>#listeners</code></em></code>] [<code class="option">-u <em class="replaceable"><code>user</code></em></code>] [<code class="option">-v</code>] [<code class="option">-V</code>] [<code class="option">-X <em class="replaceable"><code>lock-file</code></em></code>] [<code class="option">-x <em class="replaceable"><code>cache-file</code></em></code>]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2656041"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">named</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">named</code>
+ [<code class="option">-4</code>]
+ [<code class="option">-6</code>]
+ [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>]
+ [<code class="option">-d <em class="replaceable"><code>debug-level</code></em></code>]
+ [<code class="option">-D <em class="replaceable"><code>string</code></em></code>]
+ [<code class="option">-E <em class="replaceable"><code>engine-name</code></em></code>]
+ [<code class="option">-f</code>]
+ [<code class="option">-g</code>]
+ [<code class="option">-L <em class="replaceable"><code>logfile</code></em></code>]
+ [<code class="option">-M <em class="replaceable"><code>option</code></em></code>]
+ [<code class="option">-m <em class="replaceable"><code>flag</code></em></code>]
+ [<code class="option">-n <em class="replaceable"><code>#cpus</code></em></code>]
+ [<code class="option">-p <em class="replaceable"><code>port</code></em></code>]
+ [<code class="option">-s</code>]
+ [<code class="option">-S <em class="replaceable"><code>#max-socks</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>]
+ [<code class="option">-U <em class="replaceable"><code>#listeners</code></em></code>]
+ [<code class="option">-u <em class="replaceable"><code>user</code></em></code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-X <em class="replaceable"><code>lock-file</code></em></code>]
+ [<code class="option">-x <em class="replaceable"><code>cache-file</code></em></code>]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.16.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>named</strong></span>
is a Domain Name System (DNS) server,
part of the BIND 9 distribution from ISC. For more
information on the DNS, see RFCs 1033, 1034, and 1035.
</p>
-<p>
- When invoked without arguments, <span><strong class="command">named</strong></span>
+ When invoked without arguments, <span class="command"><strong>named</strong></span>
will
read the default configuration file
<code class="filename">/etc/named.conf</code>, read any initial
data, and listen for queries.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2656072"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.16.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-4</span></dt>
-<dd><p>
+<dd>
+ <p>
Use IPv4 only even if the host machine is capable of IPv6.
<code class="option">-4</code> and <code class="option">-6</code> are mutually
exclusive.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-6</span></dt>
-<dd><p>
+<dd>
+ <p>
Use IPv6 only even if the host machine is capable of IPv4.
<code class="option">-4</code> and <code class="option">-6</code> are mutually
exclusive.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>config-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>config-file</code></em> as the
configuration file instead of the default,
<code class="filename">/etc/named.conf</code>. To
<code class="option">directory</code> option in the configuration
file, <em class="replaceable"><code>config-file</code></em> should be
an absolute pathname.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-d <em class="replaceable"><code>debug-level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the daemon's debug level to <em class="replaceable"><code>debug-level</code></em>.
- Debugging traces from <span><strong class="command">named</strong></span> become
+ Debugging traces from <span class="command"><strong>named</strong></span> become
more verbose as the debug level increases.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D <em class="replaceable"><code>string</code></em></span></dt>
-<dd><p>
- Specifies a string that is used to identify a instance of
- <span><strong class="command">named</strong></span> in a process listing. The contents
- of <em class="replaceable"><code>string</code></em> are
- not examined.
- </p></dd>
+<dd>
+ <p>
+ Specifies a string that is used to identify a instance of
+ <span class="command"><strong>named</strong></span> in a process listing. The contents
+ of <em class="replaceable"><code>string</code></em> are
+ not examined.
+ </p>
+ </dd>
<dt><span class="term">-E <em class="replaceable"><code>engine-name</code></em></span></dt>
<dd>
-<p>
When applicable, specifies the hardware to use for
cryptographic operations, such as a secure key store used
for signing.
</p>
-<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
-</dd>
+ </dd>
<dt><span class="term">-f</span></dt>
-<dd><p>
+<dd>
+ <p>
Run the server in the foreground (i.e. do not daemonize).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-g</span></dt>
-<dd><p>
+<dd>
+ <p>
Run the server in the foreground and force all logging
to <code class="filename">stderr</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>logfile</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Log to the file <code class="option">logfile</code> by default
instead of the system log.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-M <em class="replaceable"><code>option</code></em></span></dt>
-<dd><p>
- Sets the default memory context options. Currently
- the only supported option is
- <em class="replaceable"><code>external</code></em>,
- which causes the internal memory manager to be bypassed
- in favor of system-provided memory allocation functions.
- </p></dd>
+<dd>
+ <p>
+ Sets the default memory context options. Currently
+ the only supported option is
+ <em class="replaceable"><code>external</code></em>,
+ which causes the internal memory manager to be bypassed
+ in favor of system-provided memory allocation functions.
+ </p>
+ </dd>
<dt><span class="term">-m <em class="replaceable"><code>flag</code></em></span></dt>
-<dd><p>
- Turn on memory usage debugging flags. Possible flags are
- <em class="replaceable"><code>usage</code></em>,
- <em class="replaceable"><code>trace</code></em>,
- <em class="replaceable"><code>record</code></em>,
- <em class="replaceable"><code>size</code></em>, and
- <em class="replaceable"><code>mctx</code></em>.
- These correspond to the ISC_MEM_DEBUGXXXX flags described in
- <code class="filename"><isc/mem.h></code>.
- </p></dd>
+<dd>
+ <p>
+ Turn on memory usage debugging flags. Possible flags are
+ <em class="replaceable"><code>usage</code></em>,
+ <em class="replaceable"><code>trace</code></em>,
+ <em class="replaceable"><code>record</code></em>,
+ <em class="replaceable"><code>size</code></em>, and
+ <em class="replaceable"><code>mctx</code></em>.
+ These correspond to the ISC_MEM_DEBUGXXXX flags described in
+ <code class="filename"><isc/mem.h></code>.
+ </p>
+ </dd>
<dt><span class="term">-n <em class="replaceable"><code>#cpus</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Create <em class="replaceable"><code>#cpus</code></em> worker threads
to take advantage of multiple CPUs. If not specified,
- <span><strong class="command">named</strong></span> will try to determine the
+ <span class="command"><strong>named</strong></span> will try to determine the
number of CPUs present and create one thread per CPU.
If it is unable to determine the number of CPUs, a
single worker thread will be created.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Listen for queries on port <em class="replaceable"><code>port</code></em>. If not
specified, the default is port 53.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s</span></dt>
<dd>
-<p>
Write memory usage statistics to <code class="filename">stdout</code> on exit.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
This option is mainly of interest to BIND 9 developers
and may be removed or changed in a future release.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
<dt><span class="term">-S <em class="replaceable"><code>#max-socks</code></em></span></dt>
<dd>
-<p>
- Allow <span><strong class="command">named</strong></span> to use up to
- <em class="replaceable"><code>#max-socks</code></em> sockets.
+ Allow <span class="command"><strong>named</strong></span> to use up to
+ <em class="replaceable"><code>#max-socks</code></em> sockets.
The default value is 4096 on systems built with default
configuration options, and 21000 on systems built with
"configure --with-tuning=large".
- </p>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
+ </p>
+
<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Warning</h3>
-<p>
This option should be unnecessary for the vast majority
of users.
- The use of this option could even be harmful because the
+ The use of this option could even be harmful because the
specified value may exceed the limitation of the
underlying system API.
- It is therefore set only when the default configuration
+ It is therefore set only when the default configuration
causes exhaustion of file descriptors and the
operational environment is known to support the
specified number of sockets.
- Note also that the actual maximum number is normally a little
+ Note also that the actual maximum number is normally a little
fewer than the specified value because
- <span><strong class="command">named</strong></span> reserves some file descriptors
- for its internal use.
+ <span class="command"><strong>named</strong></span> reserves some file descriptors
+ for its internal use.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>directory</code></em></span></dt>
<dd>
-<p>Chroot
- to <em class="replaceable"><code>directory</code></em> after
+ to <em class="replaceable"><code>directory</code></em> after
processing the command line arguments, but before
reading the configuration file.
</p>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Warning</h3>
-<p>
This option should be used in conjunction with the
<code class="option">-u</code> option, as chrooting a process
running as root doesn't enhance security on most
defined allows a process with root privileges to
escape a chroot jail.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
<dt><span class="term">-U <em class="replaceable"><code>#listeners</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>#listeners</code></em>
worker threads to listen for incoming UDP packets on each
- address. If not specified, <span><strong class="command">named</strong></span> will
+ address. If not specified, <span class="command"><strong>named</strong></span> will
calculate a default value based on the number of detected
- CPUs: 1 for 1 CPU, 2 for 2-4 CPUs, and the number of
- detected CPUs divided by 2 for values higher than 4.
+ CPUs: 1 for 1 CPU, and the number of detected CPUs
+ minus one for machines with more than 1 CPU. This cannot
+ be increased to a value higher than the number of CPUs.
If <code class="option">-n</code> has been set to a higher value than
the number of detected CPUs, then <code class="option">-U</code> may
be increased as high as that value, but no higher.
- </p></dd>
+ On Windows, the number of UDP listeners is hardwired to 1
+ and this option has no effect.
+ </p>
+ </dd>
<dt><span class="term">-u <em class="replaceable"><code>user</code></em></span></dt>
<dd>
-<p>Setuid
- to <em class="replaceable"><code>user</code></em> after completing
+ to <em class="replaceable"><code>user</code></em> after completing
privileged operations, such as creating sockets that
listen on privileged ports.
</p>
-<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
-<p>
- On Linux, <span><strong class="command">named</strong></span> uses the kernel's
- capability mechanism to drop all root privileges
+ On Linux, <span class="command"><strong>named</strong></span> uses the kernel's
+ capability mechanism to drop all root privileges
except the ability to <code class="function">bind(2)</code> to
a
privileged port and set process resource limits.
Unfortunately, this means that the <code class="option">-u</code>
- option only works when <span><strong class="command">named</strong></span> is
+ option only works when <span class="command"><strong>named</strong></span> is
run
on kernel 2.2.18 or later, or kernel 2.3.99-pre3 or
later, since previous kernels did not allow privileges
to be retained after <code class="function">setuid(2)</code>.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
<dt><span class="term">-v</span></dt>
-<dd><p>
+<dd>
+ <p>
Report the version number and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Report the version number and build options, and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-X <em class="replaceable"><code>lock-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Acquire a lock on the specified file at runtime; this
- helps to prevent duplicate <span><strong class="command">named</strong></span> instances
+ helps to prevent duplicate <span class="command"><strong>named</strong></span> instances
from running simultaneously.
- Use of this option overrides the <span><strong class="command">lock-file</strong></span>
+ Use of this option overrides the <span class="command"><strong>lock-file</strong></span>
option in <code class="filename">named.conf</code>.
If set to <code class="literal">none</code>, the lock file check
is disabled.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-x <em class="replaceable"><code>cache-file</code></em></span></dt>
<dd>
-<p>
Load data from <em class="replaceable"><code>cache-file</code></em> into the
cache of the default view.
</p>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
+
<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Warning</h3>
-<p>
This option must not be used. It is only of interest
to BIND 9 developers and may be removed or changed in a
future release.
</p>
-</div>
-</dd>
+ </div>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2687354"></a><h2>SIGNALS</h2>
-<p>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.16.9"></a><h2>SIGNALS</h2>
+
+ <p>
In routine operation, signals should not be used to control
- the nameserver; <span><strong class="command">rndc</strong></span> should be used
+ the nameserver; <span class="command"><strong>rndc</strong></span> should be used
instead.
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">SIGHUP</span></dt>
-<dd><p>
+<dd>
+ <p>
Force a reload of the server.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">SIGINT, SIGTERM</span></dt>
-<dd><p>
+<dd>
+ <p>
Shut down the server.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-<p>
+
+ <p>
The result of sending any other signals to the server is undefined.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2687404"></a><h2>CONFIGURATION</h2>
-<p>
- The <span><strong class="command">named</strong></span> configuration file is too complex
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.16.10"></a><h2>CONFIGURATION</h2>
+
+ <p>
+ The <span class="command"><strong>named</strong></span> configuration file is too complex
to describe in detail here. A complete description is provided
in the
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-<p>
- <span><strong class="command">named</strong></span> inherits the <code class="function">umask</code>
+
+ <p>
+ <span class="command"><strong>named</strong></span> inherits the <code class="function">umask</code>
(file creation mode mask) from the parent process. If files
- created by <span><strong class="command">named</strong></span>, such as journal files,
+ created by <span class="command"><strong>named</strong></span>, such as journal files,
need to have custom permissions, the <code class="function">umask</code>
should be set explicitly in the script used to start the
- <span><strong class="command">named</strong></span> process.
+ <span class="command"><strong>named</strong></span> process.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2687453"></a><h2>FILES</h2>
-<div class="variablelist"><dl>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.16.11"></a><h2>FILES</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="filename">/etc/named.conf</code></span></dt>
-<dd><p>
+<dd>
+ <p>
The default configuration file.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="filename">/var/run/named/named.pid</code></span></dt>
-<dd><p>
+<dd>
+ <p>
The default process-id file.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2687497"></a><h2>SEE ALSO</h2>
-<p><em class="citetitle">RFC 1033</em>,
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.16.12"></a><h2>SEE ALSO</h2>
+
+ <p><em class="citetitle">RFC 1033</em>,
<em class="citetitle">RFC 1034</em>,
<em class="citetitle">RFC 1035</em>,
- <span class="citerefentry"><span class="refentrytitle">named-checkconf</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">named-checkzone</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">lwresd</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">named.conf</span>(5)</span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named-checkconf</span>
+ (8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named-checkzone</span>
+ (8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">rndc</span>
+ (8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">lwresd</span>
+ (8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named.conf</span>
+ (5)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2687568"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
-<a accesskey="p" href="man.named-checkzone.html">Prev</a> </td>
+<a accesskey="p" href="man.lwresd.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="man.named.conf.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
-<span class="application">named-checkzone</span> </td>
+<span class="application">lwresd</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top"> <code class="filename">named.conf</code>
</td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nsec3hash</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
-<link rel="prev" href="man.named-rrchecker.html" title="named-rrchecker">
+<link rel="prev" href="man.isc-hmac-fixup.html" title="isc-hmac-fixup">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<tr><th colspan="3" align="center"><span class="application">nsec3hash</span></th></tr>
<tr>
<td width="20%" align="left">
-<a accesskey="p" href="man.named-rrchecker.html">Prev</a> </td>
+<a accesskey="p" href="man.isc-hmac-fixup.html">Prev</a> </td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right"> </td>
</tr>
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.nsec3hash"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">nsec3hash</span> — generate NSEC3 hash</p>
+<p>
+ <span class="application">nsec3hash</span>
+ — generate NSEC3 hash
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">nsec3hash</code> {<em class="replaceable"><code>salt</code></em>} {<em class="replaceable"><code>algorithm</code></em>} {<em class="replaceable"><code>iterations</code></em>} {<em class="replaceable"><code>domain</code></em>}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746647"></a><h2>DESCRIPTION</h2>
-<p>
- <span><strong class="command">nsec3hash</strong></span> generates an NSEC3 hash based on
+ <div class="cmdsynopsis"><p>
+ <code class="command">nsec3hash</code>
+ {<em class="replaceable"><code>salt</code></em>}
+ {<em class="replaceable"><code>algorithm</code></em>}
+ {<em class="replaceable"><code>iterations</code></em>}
+ {<em class="replaceable"><code>domain</code></em>}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.31.7"></a><h2>DESCRIPTION</h2>
+
+ <p>
+ <span class="command"><strong>nsec3hash</strong></span> generates an NSEC3 hash based on
a set of NSEC3 parameters. This can be used to check the validity
of NSEC3 records in a signed zone.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746662"></a><h2>ARGUMENTS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.31.8"></a><h2>ARGUMENTS</h2>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">salt</span></dt>
-<dd><p>
+<dd>
+ <p>
The salt provided to the hash algorithm.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">algorithm</span></dt>
-<dd><p>
+<dd>
+ <p>
A number indicating the hash algorithm. Currently the
only supported hash algorithm for NSEC3 is SHA-1, which is
indicated by the number 1; consequently "1" is the only
useful value for this argument.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">iterations</span></dt>
-<dd><p>
+<dd>
+ <p>
The number of additional times the hash should be performed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">domain</span></dt>
-<dd><p>
+<dd>
+ <p>
The domain name to be hashed.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746724"></a><h2>SEE ALSO</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.31.9"></a><h2>SEE ALSO</h2>
+
+ <p>
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 5155</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746741"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
-<a accesskey="p" href="man.named-rrchecker.html">Prev</a> </td>
+<a accesskey="p" href="man.isc-hmac-fixup.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right"> </td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
-<span class="application">named-rrchecker</span> </td>
+<span class="application">isc-hmac-fixup</span> </td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top"> </td>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nsupdate</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-rrchecker.html" title="named-rrchecker">
<link rel="next" href="man.rndc.html" title="rndc">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.nsupdate"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">nsupdate</span> — Dynamic DNS update utility</p>
+<p>
+ <span class="application">nsupdate</span>
+ — Dynamic DNS update utility
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">nsupdate</code> [<code class="option">-d</code>] [<code class="option">-D</code>] [<code class="option">-L <em class="replaceable"><code>level</code></em></code>] [[<code class="option">-g</code>] | [<code class="option">-o</code>] | [<code class="option">-l</code>] | [<code class="option">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]keyname:secret</code></em></code>] | [<code class="option">-k <em class="replaceable"><code>keyfile</code></em></code>]] [<code class="option">-t <em class="replaceable"><code>timeout</code></em></code>] [<code class="option">-u <em class="replaceable"><code>udptimeout</code></em></code>] [<code class="option">-r <em class="replaceable"><code>udpretries</code></em></code>] [<code class="option">-R <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-v</code>] [<code class="option">-T</code>] [<code class="option">-P</code>] [<code class="option">-V</code>] [filename]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2664568"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">nsupdate</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">nsupdate</code>
+ [<code class="option">-d</code>]
+ [<code class="option">-D</code>]
+ [<code class="option">-L <em class="replaceable"><code>level</code></em></code>]
+ [
+ [<code class="option">-g</code>]
+ | [<code class="option">-o</code>]
+ | [<code class="option">-l</code>]
+ | [<code class="option">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]keyname:secret</code></em></code>]
+ | [<code class="option">-k <em class="replaceable"><code>keyfile</code></em></code>]
+ ]
+ [<code class="option">-t <em class="replaceable"><code>timeout</code></em></code>]
+ [<code class="option">-u <em class="replaceable"><code>udptimeout</code></em></code>]
+ [<code class="option">-r <em class="replaceable"><code>udpretries</code></em></code>]
+ [<code class="option">-R <em class="replaceable"><code>randomdev</code></em></code>]
+ [<code class="option">-v</code>]
+ [<code class="option">-T</code>]
+ [<code class="option">-P</code>]
+ [<code class="option">-V</code>]
+ [filename]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.22.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>nsupdate</strong></span>
is used to submit Dynamic DNS Update requests as defined in RFC 2136
to a name server.
This allows resource records to be added or removed from a zone
one
resource record.
</p>
-<p>
Zones that are under dynamic control via
- <span><strong class="command">nsupdate</strong></span>
+ <span class="command"><strong>nsupdate</strong></span>
or a DHCP server should not be edited by hand.
Manual edits could
conflict with dynamic updates and cause data to be lost.
</p>
-<p>
The resource records that are dynamically added or removed with
- <span><strong class="command">nsupdate</strong></span>
+ <span class="command"><strong>nsupdate</strong></span>
have to be in the same zone.
Requests are sent to the zone's master server.
This is identified by the MNAME field of the zone's SOA record.
</p>
-<p>
Transaction signatures can be used to authenticate the Dynamic
DNS updates. These use the TSIG resource record type described
in RFC 2845 or the SIG(0) record described in RFC 2535 and
RFC 2931 or GSS-TSIG as described in RFC 3645.
</p>
-<p>
TSIG relies on
a shared secret that should only be known to
- <span><strong class="command">nsupdate</strong></span> and the name server.
+ <span class="command"><strong>nsupdate</strong></span> and the name server.
For instance, suitable <span class="type">key</span> and
<span class="type">server</span> statements would be added to
<code class="filename">/etc/named.conf</code> so that the name server
can associate the appropriate secret key and algorithm with
the IP address of the client application that will be using
- TSIG authentication. You can use <span><strong class="command">ddns-confgen</strong></span>
+ TSIG authentication. You can use <span class="command"><strong>ddns-confgen</strong></span>
to generate suitable configuration fragments.
- <span><strong class="command">nsupdate</strong></span>
+ <span class="command"><strong>nsupdate</strong></span>
uses the <code class="option">-y</code> or <code class="option">-k</code> options
to provide the TSIG shared secret. These options are mutually exclusive.
</p>
-<p>
SIG(0) uses public key cryptography.
To use a SIG(0) key, the public key must be stored in a KEY
record in a zone served by the name server.
</p>
-<p>
GSS-TSIG uses Kerberos credentials. Standard GSS-TSIG mode
is switched on with the <code class="option">-g</code> flag. A
non-standards-compliant variant of GSS-TSIG used by Windows
2000 can be switched on with the <code class="option">-o</code> flag.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2665339"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.22.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-d</span></dt>
-<dd><p>
+<dd>
+ <p>
Debug mode. This provides tracing information about the
update requests that are made and the replies received
from the name server.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-D</span></dt>
-<dd><p>
+<dd>
+ <p>
Extra debug mode.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-k <em class="replaceable"><code>keyfile</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The file containing the TSIG authentication key.
Keyfiles may be in two formats: a single file containing
- a <code class="filename">named.conf</code>-format <span><strong class="command">key</strong></span>
+ a <code class="filename">named.conf</code>-format <span class="command"><strong>key</strong></span>
statement, which may be generated automatically by
- <span><strong class="command">ddns-confgen</strong></span>, or a pair of files whose names are
+ <span class="command"><strong>ddns-confgen</strong></span>, or a pair of files whose names are
of the format <code class="filename">K{name}.+157.+{random}.key</code> and
<code class="filename">K{name}.+157.+{random}.private</code>, which can be
- generated by <span><strong class="command">dnssec-keygen</strong></span>.
+ generated by <span class="command"><strong>dnssec-keygen</strong></span>.
The <code class="option">-k</code> may also be used to specify a SIG(0) key used
to authenticate Dynamic DNS update requests. In this case, the key
specified is not an HMAC-MD5 key.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-l</span></dt>
-<dd><p>
+<dd>
+ <p>
Local-host only mode. This sets the server address to
- localhost (disabling the <span><strong class="command">server</strong></span> so that the server
+ localhost (disabling the <span class="command"><strong>server</strong></span> so that the server
address cannot be overridden). Connections to the local server will
use a TSIG key found in <code class="filename">/var/run/named/session.key</code>,
- which is automatically generated by <span><strong class="command">named</strong></span> if any
- local master zone has set <span><strong class="command">update-policy</strong></span> to
- <span><strong class="command">local</strong></span>. The location of this key file can be
+ which is automatically generated by <span class="command"><strong>named</strong></span> if any
+ local master zone has set <span class="command"><strong>update-policy</strong></span> to
+ <span class="command"><strong>local</strong></span>. The location of this key file can be
overridden with the <code class="option">-k</code> option.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-L <em class="replaceable"><code>level</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the logging debug level. If zero, logging is disabled.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Set the port to use for connections to a name server. The
default is 53.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-P</span></dt>
-<dd><p>
+<dd>
+ <p>
Print the list of private BIND-specific resource record
types whose format is understood
- by <span><strong class="command">nsupdate</strong></span>. See also
+ by <span class="command"><strong>nsupdate</strong></span>. See also
the <code class="option">-T</code> option.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-r <em class="replaceable"><code>udpretries</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The number of UDP retries. The default is 3. If zero, only
one update request will be made.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-R <em class="replaceable"><code>randomdev</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Where to obtain randomness. If the operating system
does not provide a <code class="filename">/dev/random</code> or
equivalent device, the default source of randomness is keyboard
instead of the default. The special value
<code class="filename">keyboard</code> indicates that keyboard input
should be used. This option may be specified multiple times.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>timeout</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The maximum time an update request can take before it is
aborted. The default is 300 seconds. Zero can be used to
disable the timeout.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-T</span></dt>
<dd>
-<p>
Print the list of IANA standard resource record types
- whose format is understood by <span><strong class="command">nsupdate</strong></span>.
- <span><strong class="command">nsupdate</strong></span> will exit after the lists are
+ whose format is understood by <span class="command"><strong>nsupdate</strong></span>.
+ <span class="command"><strong>nsupdate</strong></span> will exit after the lists are
printed. The <code class="option">-T</code> option can be combined
with the <code class="option">-P</code> option.
</p>
-<p>
Other types can be entered using "TYPEXXXXX" where "XXXXX" is the
decimal value of the type with no leading zeros. The rdata,
if present, will be parsed using the UNKNOWN rdata format,
(<backslash> <hash> <space> <length>
<space> <hexstring>).
</p>
-</dd>
+ </dd>
<dt><span class="term">-u <em class="replaceable"><code>udptimeout</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
The UDP retry interval. The default is 3 seconds. If zero,
the interval will be computed from the timeout interval and
number of UDP retries.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-v</span></dt>
-<dd><p>
+<dd>
+ <p>
Use TCP even for small update requests.
- By default, <span><strong class="command">nsupdate</strong></span>
+ By default, <span class="command"><strong>nsupdate</strong></span>
uses UDP to send update requests to the name server unless they are too
large to fit in a UDP request in which case TCP will be used.
TCP may be preferable when a batch of update requests is made.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Print the version number and exit.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]keyname:secret</code></em></span></dt>
<dd>
-<p>
Literal TSIG authentication key.
<em class="parameter"><code>keyname</code></em> is the name of the key, and
<em class="parameter"><code>secret</code></em> is the base64 encoded shared secret.
<code class="literal">hmac-sha512</code>. If <em class="parameter"><code>hmac</code></em>
is not specified, the default is <code class="literal">hmac-md5</code>.
</p>
-<p>
NOTE: Use of the <code class="option">-y</code> option is discouraged because the
shared secret is supplied as a command line argument in clear text.
This may be visible in the output from
- <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
+ <span class="citerefentry">
+ <span class="refentrytitle">ps</span>(1)
+ </span>
or in a history file maintained by the user's shell.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2765929"></a><h2>INPUT FORMAT</h2>
-<p><span><strong class="command">nsupdate</strong></span>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.22.9"></a><h2>INPUT FORMAT</h2>
+
+ <p><span class="command"><strong>nsupdate</strong></span>
reads input from
<em class="parameter"><code>filename</code></em>
or standard input.
Updates will be rejected if the tests for the prerequisite conditions
fail.
</p>
-<p>
Every update request consists of zero or more prerequisites
and zero or more updates.
This allows a suitably authenticated update request to proceed if some
specified resource records are present or missing from the zone.
- A blank input line (or the <span><strong class="command">send</strong></span> command)
+ A blank input line (or the <span class="command"><strong>send</strong></span> command)
causes the
accumulated commands to be sent as one Dynamic DNS update request to the
name server.
</p>
-<p>
The command formats and their meaning are as follows:
</p>
-<div class="variablelist"><dl>
+<div class="variablelist"><dl class="variablelist">
<dt><span class="term">
- <span><strong class="command">server</strong></span>
+ <span class="command"><strong>server</strong></span>
{servername}
[port]
</span></dt>
-<dd><p>
+<dd>
+ <p>
Sends all dynamic update requests to the name server
<em class="parameter"><code>servername</code></em>.
When no server statement is provided,
- <span><strong class="command">nsupdate</strong></span>
+ <span class="command"><strong>nsupdate</strong></span>
will send updates to the master server of the correct zone.
The MNAME field of that zone's SOA record will identify the
master
If no port number is specified, the default DNS port number of
53 is
used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">local</strong></span>
+ <span class="command"><strong>local</strong></span>
{address}
[port]
</span></dt>
-<dd><p>
+<dd>
+ <p>
Sends all dynamic update requests using the local
<em class="parameter"><code>address</code></em>.
When no local statement is provided,
- <span><strong class="command">nsupdate</strong></span>
+ <span class="command"><strong>nsupdate</strong></span>
will send updates using an address and port chosen by the
system.
<em class="parameter"><code>port</code></em>
can additionally be used to make requests come from a specific
port.
If no port number is specified, the system will assign one.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">zone</strong></span>
+ <span class="command"><strong>zone</strong></span>
{zonename}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies that all updates are to be made to the zone
<em class="parameter"><code>zonename</code></em>.
If no
<em class="parameter"><code>zone</code></em>
statement is provided,
- <span><strong class="command">nsupdate</strong></span>
+ <span class="command"><strong>nsupdate</strong></span>
will attempt determine the correct zone to update based on the
rest of the input.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">class</strong></span>
+ <span class="command"><strong>class</strong></span>
{classname}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the default class.
If no <em class="parameter"><code>class</code></em> is specified, the
default class is
<em class="parameter"><code>IN</code></em>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">ttl</strong></span>
+ <span class="command"><strong>ttl</strong></span>
{seconds}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Specify the default time to live for records to be added.
The value <em class="parameter"><code>none</code></em> will clear the default
ttl.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">key</strong></span>
+ <span class="command"><strong>key</strong></span>
[hmac:] {keyname}
{secret}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies that all updates are to be TSIG-signed using the
<em class="parameter"><code>keyname</code></em> <em class="parameter"><code>secret</code></em> pair.
If <em class="parameter"><code>hmac</code></em> is specified, then it sets the
signing algorithm in use; the default is
- <code class="literal">hmac-md5</code>. The <span><strong class="command">key</strong></span>
+ <code class="literal">hmac-md5</code>. The <span class="command"><strong>key</strong></span>
command overrides any key specified on the command line via
<code class="option">-y</code> or <code class="option">-k</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">gsstsig</strong></span>
+ <span class="command"><strong>gsstsig</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Use GSS-TSIG to sign the updated. This is equivalent to
specifying <code class="option">-g</code> on the command line.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">oldgsstsig</strong></span>
+ <span class="command"><strong>oldgsstsig</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Use the Windows 2000 version of GSS-TSIG to sign the updated.
This is equivalent to specifying <code class="option">-o</code> on the
command line.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">realm</strong></span>
+ <span class="command"><strong>realm</strong></span>
{[<span class="optional">realm_name</span>]}
</span></dt>
-<dd><p>
+<dd>
+ <p>
When using GSS-TSIG use <em class="parameter"><code>realm_name</code></em> rather
than the default realm in <code class="filename">krb5.conf</code>. If no
realm is specified the saved realm is cleared.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">check-names</strong></span>
+ <span class="command"><strong>check-names</strong></span>
{[<span class="optional">yes_or_no</span>]}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Turn on or off check-names processing on records to
be added. Check-names has no effect on prerequisites
or records to be deleted. By default check-names
processing is on. If check-names processing fails
the record will not be added to the UPDATE message.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">[<span class="optional">prereq</span>] nxdomain</strong></span>
+ <span class="command"><strong>[<span class="optional">prereq</span>] nxdomain</strong></span>
{domain-name}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Requires that no resource record of any type exists with name
<em class="parameter"><code>domain-name</code></em>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">[<span class="optional">prereq</span>] yxdomain</strong></span>
+ <span class="command"><strong>[<span class="optional">prereq</span>] yxdomain</strong></span>
{domain-name}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Requires that
<em class="parameter"><code>domain-name</code></em>
exists (has as at least one resource record, of any type).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">[<span class="optional">prereq</span>] nxrrset</strong></span>
+ <span class="command"><strong>[<span class="optional">prereq</span>] nxrrset</strong></span>
{domain-name}
[class]
{type}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Requires that no resource record exists of the specified
<em class="parameter"><code>type</code></em>,
<em class="parameter"><code>class</code></em>
If
<em class="parameter"><code>class</code></em>
is omitted, IN (internet) is assumed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">[<span class="optional">prereq</span>] yxrrset</strong></span>
+ <span class="command"><strong>[<span class="optional">prereq</span>] yxrrset</strong></span>
{domain-name}
[class]
{type}
</span></dt>
-<dd><p>
+<dd>
+ <p>
This requires that a resource record of the specified
<em class="parameter"><code>type</code></em>,
<em class="parameter"><code>class</code></em>
If
<em class="parameter"><code>class</code></em>
is omitted, IN (internet) is assumed.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">[<span class="optional">prereq</span>] yxrrset</strong></span>
+ <span class="command"><strong>[<span class="optional">prereq</span>] yxrrset</strong></span>
{domain-name}
[class]
{type}
{data...}
</span></dt>
-<dd><p>
+<dd>
+ <p>
The
<em class="parameter"><code>data</code></em>
from each set of prerequisites of this form
are written in the standard text representation of the resource
record's
RDATA.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">[<span class="optional">update</span>] del[<span class="optional">ete</span>]</strong></span>
+ <span class="command"><strong>[<span class="optional">update</span>] del[<span class="optional">ete</span>]</strong></span>
{domain-name}
[ttl]
[class]
[type [data...]]
</span></dt>
-<dd><p>
+<dd>
+ <p>
Deletes any resource records named
<em class="parameter"><code>domain-name</code></em>.
If
is not supplied. The
<em class="parameter"><code>ttl</code></em>
is ignored, and is only allowed for compatibility.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">[<span class="optional">update</span>] add</strong></span>
+ <span class="command"><strong>[<span class="optional">update</span>] add</strong></span>
{domain-name}
{ttl}
[class]
{type}
{data...}
</span></dt>
-<dd><p>
+<dd>
+ <p>
Adds a new resource record with the specified
<em class="parameter"><code>ttl</code></em>,
<em class="parameter"><code>class</code></em>
and
<em class="parameter"><code>data</code></em>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">show</strong></span>
+ <span class="command"><strong>show</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Displays the current message, containing all of the
prerequisites and
updates specified since the last send.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">send</strong></span>
+ <span class="command"><strong>send</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Sends the current message. This is equivalent to entering a
blank line.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">answer</strong></span>
+ <span class="command"><strong>answer</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Displays the answer.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">debug</strong></span>
+ <span class="command"><strong>debug</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Turn on debugging.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">version</strong></span>
+ <span class="command"><strong>version</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Print version number.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">
- <span><strong class="command">help</strong></span>
+ <span class="command"><strong>help</strong></span>
</span></dt>
-<dd><p>
+<dd>
+ <p>
Print a list of commands.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
<p>
</p>
-<p>
+
+ <p>
Lines beginning with a semicolon are comments and are ignored.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2767207"></a><h2>EXAMPLES</h2>
-<p>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.22.10"></a><h2>EXAMPLES</h2>
+
+ <p>
The examples below show how
- <span><strong class="command">nsupdate</strong></span>
+ <span class="command"><strong>nsupdate</strong></span>
could be used to insert and delete resource records from the
<span class="type">example.com</span>
zone.
</pre>
<p>
</p>
-<p>
Any A records for
<span class="type">oldhost.example.com</span>
are deleted.
</pre>
<p>
</p>
-<p>
The prerequisite condition gets the name server to check that there
are no resource records of any type for
<span class="type">nickname.example.com</span>.
(The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have
RRSIG, DNSKEY and NSEC records.)
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2767257"></a><h2>FILES</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.22.11"></a><h2>FILES</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="constant">/etc/resolv.conf</code></span></dt>
-<dd><p>
+<dd>
+ <p>
used to identify default name server
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="constant">/var/run/named/session.key</code></span></dt>
-<dd><p>
+<dd>
+ <p>
sets the default TSIG key for use in local-only mode
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><code class="constant">K{name}.+157.+{random}.key</code></span></dt>
-<dd><p>
+<dd>
+ <p>
base-64 encoding of HMAC-MD5 key created by
- <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
- </p></dd>
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>.
+ </p>
+ </dd>
<dt><span class="term"><code class="constant">K{name}.+157.+{random}.private</code></span></dt>
-<dd><p>
+<dd>
+ <p>
base-64 encoding of HMAC-MD5 key created by
- <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
- </p></dd>
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>.
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2767412"></a><h2>SEE ALSO</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.22.12"></a><h2>SEE ALSO</h2>
+
+ <p>
<em class="citetitle">RFC 2136</em>,
<em class="citetitle">RFC 3007</em>,
<em class="citetitle">RFC 2104</em>,
<em class="citetitle">RFC 1034</em>,
<em class="citetitle">RFC 2535</em>,
<em class="citetitle">RFC 2931</em>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">ddns-confgen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">ddns-confgen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">dnssec-keygen</span>(8)
+ </span>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2767469"></a><h2>BUGS</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.22.13"></a><h2>BUGS</h2>
+
+ <p>
The TSIG key is redundantly stored in two separate files.
This is a consequence of nsupdate using the DST library
for its cryptographic operations, and may change in future
releases.
</p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc-confgen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.rndc.conf.html" title="rndc.conf">
<link rel="next" href="man.ddns-confgen.html" title="ddns-confgen">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.rndc-confgen"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">rndc-confgen</span> — rndc key generation tool</p>
+<p>
+ <span class="application">rndc-confgen</span>
+ — rndc key generation tool
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">rndc-confgen</code> [<code class="option">-a</code>] [<code class="option">-A <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-b <em class="replaceable"><code>keysize</code></em></code>] [<code class="option">-c <em class="replaceable"><code>keyfile</code></em></code>] [<code class="option">-h</code>] [<code class="option">-k <em class="replaceable"><code>keyname</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>] [<code class="option">-s <em class="replaceable"><code>address</code></em></code>] [<code class="option">-t <em class="replaceable"><code>chrootdir</code></em></code>] [<code class="option">-u <em class="replaceable"><code>user</code></em></code>]</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2718548"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">rndc-confgen</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">rndc-confgen</code>
+ [<code class="option">-a</code>]
+ [<code class="option">-A <em class="replaceable"><code>algorithm</code></em></code>]
+ [<code class="option">-b <em class="replaceable"><code>keysize</code></em></code>]
+ [<code class="option">-c <em class="replaceable"><code>keyfile</code></em></code>]
+ [<code class="option">-h</code>]
+ [<code class="option">-k <em class="replaceable"><code>keyname</code></em></code>]
+ [<code class="option">-p <em class="replaceable"><code>port</code></em></code>]
+ [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>]
+ [<code class="option">-s <em class="replaceable"><code>address</code></em></code>]
+ [<code class="option">-t <em class="replaceable"><code>chrootdir</code></em></code>]
+ [<code class="option">-u <em class="replaceable"><code>user</code></em></code>]
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.25.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>rndc-confgen</strong></span>
generates configuration files
- for <span><strong class="command">rndc</strong></span>. It can be used as a
+ for <span class="command"><strong>rndc</strong></span>. It can be used as a
convenient alternative to writing the
<code class="filename">rndc.conf</code> file
- and the corresponding <span><strong class="command">controls</strong></span>
- and <span><strong class="command">key</strong></span>
+ and the corresponding <span class="command"><strong>controls</strong></span>
+ and <span class="command"><strong>key</strong></span>
statements in <code class="filename">named.conf</code> by hand.
- Alternatively, it can be run with the <span><strong class="command">-a</strong></span>
+ Alternatively, it can be run with the <span class="command"><strong>-a</strong></span>
option to set up a <code class="filename">rndc.key</code> file and
avoid the need for a <code class="filename">rndc.conf</code> file
- and a <span><strong class="command">controls</strong></span> statement altogether.
+ and a <span class="command"><strong>controls</strong></span> statement altogether.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2718614"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.25.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-a</span></dt>
<dd>
-<p>
- Do automatic <span><strong class="command">rndc</strong></span> configuration.
+ Do automatic <span class="command"><strong>rndc</strong></span> configuration.
This creates a file <code class="filename">rndc.key</code>
in <code class="filename">/etc</code> (or whatever
<code class="varname">sysconfdir</code>
was specified as when <acronym class="acronym">BIND</acronym> was
built)
- that is read by both <span><strong class="command">rndc</strong></span>
- and <span><strong class="command">named</strong></span> on startup. The
+ that is read by both <span class="command"><strong>rndc</strong></span>
+ and <span class="command"><strong>named</strong></span> on startup. The
<code class="filename">rndc.key</code> file defines a default
command channel and authentication key allowing
- <span><strong class="command">rndc</strong></span> to communicate with
- <span><strong class="command">named</strong></span> on the local host
+ <span class="command"><strong>rndc</strong></span> to communicate with
+ <span class="command"><strong>named</strong></span> on the local host
with no further configuration.
</p>
-<p>
- Running <span><strong class="command">rndc-confgen -a</strong></span> allows
- BIND 9 and <span><strong class="command">rndc</strong></span> to be used as
+ Running <span class="command"><strong>rndc-confgen -a</strong></span> allows
+ BIND 9 and <span class="command"><strong>rndc</strong></span> to be used as
drop-in
- replacements for BIND 8 and <span><strong class="command">ndc</strong></span>,
+ replacements for BIND 8 and <span class="command"><strong>ndc</strong></span>,
with no changes to the existing BIND 8
<code class="filename">named.conf</code> file.
</p>
-<p>
If a more elaborate configuration than that
- generated by <span><strong class="command">rndc-confgen -a</strong></span>
+ generated by <span class="command"><strong>rndc-confgen -a</strong></span>
is required, for example if rndc is to be used remotely,
- you should run <span><strong class="command">rndc-confgen</strong></span> without
+ you should run <span class="command"><strong>rndc-confgen</strong></span> without
the
- <span><strong class="command">-a</strong></span> option and set up a
+ <span class="command"><strong>-a</strong></span> option and set up a
<code class="filename">rndc.conf</code> and
<code class="filename">named.conf</code>
as directed.
</p>
-</dd>
+ </dd>
<dt><span class="term">-A <em class="replaceable"><code>algorithm</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the algorithm to use for the TSIG key. Available
choices are: hmac-md5, hmac-sha1, hmac-sha224, hmac-sha256,
hmac-sha384 and hmac-sha512. The default is hmac-md5.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-b <em class="replaceable"><code>keysize</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the size of the authentication key in bits.
Must be between 1 and 512 bits; the default is the
hash size.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>keyfile</code></em></span></dt>
-<dd><p>
- Used with the <span><strong class="command">-a</strong></span> option to specify
+<dd>
+ <p>
+ Used with the <span class="command"><strong>-a</strong></span> option to specify
an alternate location for <code class="filename">rndc.key</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-h</span></dt>
-<dd><p>
+<dd>
+ <p>
Prints a short summary of the options and arguments to
- <span><strong class="command">rndc-confgen</strong></span>.
- </p></dd>
+ <span class="command"><strong>rndc-confgen</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-k <em class="replaceable"><code>keyname</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies the key name of the rndc authentication key.
This must be a valid domain name.
The default is <code class="constant">rndc-key</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
-<dd><p>
- Specifies the command channel port where <span><strong class="command">named</strong></span>
- listens for connections from <span><strong class="command">rndc</strong></span>.
+<dd>
+ <p>
+ Specifies the command channel port where <span class="command"><strong>named</strong></span>
+ listens for connections from <span class="command"><strong>rndc</strong></span>.
The default is 953.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-r <em class="replaceable"><code>randomfile</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Specifies a source of random data for generating the
authorization. If the operating
system does not provide a <code class="filename">/dev/random</code>
data to be used instead of the default. The special value
<code class="filename">keyboard</code> indicates that keyboard
input should be used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s <em class="replaceable"><code>address</code></em></span></dt>
-<dd><p>
- Specifies the IP address where <span><strong class="command">named</strong></span>
+<dd>
+ <p>
+ Specifies the IP address where <span class="command"><strong>named</strong></span>
listens for command channel connections from
- <span><strong class="command">rndc</strong></span>. The default is the loopback
+ <span class="command"><strong>rndc</strong></span>. The default is the loopback
address 127.0.0.1.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-t <em class="replaceable"><code>chrootdir</code></em></span></dt>
-<dd><p>
- Used with the <span><strong class="command">-a</strong></span> option to specify
- a directory where <span><strong class="command">named</strong></span> will run
+<dd>
+ <p>
+ Used with the <span class="command"><strong>-a</strong></span> option to specify
+ a directory where <span class="command"><strong>named</strong></span> will run
chrooted. An additional copy of the <code class="filename">rndc.key</code>
will be written relative to this directory so that
- it will be found by the chrooted <span><strong class="command">named</strong></span>.
- </p></dd>
+ it will be found by the chrooted <span class="command"><strong>named</strong></span>.
+ </p>
+ </dd>
<dt><span class="term">-u <em class="replaceable"><code>user</code></em></span></dt>
-<dd><p>
- Used with the <span><strong class="command">-a</strong></span> option to set the
+<dd>
+ <p>
+ Used with the <span class="command"><strong>-a</strong></span> option to set the
owner
of the <code class="filename">rndc.key</code> file generated.
If
- <span><strong class="command">-t</strong></span> is also specified only the file
+ <span class="command"><strong>-t</strong></span> is also specified only the file
in
the chroot area has its owner changed.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2719085"></a><h2>EXAMPLES</h2>
-<p>
- To allow <span><strong class="command">rndc</strong></span> to be used with
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.25.9"></a><h2>EXAMPLES</h2>
+
+ <p>
+ To allow <span class="command"><strong>rndc</strong></span> to be used with
no manual configuration, run
</p>
-<p><strong class="userinput"><code>rndc-confgen -a</code></strong>
+
<p><strong class="userinput"><code>rndc-confgen -a</code></strong>
</p>
-<p>
To print a sample <code class="filename">rndc.conf</code> file and
- corresponding <span><strong class="command">controls</strong></span> and <span><strong class="command">key</strong></span>
+ corresponding <span class="command"><strong>controls</strong></span> and <span class="command"><strong>key</strong></span>
statements to be manually inserted into <code class="filename">named.conf</code>,
run
</p>
-<p><strong class="userinput"><code>rndc-confgen</code></strong>
+
<p><strong class="userinput"><code>rndc-confgen</code></strong>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2745971"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">rndc.conf</span>(5)</span>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.25.10"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">rndc</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">rndc.conf</span>(5)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2746009"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc.conf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.rndc.html" title="rndc">
<link rel="next" href="man.rndc-confgen.html" title="rndc-confgen">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.rndc.conf"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><code class="filename">rndc.conf</code> — rndc configuration file</p>
+<p>
+ <code class="filename">rndc.conf</code>
+ — rndc configuration file
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">rndc.conf</code> </p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2665719"></a><h2>DESCRIPTION</h2>
-<p><code class="filename">rndc.conf</code> is the configuration file
- for <span><strong class="command">rndc</strong></span>, the BIND 9 name server control
+ <div class="cmdsynopsis"><p>
+ <code class="command">rndc.conf</code>
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.24.7"></a><h2>DESCRIPTION</h2>
+
+ <p><code class="filename">rndc.conf</code> is the configuration file
+ for <span class="command"><strong>rndc</strong></span>, the BIND 9 name server control
utility. This file has a similar structure and syntax to
<code class="filename">named.conf</code>. Statements are enclosed
in braces and terminated with a semi-colon. Clauses in
the statements are also semi-colon terminated. The usual
comment styles are supported:
</p>
-<p>
C style: /* */
</p>
-<p>
C++ style: // to end of line
</p>
-<p>
Unix style: # to end of line
</p>
-<p><code class="filename">rndc.conf</code> is much simpler than
+
<p><code class="filename">rndc.conf</code> is much simpler than
<code class="filename">named.conf</code>. The file uses three
statements: an options statement, a server statement
and a key statement.
</p>
-<p>
The <code class="option">options</code> statement contains five clauses.
The <code class="option">default-server</code> clause is followed by the
name or address of a name server. This host will be used when
no name server is given as an argument to
- <span><strong class="command">rndc</strong></span>. The <code class="option">default-key</code>
+ <span class="command"><strong>rndc</strong></span>. The <code class="option">default-key</code>
clause is followed by the name of a key which is identified by
a <code class="option">key</code> statement. If no
<code class="option">keyid</code> is provided on the rndc command line,
can be used to set the IPv4 and IPv6 source addresses
respectively.
</p>
-<p>
After the <code class="option">server</code> keyword, the server
statement includes a string which is the hostname or address
for a name server. The statement has three possible clauses:
of supplied then these will be used to specify the IPv4 and IPv6
source addresses respectively.
</p>
-<p>
The <code class="option">key</code> statement begins with an identifying
string, the name of the key. The statement has two clauses.
<code class="option">algorithm</code> identifies the authentication algorithm
- for <span><strong class="command">rndc</strong></span> to use; currently only HMAC-MD5
+ for <span class="command"><strong>rndc</strong></span> to use; currently only HMAC-MD5
(for compatibility), HMAC-SHA1, HMAC-SHA224, HMAC-SHA256
(default), HMAC-SHA384 and HMAC-SHA512 are
supported. This is followed by a secret clause which contains
the base-64 encoding of the algorithm's authentication key. The
base-64 string is enclosed in double quotes.
</p>
-<p>
There are two common ways to generate the base-64 string for the
- secret. The BIND 9 program <span><strong class="command">rndc-confgen</strong></span>
+ secret. The BIND 9 program <span class="command"><strong>rndc-confgen</strong></span>
can
be used to generate a random key, or the
- <span><strong class="command">mmencode</strong></span> program, also known as
- <span><strong class="command">mimencode</strong></span>, can be used to generate a
+ <span class="command"><strong>mmencode</strong></span> program, also known as
+ <span class="command"><strong>mimencode</strong></span>, can be used to generate a
base-64
- string from known input. <span><strong class="command">mmencode</strong></span> does
+ string from known input. <span class="command"><strong>mmencode</strong></span> does
not
ship with BIND 9 but is available on many systems. See the
EXAMPLE section for sample command lines for each.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2718183"></a><h2>EXAMPLE</h2>
-<pre class="programlisting">
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.24.8"></a><h2>EXAMPLE</h2>
+
+
+ <pre class="programlisting">
options {
default-server localhost;
default-key samplekey;
</pre>
<p>
</p>
-<pre class="programlisting">
+
<pre class="programlisting">
server localhost {
key samplekey;
};
</pre>
<p>
</p>
-<pre class="programlisting">
+
<pre class="programlisting">
server testserver {
key testkey;
addresses { localhost port 5353; };
</pre>
<p>
</p>
-<pre class="programlisting">
+
<pre class="programlisting">
key samplekey {
algorithm hmac-sha256;
secret "6FMfj43Osz4lyb24OIe2iGEz9lf1llJO+lz";
</pre>
<p>
</p>
-<pre class="programlisting">
+
<pre class="programlisting">
key testkey {
algorithm hmac-sha256;
secret "R3HI8P6BKw9ZwXwN3VZKuQ==";
</pre>
<p>
</p>
-<p>
- In the above example, <span><strong class="command">rndc</strong></span> will by
+
+ <p>
+ In the above example, <span class="command"><strong>rndc</strong></span> will by
default use
the server at localhost (127.0.0.1) and the key called samplekey.
Commands to the localhost server will use the samplekey key, which
uses the HMAC-SHA256 algorithm and its secret clause contains the
base-64 encoding of the HMAC-SHA256 secret enclosed in double quotes.
</p>
-<p>
- If <span><strong class="command">rndc -s testserver</strong></span> is used then <span><strong class="command">rndc</strong></span> will
+ If <span class="command"><strong>rndc -s testserver</strong></span> is used then <span class="command"><strong>rndc</strong></span> will
connect to server on localhost port 5353 using the key testkey.
</p>
-<p>
- To generate a random secret with <span><strong class="command">rndc-confgen</strong></span>:
+ To generate a random secret with <span class="command"><strong>rndc-confgen</strong></span>:
</p>
-<p><strong class="userinput"><code>rndc-confgen</code></strong>
+
<p><strong class="userinput"><code>rndc-confgen</code></strong>
</p>
-<p>
A complete <code class="filename">rndc.conf</code> file, including
the
randomly generated key, will be written to the standard
<code class="option">controls</code> statements for
<code class="filename">named.conf</code> are also printed.
</p>
-<p>
- To generate a base-64 secret with <span><strong class="command">mmencode</strong></span>:
+ To generate a base-64 secret with <span class="command"><strong>mmencode</strong></span>:
</p>
-<p><strong class="userinput"><code>echo "known plaintext for a secret" | mmencode</code></strong>
+
<p><strong class="userinput"><code>echo "known plaintext for a secret" | mmencode</code></strong>
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2718305"></a><h2>NAME SERVER CONFIGURATION</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.24.9"></a><h2>NAME SERVER CONFIGURATION</h2>
+
+ <p>
The name server must be configured to accept rndc connections and
to recognize the key specified in the <code class="filename">rndc.conf</code>
file, using the controls statement in <code class="filename">named.conf</code>.
See the sections on the <code class="option">controls</code> statement in the
BIND 9 Administrator Reference Manual for details.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2718330"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">rndc-confgen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">mmencode</span>(1)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.24.10"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">rndc</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">rndc-confgen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">mmencode</span>(1)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2718369"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id$ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
-<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.nsupdate.html" title="nsupdate">
<link rel="next" href="man.rndc.conf.html" title="rndc.conf">
</table>
<hr>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="man.rndc"></a><div class="titlepage"></div>
-<div class="refnamediv">
+
+
+
+
+
+ <div class="refnamediv">
<h2>Name</h2>
-<p><span class="application">rndc</span> — name server control utility</p>
+<p>
+ <span class="application">rndc</span>
+ — name server control utility
+ </p>
</div>
-<div class="refsynopsisdiv">
+
+
+
+ <div class="refsynopsisdiv">
<h2>Synopsis</h2>
-<div class="cmdsynopsis"><p><code class="command">rndc</code> [<code class="option">-b <em class="replaceable"><code>source-address</code></em></code>] [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-k <em class="replaceable"><code>key-file</code></em></code>] [<code class="option">-s <em class="replaceable"><code>server</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-q</code>] [<code class="option">-r</code>] [<code class="option">-V</code>] [<code class="option">-y <em class="replaceable"><code>key_id</code></em></code>] {command}</p></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2690758"></a><h2>DESCRIPTION</h2>
-<p><span><strong class="command">rndc</strong></span>
+ <div class="cmdsynopsis"><p>
+ <code class="command">rndc</code>
+ [<code class="option">-b <em class="replaceable"><code>source-address</code></em></code>]
+ [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>]
+ [<code class="option">-k <em class="replaceable"><code>key-file</code></em></code>]
+ [<code class="option">-s <em class="replaceable"><code>server</code></em></code>]
+ [<code class="option">-p <em class="replaceable"><code>port</code></em></code>]
+ [<code class="option">-q</code>]
+ [<code class="option">-r</code>]
+ [<code class="option">-V</code>]
+ [<code class="option">-y <em class="replaceable"><code>key_id</code></em></code>]
+ {command}
+ </p></div>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.23.7"></a><h2>DESCRIPTION</h2>
+
+ <p><span class="command"><strong>rndc</strong></span>
controls the operation of a name
- server. It supersedes the <span><strong class="command">ndc</strong></span> utility
+ server. It supersedes the <span class="command"><strong>ndc</strong></span> utility
that was provided in old BIND releases. If
- <span><strong class="command">rndc</strong></span> is invoked with no command line
+ <span class="command"><strong>rndc</strong></span> is invoked with no command line
options or arguments, it prints a short summary of the
supported commands and the available options and their
arguments.
</p>
-<p><span><strong class="command">rndc</strong></span>
+ <p><span class="command"><strong>rndc</strong></span>
communicates with the name server over a TCP connection, sending
commands authenticated with digital signatures. In the current
versions of
- <span><strong class="command">rndc</strong></span> and <span><strong class="command">named</strong></span>,
+ <span class="command"><strong>rndc</strong></span> and <span class="command"><strong>named</strong></span>,
the only supported authentication algorithms are HMAC-MD5
(for compatibility), HMAC-SHA1, HMAC-SHA224, HMAC-SHA256
(default), HMAC-SHA384 and HMAC-SHA512.
over the channel must be signed by a key_id known to the
server.
</p>
-<p><span><strong class="command">rndc</strong></span>
+ <p><span class="command"><strong>rndc</strong></span>
reads a configuration file to
determine how to contact the name server and decide what
algorithm and key it should use.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2690876"></a><h2>OPTIONS</h2>
-<div class="variablelist"><dl>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.23.8"></a><h2>OPTIONS</h2>
+
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term">-b <em class="replaceable"><code>source-address</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>source-address</code></em>
as the source address for the connection to the server.
Multiple instances are permitted to allow setting of both
the IPv4 and IPv6 source addresses.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-c <em class="replaceable"><code>config-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>config-file</code></em>
as the configuration file instead of the default,
<code class="filename">/etc/rndc.conf</code>.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-k <em class="replaceable"><code>key-file</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use <em class="replaceable"><code>key-file</code></em>
as the key file instead of the default,
<code class="filename">/etc/rndc.key</code>. The key in
authenticate
commands sent to the server if the <em class="replaceable"><code>config-file</code></em>
does not exist.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-s <em class="replaceable"><code>server</code></em></span></dt>
-<dd><p><em class="replaceable"><code>server</code></em> is
+<dd>
+ <p><em class="replaceable"><code>server</code></em> is
the name or address of the server which matches a
server statement in the configuration file for
- <span><strong class="command">rndc</strong></span>. If no server is supplied on the
+ <span class="command"><strong>rndc</strong></span>. If no server is supplied on the
command line, the host named by the default-server clause
- in the options statement of the <span><strong class="command">rndc</strong></span>
+ in the options statement of the <span class="command"><strong>rndc</strong></span>
configuration file will be used.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Send commands to TCP port
<em class="replaceable"><code>port</code></em>
instead
of BIND 9's default control channel port, 953.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-q</span></dt>
-<dd><p>
+<dd>
+ <p>
Quiet mode: Message text returned by the server
will not be printed except when there is an error.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-r</span></dt>
-<dd><p>
- Instructs <span><strong class="command">rndc</strong></span> to print the result code
- returned by <span><strong class="command">named</strong></span> after executing the
+<dd>
+ <p>
+ Instructs <span class="command"><strong>rndc</strong></span> to print the result code
+ returned by <span class="command"><strong>named</strong></span> after executing the
requested command (e.g., ISC_R_SUCCESS, ISC_R_FAILURE, etc).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-V</span></dt>
-<dd><p>
+<dd>
+ <p>
Enable verbose logging.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term">-y <em class="replaceable"><code>key_id</code></em></span></dt>
-<dd><p>
+<dd>
+ <p>
Use the key <em class="replaceable"><code>key_id</code></em>
from the configuration file.
<em class="replaceable"><code>key_id</code></em>
must be
- known by <span><strong class="command">named</strong></span> with the same algorithm and secret string
+ known by <span class="command"><strong>named</strong></span> with the same algorithm and secret string
in order for control message validation to succeed.
If no <em class="replaceable"><code>key_id</code></em>
- is specified, <span><strong class="command">rndc</strong></span> will first look
+ is specified, <span class="command"><strong>rndc</strong></span> will first look
for a key clause in the server statement of the server
being used, or if no server statement is present for that
host, then the default-key clause of the options statement.
which are used to send authenticated control commands
to name servers. It should therefore not have general read
or write access.
- </p></dd>
+ </p>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2691129"></a><h2>COMMANDS</h2>
-<p>
- A list of commands supported by <span><strong class="command">rndc</strong></span> can
- be seen by running <span><strong class="command">rndc</strong></span> without arguments.
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.23.9"></a><h2>COMMANDS</h2>
+
+ <p>
+ A list of commands supported by <span class="command"><strong>rndc</strong></span> can
+ be seen by running <span class="command"><strong>rndc</strong></span> without arguments.
</p>
-<p>
Currently supported commands are:
</p>
-<div class="variablelist"><dl>
+
+ <div class="variablelist"><dl class="variablelist">
<dt><span class="term"><strong class="userinput"><code>addzone <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] <em class="replaceable"><code>configuration</code></em> </code></strong></span></dt>
<dd>
-<p>
Add a zone while the server is running. This
command requires the
- <span><strong class="command">allow-new-zones</strong></span> option to be set
+ <span class="command"><strong>allow-new-zones</strong></span> option to be set
to <strong class="userinput"><code>yes</code></strong>. The
<em class="replaceable"><code>configuration</code></em> string
specified on the command line is the zone
configuration text that would ordinarily be
placed in <code class="filename">named.conf</code>.
</p>
-<p>
The configuration is saved in a file called
<code class="filename"><em class="replaceable"><code>name</code></em>.nzf</code>,
where <em class="replaceable"><code>name</code></em> is the
that are incompatible with use as a file name, a
cryptographic hash generated from the name
of the view.
- When <span><strong class="command">named</strong></span> is
+ When <span class="command"><strong>named</strong></span> is
restarted, the file will be loaded into the view
configuration, so that zones that were added
can persist after a restart.
</p>
-<p>
- This sample <span><strong class="command">addzone</strong></span> command
+ This sample <span class="command"><strong>addzone</strong></span> command
would add the zone <code class="literal">example.com</code>
to the default view:
</p>
-<p>
<code class="prompt">$ </code><strong class="userinput"><code>rndc addzone example.com '{ type master; file "example.com.db"; };'</code></strong>
</p>
-<p>
(Note the brackets and semi-colon around the zone
configuration text.)
</p>
-<p>
- See also <span><strong class="command">rndc delzone</strong></span> and <span><strong class="command">rndc modzone</strong></span>.
+ See also <span class="command"><strong>rndc delzone</strong></span> and <span class="command"><strong>rndc modzone</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>delzone [<span class="optional">-clean</span>] <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] </code></strong></span></dt>
<dd>
-<p>
Delete a zone while the server is running.
</p>
-<p>
If the <code class="option">-clean</code> argument is specified,
the zone's master file (and journal file, if any)
will be deleted along with the zone. Without the
be cleaned up by hand. (If the zone is of
type "slave" or "stub", the files needing to
be cleaned up will be reported in the output
- of the <span><strong class="command">rndc delzone</strong></span> command.)
+ of the <span class="command"><strong>rndc delzone</strong></span> command.)
</p>
-<p>
If the zone was originally added via
- <span><strong class="command">rndc addzone</strong></span>, then it will be
+ <span class="command"><strong>rndc addzone</strong></span>, then it will be
removed permanently. However, if it was originally
configured in <code class="filename">named.conf</code>, then
that original configuration is still in place; when
come back. To remove it permanently, it must also be
removed from <code class="filename">named.conf</code>
</p>
-<p>
- See also <span><strong class="command">rndc addzone</strong></span> and <span><strong class="command">rndc modzone</strong></span>.
+ See also <span class="command"><strong>rndc addzone</strong></span> and <span class="command"><strong>rndc modzone</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>dumpdb [<span class="optional">-all|-cache|-zone|-adb|-bad|-fail</span>] [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Dump the server's caches (default) and/or zones to
the
dump file for the specified views. If no view is
specified, all
views are dumped.
- (See the <span><strong class="command">dump-file</strong></span> option in
+ (See the <span class="command"><strong>dump-file</strong></span> option in
the BIND 9 Administrator Reference Manual.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>flush</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Flushes the server's cache.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>flushname</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
-<dd><p>
+<dd>
+ <p>
Flushes the given name from the view's DNS cache
and, if applicable, from the view's nameserver address
database, bad server cache and SERVFAIL cache.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>flushtree</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
-<dd><p>
+<dd>
+ <p>
Flushes the given name, and all of its subdomains,
from the view's DNS cache, address database,
bad server cache, and SERVFAIL cache.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>freeze [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
<dd>
-<p>
Suspend updates to a dynamic zone. If no zone is
specified, then all zones are suspended. This allows
manual edits to be made to a zone normally updated by
All dynamic update attempts will be refused while
the zone is frozen.
</p>
-<p>
- See also <span><strong class="command">rndc thaw</strong></span>.
+ See also <span class="command"><strong>rndc thaw</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>halt [<span class="optional">-p</span>]</code></strong></span></dt>
<dd>
-<p>
Stop the server immediately. Recent changes
made through dynamic update or IXFR are not saved to
the master files, but will be rolled forward from the
journal files when the server is restarted.
- If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
- This allows an external process to determine when <span><strong class="command">named</strong></span>
+ If <code class="option">-p</code> is specified <span class="command"><strong>named</strong></span>'s process id is returned.
+ This allows an external process to determine when <span class="command"><strong>named</strong></span>
had completed halting.
</p>
-<p>
- See also <span><strong class="command">rndc stop</strong></span>.
+ See also <span class="command"><strong>rndc stop</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>loadkeys <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
<dd>
-<p>
Fetch all DNSSEC keys for the given zone
from the key directory. If they are within
their publication period, merge them into the
- zone's DNSKEY RRset. Unlike <span><strong class="command">rndc
+ zone's DNSKEY RRset. Unlike <span class="command"><strong>rndc
sign</strong></span>, however, the zone is not
immediately re-signed by the new keys, but is
allowed to incrementally re-sign over time.
</p>
-<p>
This command requires that the
- <span><strong class="command">auto-dnssec</strong></span> zone option
+ <span class="command"><strong>auto-dnssec</strong></span> zone option
be set to <code class="literal">maintain</code>,
and also requires the zone to be configured to
allow dynamic DNS.
(See "Dynamic Update Policies" in the Administrator
Reference Manual for more details.)
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>managed-keys <em class="replaceable"><code>(status | refresh | sync)</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
When run with the "status" keyword, print the current
status of the managed-keys database for the specified
view, or for all views if none is specified. When run
immediate dump of the managed-keys database to disk (in
the file <code class="filename">managed-keys.bind</code> or
(<code class="filename"><em class="replaceable"><code>viewname</code></em>.mkeys</code>).
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>modzone <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] <em class="replaceable"><code>configuration</code></em> </code></strong></span></dt>
<dd>
-<p>
Modify the configuration of a zone while the server
is running. This command requires the
- <span><strong class="command">allow-new-zones</strong></span> option to be
+ <span class="command"><strong>allow-new-zones</strong></span> option to be
set to <strong class="userinput"><code>yes</code></strong>. As with
- <span><strong class="command">addzone</strong></span>, the
+ <span class="command"><strong>addzone</strong></span>, the
<em class="replaceable"><code>configuration</code></em> string
specified on the command line is the zone
configuration text that would ordinarily be
placed in <code class="filename">named.conf</code>.
</p>
-<p>
If the zone was originally added via
- <span><strong class="command">rndc addzone</strong></span>, the configuration
+ <span class="command"><strong>rndc addzone</strong></span>, the configuration
changes will be recorded permanently and will still be
in effect after the server is restarted or reconfigured.
However, if it was originally configured in
permanent, it must also be modified in
<code class="filename">named.conf</code>
</p>
-<p>
- See also <span><strong class="command">rndc addzone</strong></span> and <span><strong class="command">rndc delzone</strong></span>.
+ See also <span class="command"><strong>rndc addzone</strong></span> and <span class="command"><strong>rndc delzone</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>notify <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Resend NOTIFY messages for the zone.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>notrace</code></strong></span></dt>
<dd>
-<p>
Sets the server's debugging level to 0.
</p>
-<p>
- See also <span><strong class="command">rndc trace</strong></span>.
+ See also <span class="command"><strong>rndc trace</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>nta
[<span class="optional">( -d | -f | -r | -l <em class="replaceable"><code>duration</code></em>)</span>]
<em class="replaceable"><code>domain</code></em>
[<span class="optional"><em class="replaceable"><code>view</code></em></span>]
</code></strong></span></dt>
<dd>
-<p>
Sets a DNSSEC negative trust anchor (NTA)
for <code class="option">domain</code>, with a lifetime of
<code class="option">duration</code>. The default lifetime is
<code class="option">nta-lifetime</code> option, and defaults to
one hour. The lifetime cannot exceed one week.
</p>
-<p>
A negative trust anchor selectively disables
DNSSEC validation for zones that are known to be
failing because of misconfiguration rather than
an attack. When data to be validated is
at or below an active NTA (and above any other
- configured trust anchors), <span><strong class="command">named</strong></span> will
+ configured trust anchors), <span class="command"><strong>named</strong></span> will
abort the DNSSEC validation process and treat the data as
insecure rather than bogus. This continues until the
NTA's lifetime is elapsed.
</p>
-<p>
- NTAs persist across restarts of the <span><strong class="command">named</strong></span> server.
+ NTAs persist across restarts of the <span class="command"><strong>named</strong></span> server.
The NTAs for a view are saved in a file called
<code class="filename"><em class="replaceable"><code>name</code></em>.nta</code>,
where <em class="replaceable"><code>name</code></em> is the
cryptographic hash generated from the name
of the view.
</p>
-<p>
An existing NTA can be removed by using the
<code class="option">-remove</code> option.
</p>
-<p>
An NTA's lifetime can be specified with the
<code class="option">-lifetime</code> option. TTL-style
suffixes can be used to specify the lifetime in
new value. Setting <code class="option">lifetime</code> to zero
is equivalent to <code class="option">-remove</code>.
</p>
-<p>
If <code class="option">-dump</code> is used, any other arguments
are ignored, and a list of existing NTAs is printed
(note that this may include NTAs that are expired but
have not yet been cleaned up).
</p>
-<p>
- Normally, <span><strong class="command">named</strong></span> will periodically
+ Normally, <span class="command"><strong>named</strong></span> will periodically
test to see whether data below an NTA can now be
validated (see the <code class="option">nta-recheck</code> option
in the Administrator Reference Manual for details).
lifetime, regardless of whether data could be
validated if the NTA were not present.
</p>
-<p>
All of these options can be shortened, i.e., to
<code class="option">-l</code>, <code class="option">-r</code>, <code class="option">-d</code>,
and <code class="option">-f</code>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>querylog</code></strong> [<span class="optional">on|off</span>] </span></dt>
<dd>
-<p>
Enable or disable query logging. (For backward
compatibility, this command can also be used without
an argument to toggle query logging on and off.)
</p>
-<p>
Query logging can also be enabled
- by explicitly directing the <span><strong class="command">queries</strong></span>
- <span><strong class="command">category</strong></span> to a
- <span><strong class="command">channel</strong></span> in the
- <span><strong class="command">logging</strong></span> section of
+ by explicitly directing the <span class="command"><strong>queries</strong></span>
+ <span class="command"><strong>category</strong></span> to a
+ <span class="command"><strong>channel</strong></span> in the
+ <span class="command"><strong>logging</strong></span> section of
<code class="filename">named.conf</code> or by specifying
- <span><strong class="command">querylog yes;</strong></span> in the
- <span><strong class="command">options</strong></span> section of
+ <span class="command"><strong>querylog yes;</strong></span> in the
+ <span class="command"><strong>options</strong></span> section of
<code class="filename">named.conf</code>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>reconfig</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Reload the configuration file and load new zones,
but do not reload existing zone files even if they
have changed.
- This is faster than a full <span><strong class="command">reload</strong></span> when there
+ This is faster than a full <span class="command"><strong>reload</strong></span> when there
is a large number of zones because it avoids the need
to examine the
modification times of the zones files.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>recursing</code></strong></span></dt>
-<dd><p>
- Dump the list of queries <span><strong class="command">named</strong></span> is currently
+<dd>
+ <p>
+ Dump the list of queries <span class="command"><strong>named</strong></span> is currently
recursing on, and the list of domains to which iterative
queries are currently being sent. (The second list includes
the number of fetches currently active for the given domain,
and how many have been passed or dropped because of the
<code class="option">fetches-per-zone</code> option.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>refresh <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Schedule zone maintenance for the given zone.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>reload</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Reload configuration file and zones.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>reload <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Reload the given zone.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>retransfer <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
<dd>
-<p>
Retransfer the given slave zone from the master server.
</p>
-<p>
If the zone is configured to use
- <span><strong class="command">inline-signing</strong></span>, the signed
+ <span class="command"><strong>inline-signing</strong></span>, the signed
version of the zone is discarded; after the
retransfer of the unsigned version is complete, the
signed version will be regenerated with all new
signatures.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>scan</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Scan the list of available network interfaces
for changes, without performing a full
- <span><strong class="command">reconfig</strong></span> or waiting for the
- <span><strong class="command">interface-interval</strong></span> timer.
- </p></dd>
+ <span class="command"><strong>reconfig</strong></span> or waiting for the
+ <span class="command"><strong>interface-interval</strong></span> timer.
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>secroots [<span class="optional">-</span>] [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
<dd>
-<p>
Dump the server's security roots and negative trust anchors
for the specified views. If no view is specified, all views
are dumped.
</p>
-<p>
If the first argument is "-", then the output is
- returned via the <span><strong class="command">rndc</strong></span> response channel
+ returned via the <span class="command"><strong>rndc</strong></span> response channel
and printed to the standard output.
Otherwise, it is written to the secroots dump file, which
defaults to <code class="filename">named.secroots</code>, but can be
overridden via the <code class="option">secroots-file</code> option in
<code class="filename">named.conf</code>.
</p>
-<p>
- See also <span><strong class="command">rndc managed-keys</strong></span>.
+ See also <span class="command"><strong>rndc managed-keys</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>showzone <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] </code></strong></span></dt>
<dd>
-<p>
Print the configuration of a running zone.
</p>
-<p>
- See also <span><strong class="command">rndc zonestatus</strong></span>.
+ See also <span class="command"><strong>rndc zonestatus</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>sign <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
<dd>
-<p>
Fetch all DNSSEC keys for the given zone
from the key directory (see the
- <span><strong class="command">key-directory</strong></span> option in
+ <span class="command"><strong>key-directory</strong></span> option in
the BIND 9 Administrator Reference Manual). If they are within
their publication period, merge them into the
zone's DNSKEY RRset. If the DNSKEY RRset
is changed, then the zone is automatically
re-signed with the new key set.
</p>
-<p>
This command requires that the
- <span><strong class="command">auto-dnssec</strong></span> zone option be set
+ <span class="command"><strong>auto-dnssec</strong></span> zone option be set
to <code class="literal">allow</code> or
<code class="literal">maintain</code>,
and also requires the zone to be configured to
(See "Dynamic Update Policies" in the Administrator
Reference Manual for more details.)
</p>
-<p>
- See also <span><strong class="command">rndc loadkeys</strong></span>.
+ See also <span class="command"><strong>rndc loadkeys</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>signing [<span class="optional">( -list | -clear <em class="replaceable"><code>keyid/algorithm</code></em> | -clear <code class="literal">all</code> | -nsec3param ( <em class="replaceable"><code>parameters</code></em> | <code class="literal">none</code> ) | -serial <em class="replaceable"><code>value</code></em> ) </span>] <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] </code></strong></span></dt>
<dd>
-<p>
List, edit, or remove the DNSSEC signing state records
for the specified zone. The status of ongoing DNSSEC
operations (such as signing or generating
NSEC3 chains) is stored in the zone in the form
of DNS resource records of type
- <span><strong class="command">sig-signing-type</strong></span>.
- <span><strong class="command">rndc signing -list</strong></span> converts
+ <span class="command"><strong>sig-signing-type</strong></span>.
+ <span class="command"><strong>rndc signing -list</strong></span> converts
these records into a human-readable form,
indicating which keys are currently signing
or have finished signing the zone, and which NSEC3
chains are being created or removed.
</p>
-<p>
- <span><strong class="command">rndc signing -clear</strong></span> can remove
+ <span class="command"><strong>rndc signing -clear</strong></span> can remove
a single key (specified in the same format that
- <span><strong class="command">rndc signing -list</strong></span> uses to
+ <span class="command"><strong>rndc signing -list</strong></span> uses to
display it), or all keys. In either case, only
completed keys are removed; any record indicating
that a key has not yet finished signing the zone
will be retained.
</p>
-<p>
- <span><strong class="command">rndc signing -nsec3param</strong></span> sets
+ <span class="command"><strong>rndc signing -nsec3param</strong></span> sets
the NSEC3 parameters for a zone. This is the
only supported mechanism for using NSEC3 with
- <span><strong class="command">inline-signing</strong></span> zones.
+ <span class="command"><strong>inline-signing</strong></span> zones.
Parameters are specified in the same format as
an NSEC3PARAM resource record: hash algorithm,
flags, iterations, and salt, in that order.
</p>
-<p>
Currently, the only defined value for hash algorithm
is <code class="literal">1</code>, representing SHA-1.
The <code class="option">flags</code> may be set to
<code class="option">salt</code> is a string of data expressed
in hexadecimal, a hyphen (`-') if no salt is
to be used, or the keyword <code class="literal">auto</code>,
- which causes <span><strong class="command">named</strong></span> to generate a
+ which causes <span class="command"><strong>named</strong></span> to generate a
random 64-bit salt.
</p>
-<p>
So, for example, to create an NSEC3 chain using
the SHA-1 hash algorithm, no opt-out flag,
10 iterations, and a salt value of "FFFF", use:
- <span><strong class="command">rndc signing -nsec3param 1 0 10 FFFF <em class="replaceable"><code>zone</code></em></strong></span>.
+ <span class="command"><strong>rndc signing -nsec3param 1 0 10 FFFF <em class="replaceable"><code>zone</code></em></strong></span>.
To set the opt-out flag, 15 iterations, and no
salt, use:
- <span><strong class="command">rndc signing -nsec3param 1 1 15 - <em class="replaceable"><code>zone</code></em></strong></span>.
+ <span class="command"><strong>rndc signing -nsec3param 1 1 15 - <em class="replaceable"><code>zone</code></em></strong></span>.
</p>
-<p>
- <span><strong class="command">rndc signing -nsec3param none</strong></span>
+ <span class="command"><strong>rndc signing -nsec3param none</strong></span>
removes an existing NSEC3 chain and replaces it
with NSEC.
</p>
-<p>
- <span><strong class="command">rndc signing -serial value</strong></span> sets
+ <span class="command"><strong>rndc signing -serial value</strong></span> sets
the serial number of the zone to value. If the value
would cause the serial number to go backwards it will
be rejected. The primary use is to set the serial on
inline signed zones.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>stats</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Write server statistics to the statistics file.
- (See the <span><strong class="command">statistics-file</strong></span> option in
+ (See the <span class="command"><strong>statistics-file</strong></span> option in
the BIND 9 Administrator Reference Manual.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>status</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Display status of the server.
- Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone
- and the default <span><strong class="command">./IN</strong></span>
+ Note that the number of zones includes the internal <span class="command"><strong>bind/CH</strong></span> zone
+ and the default <span class="command"><strong>./IN</strong></span>
hint zone if there is not an
explicit root zone configured.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>stop [<span class="optional">-p</span>]</code></strong></span></dt>
<dd>
-<p>
Stop the server, making sure any recent changes
made through dynamic update or IXFR are first saved to
the master files of the updated zones.
- If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
- This allows an external process to determine when <span><strong class="command">named</strong></span>
+ If <code class="option">-p</code> is specified <span class="command"><strong>named</strong></span>'s process id is returned.
+ This allows an external process to determine when <span class="command"><strong>named</strong></span>
had completed stopping.
</p>
-<p>See also <span><strong class="command">rndc halt</strong></span>.</p>
-</dd>
+ <p>See also <span class="command"><strong>rndc halt</strong></span>.</p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>sync [<span class="optional">-clean</span>] [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Sync changes in the journal file for a dynamic zone
to the master file. If the "-clean" option is
specified, the journal file is also removed. If
no zone is specified, then all zones are synced.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>thaw [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
<dd>
-<p>
Enable updates to a frozen dynamic zone. If no
zone is specified, then all frozen zones are
enabled. This causes the server to reload the zone
load has completed. After a zone is thawed,
dynamic updates will no longer be refused. If
the zone has changed and the
- <span><strong class="command">ixfr-from-differences</strong></span> option is
+ <span class="command"><strong>ixfr-from-differences</strong></span> option is
in use, then the journal file will be updated to
reflect changes in the zone. Otherwise, if the
zone has changed, any existing journal file will be
removed.
</p>
-<p>See also <span><strong class="command">rndc freeze</strong></span>.</p>
-</dd>
+ <p>See also <span class="command"><strong>rndc freeze</strong></span>.</p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>trace</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Increment the servers debugging level by one.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>trace <em class="replaceable"><code>level</code></em></code></strong></span></dt>
<dd>
-<p>
Sets the server's debugging level to an explicit
value.
</p>
-<p>
- See also <span><strong class="command">rndc notrace</strong></span>.
+ See also <span class="command"><strong>rndc notrace</strong></span>.
</p>
-</dd>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>tsig-delete</code></strong> <em class="replaceable"><code>keyname</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span></dt>
-<dd><p>
+<dd>
+ <p>
Delete a given TKEY-negotiated key from the server.
(This does not apply to statically configured TSIG
keys.)
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>tsig-list</code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
List the names of all TSIG keys currently configured
- for use by <span><strong class="command">named</strong></span> in each view. The
+ for use by <span class="command"><strong>named</strong></span> in each view. The
list both statically configured keys and dynamic
TKEY-negotiated keys.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>validation ( on | off | check ) [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>] </code></strong></span></dt>
-<dd><p>
+<dd>
+ <p>
Enable, disable, or check the current status of
DNSSEC validation.
- Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
+ Note <span class="command"><strong>dnssec-enable</strong></span> also needs to be
set to <strong class="userinput"><code>yes</code></strong> or
<strong class="userinput"><code>auto</code></strong> to be effective.
It defaults to enabled.
- </p></dd>
+ </p>
+ </dd>
<dt><span class="term"><strong class="userinput"><code>zonestatus <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
<dd>
-<p>
Displays the current status of the given zone,
including the master file name and any include
files from which it was loaded, when it was most
management or inline signing, and the scheduled
refresh or expiry times for the zone.
</p>
-<p>
- See also <span><strong class="command">rndc showzone</strong></span>.
+ See also <span class="command"><strong>rndc showzone</strong></span>.
</p>
-</dd>
+ </dd>
</dl></div>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2770679"></a><h2>LIMITATIONS</h2>
-<p>
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.23.10"></a><h2>LIMITATIONS</h2>
+
+ <p>
There is currently no way to provide the shared secret for a
<code class="option">key_id</code> without using the configuration file.
</p>
-<p>
Several error messages could be clearer.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2770697"></a><h2>SEE ALSO</h2>
-<p><span class="citerefentry"><span class="refentrytitle">rndc.conf</span>(5)</span>,
- <span class="citerefentry"><span class="refentrytitle">rndc-confgen</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
- <span class="citerefentry"><span class="refentrytitle">named.conf</span>(5)</span>,
- <span class="citerefentry"><span class="refentrytitle">ndc</span>(8)</span>,
+ </div>
+
+ <div class="refsection">
+<a name="id-1.14.23.11"></a><h2>SEE ALSO</h2>
+
+ <p><span class="citerefentry">
+ <span class="refentrytitle">rndc.conf</span>(5)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">rndc-confgen</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named</span>(8)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">named.conf</span>(5)
+ </span>,
+ <span class="citerefentry">
+ <span class="refentrytitle">ndc</span>(8)
+ </span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
</p>
-</div>
-<div class="refsect1" lang="en">
-<a name="id2770753"></a><h2>AUTHOR</h2>
-<p><span class="corpauthor">Internet Systems Consortium</span>
- </p>
-</div>
+ </div>
+
</div>
<div class="navfooter">
<hr>
</tr>
</table>
</div>
-<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>
-<?xml version="1.0" encoding="utf-8"?>
<!--
- Copyright (C) 2010, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<!-- $Id: managed-keys.xml,v 1.3 2010/02/03 23:49:07 tbox Exp $ -->
-
-<sect1 id="rfc5011.support">
- <title>Dynamic Trust Anchor Management</title>
+<!-- Converted by db4-upgrade version 1.0 -->
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="rfc5011.support"><info><title>Dynamic Trust Anchor Management</title></info>
+
<para>BIND 9.7.0 introduces support for RFC 5011, dynamic trust
anchor management. Using this feature allows
<command>named</command> to keep track of changes to critical
DNSSEC keys without any need for the operator to make changes to
configuration files.</para>
- <sect2>
- <title>Validating Resolver</title>
+ <section><info><title>Validating Resolver</title></info>
+
<!-- TODO: command tag is overloaded for configuration and executables -->
<para>To configure a validating resolver to use RFC 5011 to
maintain a trust anchor, configure the trust anchor using a
<command>managed-keys</command> statement. Information about
this can be found in
- <xref linkend="managed-keys" />.</para>
+ <xref linkend="managed-keys"/>.</para>
<!-- TODO: managed-keys examples
also in DNSSEC section above here in ARM -->
- </sect2>
- <sect2>
- <title>Authoritative Server</title>
+ </section>
+ <section><info><title>Authoritative Server</title></info>
+
<para>To set up an authoritative zone for RFC 5011 trust anchor
maintenance, generate two (or more) key signing keys (KSKs) for
the zone. Sign the zone with one of them; this is the "active"
<para>It is expected that a future release of BIND 9 will
address this problem in a different way, by storing revoked
keys with their original unrevoked key IDs.</para>
- </sect2>
-</sect1>
+ </section>
+</section>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- - Copyright (C) 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
+ - Copyright (C) 2010, 2012-2015 Internet Systems Consortium, Inc. ("ISC")
-
- Permission to use, copy, modify, and/or distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<article xmlns:xi="http://www.w3.org/2001/XInclude">
- <title/>
- <xi:include href="notes.xml"/>
+<!-- Converted by db4-upgrade version 1.0 -->
+<article xmlns="http://docbook.org/ns/docbook" version="5.0"><info><title/></info>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="notes.xml"/>
</article>
-
-<!--
- - Local variables:
- - mode: sgml
- - End:
- -->
--- /dev/null
+TexInputs: ../tex//
+TexStyle: notestyle
+XslParam: ../xsl/notes-param.xsl
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title></title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article" lang="en"><font color="red"><xi:include></xi:include></font></div></body>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article">
+
+ <div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id-1.2"></a>Release Notes for BIND Version 9.11.0pre-alpha</h2></div></div></div>
+
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_intro"></a>Introduction</h3></div></div></div>
+
+ <p>
+ This document summarizes changes since the last production release
+ of BIND on the corresponding major release branch.
+ </p>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_download"></a>Download</h3></div></div></div>
+
+ <p>
+ The latest versions of BIND 9 software can always be found at
+ <a class="ulink" href="http://www.isc.org/downloads/" target="_top">http://www.isc.org/downloads/</a>.
+ There you will find additional information about each release,
+ source code, and pre-compiled versions for Microsoft Windows
+ operating systems.
+ </p>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_security"></a>Security Fixes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ An incorrect boundary check in the OPENPGPKEY rdatatype
+ could trigger an assertion failure. This flaw is disclosed
+ in CVE-2015-5986. [RT #40286]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A buffer accounting error could trigger an assertion failure
+ when parsing certain malformed DNSSEC keys.
+ </p>
+ <p>
+ This flaw was discovered by Hanno Böck of the Fuzzing
+ Project, and is disclosed in CVE-2015-5722. [RT #40212]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A specially crafted query could trigger an assertion failure
+ in message.c.
+ </p>
+ <p>
+ This flaw was discovered by Jonathan Foote, and is disclosed
+ in CVE-2015-5477. [RT #40046]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On servers configured to perform DNSSEC validation, an
+ assertion failure could be triggered on answers from
+ a specially configured server.
+ </p>
+ <p>
+ This flaw was discovered by Breno Silveira Soares, and is
+ disclosed in CVE-2015-4620. [RT #39795]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On servers configured to perform DNSSEC validation using
+ managed trust anchors (i.e., keys configured explicitly
+ via <span class="command"><strong>managed-keys</strong></span>, or implicitly
+ via <span class="command"><strong>dnssec-validation auto;</strong></span> or
+ <span class="command"><strong>dnssec-lookaside auto;</strong></span>), revoking
+ a trust anchor and sending a new untrusted replacement
+ could cause <span class="command"><strong>named</strong></span> to crash with an
+ assertion failure. This could occur in the event of a
+ botched key rollover, or potentially as a result of a
+ deliberate attack if the attacker was in position to
+ monitor the victim's DNS traffic.
+ </p>
+ <p>
+ This flaw was discovered by Jan-Piet Mens, and is
+ disclosed in CVE-2015-1349. [RT #38344]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A flaw in delegation handling could be exploited to put
+ <span class="command"><strong>named</strong></span> into an infinite loop, in which
+ each lookup of a name server triggered additional lookups
+ of more name servers. This has been addressed by placing
+ limits on the number of levels of recursion
+ <span class="command"><strong>named</strong></span> will allow (default 7), and
+ on the number of queries that it will send before
+ terminating a recursive query (default 50).
+ </p>
+ <p>
+ The recursion depth limit is configured via the
+ <code class="option">max-recursion-depth</code> option, and the query limit
+ via the <code class="option">max-recursion-queries</code> option.
+ </p>
+ <p>
+ The flaw was discovered by Florian Maury of ANSSI, and is
+ disclosed in CVE-2014-8500. [RT #37580]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Two separate problems were identified in BIND's GeoIP code that
+ could lead to an assertion failure. One was triggered by use of
+ both IPv4 and IPv6 address families, the other by referencing
+ a GeoIP database in <code class="filename">named.conf</code> which was
+ not installed. Both are covered by CVE-2014-8680. [RT #37672]
+ [RT #37679]
+ </p>
+ <p>
+ A less serious security flaw was also found in GeoIP: changes
+ to the <span class="command"><strong>geoip-directory</strong></span> option in
+ <code class="filename">named.conf</code> were ignored when running
+ <span class="command"><strong>rndc reconfig</strong></span>. In theory, this could allow
+ <span class="command"><strong>named</strong></span> to allow access to unintended clients.
+ </p>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_features"></a>New Features</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ Added support for DynDB, a new interface for loading zone data
+ from an external database, developed by Red Hat for the FreeIPA
+ project. (Thanks in particular to Adam Tkac and Petr
+ Spacek of Red Hat for the contribution.)
+ </p>
+ <p>
+ Unlike the existing DLZ and SDB interfaces, which provide a
+ limited subset of database functionality within BIND —
+ translating DNS queries into real-time database lookups with
+ relatively poor performance and with no ability to handle
+ DNSSEC-signed data — DynDB is able to fully implement
+ and extend the database API used natively by BIND.
+ </p>
+ <p>
+ A DynDB module could pre-load data from an external data
+ source, then serve it with the same performance and
+ functionality as conventional BIND zones, and with the
+ ability to take advantage of database features not
+ available in BIND, such as multi-master replication.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ New quotas have been added to limit the queries that are
+ sent by recursive resolvers to authoritative servers
+ experiencing denial-of-service attacks. When configured,
+ these options can both reduce the harm done to authoritative
+ servers and also avoid the resource exhaustion that can be
+ experienced by recursives when they are being used as a
+ vehicle for such an attack.
+ </p>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
+<li class="listitem">
+ <p>
+ <code class="option">fetches-per-server</code> limits the number of
+ simultaneous queries that can be sent to any single
+ authoritative server. The configured value is a starting
+ point; it is automatically adjusted downward if the server is
+ partially or completely non-responsive. The algorithm used to
+ adjust the quota can be configured via the
+ <code class="option">fetch-quota-params</code> option.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <code class="option">fetches-per-zone</code> limits the number of
+ simultaneous queries that can be sent for names within a
+ single domain. (Note: Unlike "fetches-per-server", this
+ value is not self-tuning.)
+ </p>
+ </li>
+</ul></div>
+ <p>
+ Statistics counters have also been added to track the number
+ of queries affected by these quotas.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Added support for <span class="command"><strong>dnstap</strong></span>, a fast,
+ flexible method for capturing and logging DNS traffic,
+ developed by Robert Edmonds at Farsight Security, Inc.,
+ whose assistance is gratefully acknowledged.
+ </p>
+ <p>
+ To enable <span class="command"><strong>dnstap</strong></span> at compile time,
+ the <span class="command"><strong>fstrm</strong></span> and <span class="command"><strong>protobuf-c</strong></span>
+ libraries must be available, and BIND must be configured with
+ <code class="option">--enable-dnstap</code>.
+ </p>
+ <p>
+ A new utility <span class="command"><strong>dnstap-read</strong></span> has been added
+ to allow <span class="command"><strong>dnstap</strong></span> data to be presented in
+ a human-readable format.
+ </p>
+ <p>
+ For more information on <span class="command"><strong>dnstap</strong></span>, see
+ <a class="ulink" href="http://dnstap.info" target="_top">http://dnstap.info</a>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ New statistics counters have been added to track traffic
+ sizes, as specified in RSSAC002. Query and response
+ message sizes are broken up into ranges of histogram buckets:
+ TCP and UDP queries of size 0-15, 16-31, ..., 272-288, and 288+,
+ and TCP and UDP responses of size 0-15, 16-31, ..., 4080-4095,
+ and 4096+. These values can be accessed via the XML and JSON
+ statistics channels at, for example,
+ <a class="ulink" href="http://localhost:8888/xml/v3/traffic" target="_top">http://localhost:8888/xml/v3/traffic</a>
+ or
+ <a class="ulink" href="http://localhost:8888/json/v1/traffic" target="_top">http://localhost:8888/json/v1/traffic</a>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The serial number of a dynamically updatable zone can
+ now be set using
+ <span class="command"><strong>rndc signing -serial <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>zonename</code></em></strong></span>.
+ This is particularly useful with <code class="option">inline-signing</code>
+ zones that have been reset. Setting the serial number to a value
+ larger than that on the slaves will trigger an AXFR-style
+ transfer.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When answering recursive queries, SERVFAIL responses can now be
+ cached by the server for a limited time; subsequent queries for
+ the same query name and type will return another SERVFAIL until
+ the cache times out. This reduces the frequency of retries
+ when a query is persistently failing, which can be a burden
+ on recursive serviers. The SERVFAIL cache timeout is controlled
+ by <code class="option">servfail-ttl</code>, which defaults to 10 seconds
+ and has an upper limit of 30.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The new <span class="command"><strong>rndc nta</strong></span> command can now be used to
+ set a "negative trust anchor" (NTA), disabling DNSSEC validation for
+ a specific domain; this can be used when responses from a domain
+ are known to be failing validation due to administrative error
+ rather than because of a spoofing attack. NTAs are strictly
+ temporary; by default they expire after one hour, but can be
+ configured to last up to one week. The default NTA lifetime
+ can be changed by setting the <code class="option">nta-lifetime</code> in
+ <code class="filename">named.conf</code>. When added, NTAs are stored in a
+ file (<code class="filename"><em class="replaceable"><code>viewname</code></em>.nta</code>)
+ in order to persist across restarts of the <span class="command"><strong>named</strong></span> server.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The EDNS Client Subnet (ECS) option is now supported for
+ authoritative servers; if a query contains an ECS option then
+ ACLs containing <code class="option">geoip</code> or <code class="option">ecs</code>
+ elements can match against the the address encoded in the option.
+ This can be used to select a view for a query, so that different
+ answers can be provided depending on the client network.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The EDNS EXPIRE option has been implemented on the client
+ side, allowing a slave server to set the expiration timer
+ correctly when transferring zone data from another slave
+ server.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A new <code class="option">masterfile-style</code> zone option controls
+ the formatting of text zone files: When set to
+ <code class="literal">full</code>, the zone file will dumped in
+ single-line-per-record format.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +ednsopt</strong></span> can now be used to set
+ arbitrary EDNS options in DNS requests.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +ednsflags</strong></span> can now be used to set
+ yet-to-be-defined EDNS flags in DNS requests.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +[no]ednsnegotiation</strong></span> can now be used enable /
+ disable EDNS version negotiation.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +header-only</strong></span> can now be used to send
+ queries without a question section.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +ttlunits</strong></span> causes <span class="command"><strong>dig</strong></span>
+ to print TTL values with time-unit suffixes: w, d, h, m, s for
+ weeks, days, hours, minutes, and seconds.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +zflag</strong></span> can be used to set the last
+ unassigned DNS header flag bit. This bit in normally zero.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig +dscp=<em class="replaceable"><code>value</code></em></strong></span>
+ can now be used to set the DSCP code point in outgoing query
+ packets.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <code class="option">serial-update-method</code> can now be set to
+ <code class="literal">date</code>. On update, the serial number will
+ be set to the current date in YYYYMMDDNN format.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dnssec-signzone -N date</strong></span> also sets the serial
+ number to YYYYMMDDNN.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>named -L <em class="replaceable"><code>filename</code></em></strong></span>
+ causes <span class="command"><strong>named</strong></span> to send log messages to the specified file by
+ default instead of to the system log.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The rate limiter configured by the
+ <code class="option">serial-query-rate</code> option no longer covers
+ NOTIFY messages; those are now separately controlled by
+ <code class="option">notify-rate</code> and
+ <code class="option">startup-notify-rate</code> (the latter of which
+ controls the rate of NOTIFY messages sent when the server
+ is first started up or reconfigured).
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The default number of tasks and client objects available
+ for serving lightweight resolver queries have been increased,
+ and are now configurable via the new <code class="option">lwres-tasks</code>
+ and <code class="option">lwres-clients</code> options in
+ <code class="filename">named.conf</code>. [RT #35857]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Log output to files can now be buffered by specifying
+ <span class="command"><strong>buffered yes;</strong></span> when creating a channel.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>delv +tcp</strong></span> will exclusively use TCP when
+ sending queries.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>named</strong></span> will now check to see whether
+ other name server processes are running before starting up.
+ This is implemented in two ways: 1) by refusing to start
+ if the configured network interfaces all return "address
+ in use", and 2) by attempting to acquire a lock on a file
+ specified by the <code class="option">lock-file</code> option or
+ the <span class="command"><strong>-X</strong></span> command line option. The
+ default lock file is
+ <code class="filename">/var/run/named/named.lock</code>.
+ Specifying <code class="literal">none</code> will disable the lock
+ file check.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>rndc delzone</strong></span> can now be applied to zones
+ which were configured in <code class="filename">named.conf</code>;
+ it is no longer restricted to zones which were added by
+ <span class="command"><strong>rndc addzone</strong></span>. (Note, however, that
+ this does not edit <code class="filename">named.conf</code>; the zone
+ must be removed from the configuration or it will return
+ when <span class="command"><strong>named</strong></span> is restarted or reloaded.)
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>rndc modzone</strong></span> can be used to reconfigure
+ a zone, using similar syntax to <span class="command"><strong>rndc addzone</strong></span>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ <span class="command"><strong>rndc showzone</strong></span> displays the current
+ configuration for a specified zone.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Added server-side support for pipelined TCP queries. Clients
+ may continue sending queries via TCP while previous queries are
+ processed in parallel. Responses are sent when they are
+ ready, not necessarily in the order in which the queries were
+ received.
+ </p>
+ <p>
+ To revert to the former behavior for a particular
+ client address or range of addresses, specify the address prefix
+ in the "keep-response-order" option. To revert to the former
+ behavior for all clients, use "keep-response-order { any; };".
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The new <span class="command"><strong>mdig</strong></span> command is a version of
+ <span class="command"><strong>dig</strong></span> that sends multiple pipelined
+ queries and then waits for responses, instead of sending one
+ query and waiting the response before sending the next. [RT #38261]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ To enable better monitoring and troubleshooting of RFC 5011
+ trust anchor management, the new <span class="command"><strong>rndc managed-keys</strong></span>
+ can be used to check status of trust anchors or to force keys
+ to be refreshed. Also, the managed-keys data file now has
+ easier-to-read comments. [RT #38458]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ An <span class="command"><strong>--enable-querytrace</strong></span> configure switch is
+ now available to enable very verbose query tracelogging. This
+ option can only be set at compile time. This option has a
+ negative performance impact and should be used only for
+ debugging. [RT #37520]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A new <span class="command"><strong>tcp-only</strong></span> option can be specified
+ in <span class="command"><strong>server</strong></span> statements to force
+ <span class="command"><strong>named</strong></span> to connect to the specified
+ server via TCP. [RT #37800]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The <span class="command"><strong>nxdomain-redirect</strong></span> option specifies
+ a DNS namespace to use for NXDOMAIN redirection. When a
+ recursive lookup returns NXDOMAIN, a second lookup is
+ initiated with the specified name appended to the query
+ name. This allows NXDOMAIN redirection data to be supplied
+ by multiple zones configured on the server or by recursive
+ queries to other servers. (The older method, using
+ a single <span class="command"><strong>type redirect</strong></span> zone, has
+ better average performance but is less flexible.) [RT #37989]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The following types have been implemented: CSYNC, NINFO, RKEY,
+ SINK, TA, TALINK.
+ </p>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_changes"></a>Feature Changes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ ACLs containing <span class="command"><strong>geoip asnum</strong></span> elements were
+ not correctly matched unless the full organization name was
+ specified in the ACL (as in
+ <span class="command"><strong>geoip asnum "AS1234 Example, Inc.";</strong></span>).
+ They can now match against the AS number alone (as in
+ <span class="command"><strong>geoip asnum "AS1234";</strong></span>).
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When using native PKCS#11 cryptography (i.e.,
+ <span class="command"><strong>configure --enable-native-pkcs11</strong></span>) HSM PINs
+ of up to 256 characters can now be used.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ NXDOMAIN responses to queries of type DS are now cached separately
+ from those for other types. This helps when using "grafted" zones
+ of type forward, for which the parent zone does not contain a
+ delegation, such as local top-level domains. Previously a query
+ of type DS for such a zone could cause the zone apex to be cached
+ as NXDOMAIN, blocking all subsequent queries. (Note: This
+ change is only helpful when DNSSEC validation is not enabled.
+ "Grafted" zones without a delegation in the parent are not a
+ recommended configuration.)
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Update forwarding performance has been improved by allowing
+ a single TCP connection to be shared between multiple updates.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ By default, <span class="command"><strong>nsupdate</strong></span> will now check
+ the correctness of hostnames when adding records of type
+ A, AAAA, MX, SOA, NS, SRV or PTR. This behavior can be
+ disabled with <span class="command"><strong>check-names no</strong></span>.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Added support for OPENPGPKEY type.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The names of the files used to store managed keys and added
+ zones for each view are no longer based on the SHA256 hash
+ of the view name, except when this is necessary because the
+ view name contains characters that would be incompatible with use
+ as a file name. For views whose names do not contain forward
+ slashes ('/'), backslashes ('\'), or capital letters - which
+ could potentially cause namespace collision problems on
+ case-insensitive filesystems - files will now be named
+ after the view (for example, <code class="filename">internal.mkeys</code>
+ or <code class="filename">external.nzf</code>). However, to ensure
+ consistent behavior when upgrading, if a file using the old
+ name format is found to exist, it will continue to be used.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ "rndc" can now return text output of arbitrary size to
+ the caller. (Prior to this, certain commands such as
+ "rndc tsig-list" and "rndc zonestatus" could return
+ truncated output.)
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Errors reported when running <span class="command"><strong>rndc addzone</strong></span>
+ (e.g., when a zone file cannot be loaded) have been clarified
+ to make it easier to diagnose problems.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When encountering an authoritative name server whose name is
+ an alias pointing to another name, the resolver treats
+ this as an error and skips to the next server. Previously
+ this happened silently; now the error will be logged to
+ the newly-created "cname" log category.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ If <span class="command"><strong>named</strong></span> is not configured to validate the answer then
+ allow fallback to plain DNS on timeout even when we know
+ the server supports EDNS. This will allow the server to
+ potentially resolve signed queries when TCP is being
+ blocked.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Large inline-signing changes should be less disruptive.
+ Signature generation is now done incrementally; the number
+ of signatures to be generated in each quantum is controlled
+ by "sig-signing-signatures <em class="replaceable"><code>number</code></em>;".
+ [RT #37927]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The experimental SIT option (code point 65001) of BIND
+ 9.10.0 through BIND 9.10.2 has been replaced with the COOKIE
+ option (code point 10). It is no longer experimental, and
+ is sent by default, by both <span class="command"><strong>named</strong></span> and
+ <span class="command"><strong>dig</strong></span>.
+ </p>
+ <p>
+ The SIT-related named.conf options have been marked as
+ obsolete, and are otherwise ignored.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When <span class="command"><strong>dig</strong></span> receives a truncated (TC=1)
+ response or a BADCOOKIE response code from a server, it
+ will automatically retry the query using the server COOKIE
+ that was returned by the server in its initial response.
+ [RT #39047]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A alternative NXDOMAIN redirect method (nxdomain-redirect)
+ which allows the redirect information to be looked up from
+ a namespace on the Internet rather than requiring a zone
+ to be configured on the server is now available.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Retrieving the local port range from net.ipv4.ip_local_port_range
+ on Linux is now supported.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Within the <code class="option">response-policy</code> option, it is now
+ possible to configure RPZ rewrite logging on a per-zone basis
+ using the <code class="option">log</code> clause.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The default preferred glue is now the address type of the
+ transport the query was received over.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On machines with 2 or more processors (CPU), the default value
+ for the number of UDP listeners has been changed to the number
+ of detected processors minus one.
+ </p>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_port"></a>Porting Changes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ <p>
+ The Microsoft Windows install tool
+ <span class="command"><strong>BINDInstall.exe</strong></span> which requires a
+ non-free version of Visual Studio to be built, now uses two
+ files (lists of flags and files) created by the Configure
+ perl script with all the needed information which were
+ previously compiled in the binary. Read
+ <code class="filename">win32utils/build.txt</code> for more details.
+ [RT #38915]
+ </p>
+ </li></ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_bugs"></a>Bug Fixes</h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ <span class="command"><strong>dig</strong></span>, <span class="command"><strong>host</strong></span> and
+ <span class="command"><strong>nslookup</strong></span> aborted when encountering
+ a name which, after appending search list elements,
+ exceeded 255 bytes. Such names are now skipped, but
+ processing of other names will continue. [RT #36892]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The error message generated when
+ <span class="command"><strong>named-checkzone</strong></span> or
+ <span class="command"><strong>named-checkconf -z</strong></span> encounters a
+ <code class="option">$TTL</code> directive without a value has
+ been clarified. [RT #37138]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Semicolon characters (;) included in TXT records were
+ incorrectly escaped with a backslash when the record was
+ displayed as text. This is actually only necessary when there
+ are no quotation marks. [RT #37159]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When files opened for writing by <span class="command"><strong>named</strong></span>,
+ such as zone journal files, were referenced more than once
+ in <code class="filename">named.conf</code>, it could lead to file
+ corruption as multiple threads wrote to the same file. This
+ is now detected when loading <code class="filename">named.conf</code>
+ and reported as an error. [RT #37172]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When checking for updates to trust anchors listed in
+ <code class="option">managed-keys</code>, <span class="command"><strong>named</strong></span>
+ now revalidates keys based on the current set of
+ active trust anchors, without relying on any cached
+ record of previous validation. [RT #37506]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Large-system tuning
+ (<span class="command"><strong>configure --with-tuning=large</strong></span>) caused
+ problems on some platforms by setting a socket receive
+ buffer size that was too large. This is now detected and
+ corrected at run time. [RT #37187]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ When NXDOMAIN redirection is in use, queries for a name
+ that is present in the redirection zone but a type that
+ is not present will now return NOERROR instead of NXDOMAIN.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Due to an inadvertent removal of code in the previous
+ release, when <span class="command"><strong>named</strong></span> encountered an
+ authoritative name server which dropped all EDNS queries,
+ it did not always try plain DNS. This has been corrected.
+ [RT #37965]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A regression caused nsupdate to use the default recursive servers
+ rather than the SOA MNAME server when sending the UPDATE.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Adjusted max-recursion-queries to accommodate the smaller
+ initial packet sizes used in BIND 9.10 and higher when
+ contacting authoritative servers for the first time.
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Built-in "empty" zones did not correctly inherit the
+ "allow-transfer" ACL from the options or view. [RT #38310]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Two leaks were fixed that could cause <span class="command"><strong>named</strong></span>
+ processes to grow to very large sizes. [RT #38454]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Fixed some bugs in RFC 5011 trust anchor management,
+ including a memory leak and a possible loss of state
+ information. [RT #38458]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Asynchronous zone loads were not handled correctly when the
+ zone load was already in progress; this could trigger a crash
+ in zt.c. [RT #37573]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A race during shutdown or reconfiguration could
+ cause an assertion failure in mem.c. [RT #38979]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Some answer formatting options didn't work correctly with
+ <span class="command"><strong>dig +short</strong></span>. [RT #39291]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ Several bugs have been fixed in the RPZ implementation:
+ </p>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
+<li class="listitem">
+ <p>
+ Policy zones that did not specifically require recursion
+ could be treated as if they did; consequently, setting
+ <span class="command"><strong>qname-wait-recurse no;</strong></span> was
+ sometimes ineffective. This has been corrected.
+ In most configurations, behavioral changes due to this
+ fix will not be noticeable. [RT #39229]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The server could crash if policy zones were updated (e.g.
+ via <span class="command"><strong>rndc reload</strong></span> or an incoming zone
+ transfer) while RPZ processing was still ongoing for an
+ active query. [RT #39415]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ On servers with one or more policy zones configured as
+ slaves, if a policy zone updated during regular operation
+ (rather than at startup) using a full zone reload, such as
+ via AXFR, a bug could allow the RPZ summary data to fall out
+ of sync, potentially leading to an assertion failure in
+ rpz.c when further incremental updates were made to the
+ zone, such as via IXFR. [RT #39567]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The server could match a shorter prefix than what was
+ available in CLIENT-IP policy triggers, and so, an
+ unexpected action could be taken. This has been
+ corrected. [RT #39481]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ The server could crash if a reload of an RPZ zone was
+ initiated while another reload of the same zone was
+ already in progress. [RT #39649]
+ </p>
+ </li>
+</ul></div>
+ </li>
+</ul></div>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="end_of_life"></a>End of Life</h3></div></div></div>
+
+ <p>
+ The end of life for BIND 9.11 is yet to be determined but
+ will not be before BIND 9.13.0 has been released for 6 months.
+ <a class="ulink" href="https://www.isc.org/downloads/software-support-policy/" target="_top">https://www.isc.org/downloads/software-support-policy/</a>
+ </p>
+ </div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes_thanks"></a>Thank You</h3></div></div></div>
+
+ <p>
+ Thank you to everyone who assisted us in making this release possible.
+ If you would like to contribute to ISC to assist us in continuing to
+ make quality open source software, please visit our donations page at
+ <a class="ulink" href="http://www.isc.org/donate/" target="_top">http://www.isc.org/donate/</a>.
+ </p>
+ </div>
+</div>
+</div></body>
</html>
-<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE book [
+<!ENTITY Scaron "Š">
+<!ENTITY ccaron "č">
+<!ENTITY mdash "—">
+<!ENTITY ouml "ö">]>
<!--
- Copyright (C) 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<sect1 xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:include href="noteversion.xml"/>
- <sect2 id="relnotes_intro">
- <title>Introduction</title>
+<!-- Converted by db4-upgrade version 1.0 -->
+<section xmlns="http://docbook.org/ns/docbook" version="5.0"><info/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="noteversion.xml"/>
+ <section xml:id="relnotes_intro"><info><title>Introduction</title></info>
+
<para>
This document summarizes changes since the last production release
of BIND on the corresponding major release branch.
</para>
- </sect2>
- <sect2 id="relnotes_download">
- <title>Download</title>
+ </section>
+ <section xml:id="relnotes_download"><info><title>Download</title></info>
+
<para>
The latest versions of BIND 9 software can always be found at
- <ulink url="http://www.isc.org/downloads/"
- >http://www.isc.org/downloads/</ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.isc.org/downloads/">http://www.isc.org/downloads/</link>.
There you will find additional information about each release,
source code, and pre-compiled versions for Microsoft Windows
operating systems.
</para>
- </sect2>
- <sect2 id="relnotes_security">
- <title>Security Fixes</title>
+ </section>
+ <section xml:id="relnotes_security"><info><title>Security Fixes</title></info>
+
<itemizedlist>
<listitem>
<para>
when parsing certain malformed DNSSEC keys.
</para>
<para>
- This flaw was discovered by Hanno B쎶ck of the Fuzzing
+ This flaw was discovered by Hanno Böck of the Fuzzing
Project, and is disclosed in CVE-2015-5722. [RT #40212]
</para>
</listitem>
</para>
</listitem>
</itemizedlist>
- </sect2>
- <sect2 id="relnotes_features">
- <title>New Features</title>
+ </section>
+ <section xml:id="relnotes_features"><info><title>New Features</title></info>
+
<itemizedlist>
<listitem>
<para>
Added support for DynDB, a new interface for loading zone data
from an external database, developed by Red Hat for the FreeIPA
project. (Thanks in particular to Adam Tkac and Petr
- Špaček of Red Hat for the contribution.)
+ Spacek of Red Hat for the contribution.)
</para>
<para>
Unlike the existing DLZ and SDB interfaces, which provide a
</para>
<para>
For more information on <command>dnstap</command>, see
- <ulink url="http://dnstap.info">http://dnstap.info</ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://dnstap.info">http://dnstap.info</link>.
</para>
</listitem>
<listitem>
and TCP and UDP responses of size 0-15, 16-31, ..., 4080-4095,
and 4096+. These values can be accessed via the XML and JSON
statistics channels at, for example,
- <ulink url="http://localhost:8888/xml/v3/traffic"
- >http://localhost:8888/xml/v3/traffic</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://localhost:8888/xml/v3/traffic">http://localhost:8888/xml/v3/traffic</link>
or
- <ulink url="http://localhost:8888/json/v1/traffic"
- >http://localhost:8888/json/v1/traffic</ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://localhost:8888/json/v1/traffic">http://localhost:8888/json/v1/traffic</link>.
</para>
</listitem>
<listitem>
</para>
</listitem>
</itemizedlist>
- </sect2>
- <sect2 id="relnotes_changes">
- <title>Feature Changes</title>
+ </section>
+ <section xml:id="relnotes_changes"><info><title>Feature Changes</title></info>
+
<itemizedlist>
<listitem>
<para>
</para>
</listitem>
</itemizedlist>
- </sect2>
- <sect2 id="relnotes_port">
- <title>Porting Changes</title>
+ </section>
+ <section xml:id="relnotes_port"><info><title>Porting Changes</title></info>
+
<itemizedlist>
<listitem>
<para>
</para>
</listitem>
</itemizedlist>
- </sect2>
- <sect2 id="relnotes_bugs">
- <title>Bug Fixes</title>
+ </section>
+ <section xml:id="relnotes_bugs"><info><title>Bug Fixes</title></info>
+
<itemizedlist>
<listitem>
<para>
</itemizedlist>
</listitem>
</itemizedlist>
- </sect2>
- <sect2 id="end_of_life">
- <title>End of Life</title>
+ </section>
+ <section xml:id="end_of_life"><info><title>End of Life</title></info>
+
<para>
The end of life for BIND 9.11 is yet to be determined but
will not be before BIND 9.13.0 has been released for 6 months.
- <ulink url="https://www.isc.org/downloads/software-support-policy/"
- >https://www.isc.org/downloads/software-support-policy/</ulink>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://www.isc.org/downloads/software-support-policy/">https://www.isc.org/downloads/software-support-policy/</link>
</para>
- </sect2>
- <sect2 id="relnotes_thanks">
- <title>Thank You</title>
+ </section>
+ <section xml:id="relnotes_thanks"><info><title>Thank You</title></info>
+
<para>
Thank you to everyone who assisted us in making this release possible.
If you would like to contribute to ISC to assist us in continuing to
make quality open source software, please visit our donations page at
- <ulink url="http://www.isc.org/donate/"
- >http://www.isc.org/donate/</ulink>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.isc.org/donate/">http://www.isc.org/donate/</link>.
</para>
- </sect2>
-</sect1>
+ </section>
+</section>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2010, 2012-2015 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<sect1 id="pkcs11">
- <title>PKCS#11 (Cryptoki) support</title>
+<!-- Converted by db4-upgrade version 1.0 -->
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="pkcs11"><info><title>PKCS#11 (Cryptoki) support</title></info>
+
<para>
PKCS#11 (Public Key Cryptography Standard #11) defines a
platform-independent API for the control of hardware security
OpenSSL completely; BIND loads the provider library itself, and uses
the PKCS#11 API to drive the HSM directly.
</para>
- <sect2>
- <title>Prerequisites</title>
+ <section><info><title>Prerequisites</title></info>
+
<para>
See the documentation provided by your HSM vendor for
information about installing, initializing, testing and
troubleshooting the HSM.
</para>
- </sect2>
- <sect2>
- <title>Native PKCS#11</title>
+ </section>
+ <section><info><title>Native PKCS#11</title></info>
+
<para>
Native PKCS#11 mode will only work with an HSM capable of carrying
out <emphasis>every</emphasis> cryptographic operation BIND 9 may
<command>dnssec-*</command> tools, or the <option>-m</option> in
the <command>pkcs11-*</command> tools.)
</para>
- <sect3>
- <title>Building SoftHSMv2</title>
+ <section><info><title>Building SoftHSMv2</title></info>
+
<para>
SoftHSMv2, the latest development version of SoftHSM, is available
from
- <ulink url="https://github.com/opendnssec/SoftHSMv2">
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://github.com/opendnssec/SoftHSMv2">
https://github.com/opendnssec/SoftHSMv2
- </ulink>.
+ </link>.
It is a software library developed by the OpenDNSSEC project
- (<ulink url="http://www.opendnssec.org">
+ (<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.opendnssec.org">
http://www.opendnssec.org
- </ulink>)
+ </link>)
which provides a PKCS#11 interface to a virtual HSM, implemented in
the form of a SQLite3 database on the local filesystem. It provides
less security than a true HSM, but it allows you to experiment with
$ <userinput> make install </userinput>
$ <userinput> /opt/pkcs11/usr/bin/softhsm-util --init-token 0 --slot 0 --label softhsmv2 </userinput>
</screen>
- </sect3>
- </sect2>
- <sect2>
- <title>OpenSSL-based PKCS#11</title>
+ </section>
+ </section>
+ <section><info><title>OpenSSL-based PKCS#11</title></info>
+
<para>
OpenSSL-based PKCS#11 mode uses a modified version of the
OpenSSL library; stock OpenSSL does not fully support PKCS#11.
necessary to build OpenSSL with the patch in place, and configure
it with the path to your HSM's PKCS#11 provider library.
</para>
- <sect3>
- <title>Patching OpenSSL</title>
+ <section><info><title>Patching OpenSSL</title></info>
+
<screen>
-$ <userinput>wget <ulink>http://www.openssl.org/source/openssl-0.9.8zc.tar.gz</ulink></userinput>
+$ <userinput>wget <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="">http://www.openssl.org/source/openssl-0.9.8zc.tar.gz</link></userinput>
</screen>
<para>Extract the tarball:</para>
<screen>
Later, when building BIND 9, the location of the custom-built
OpenSSL library will need to be specified via configure.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section><info><title>Building OpenSSL for the AEP Keyper on Linux</title></info>
<!-- Example 1 -->
- <title>Building OpenSSL for the AEP Keyper on Linux</title>
+
<para>
The AEP Keyper is a highly secure key storage device,
but does not provide hardware cryptographic acceleration. It
test</command>" fails with "pthread_atfork() not found", you forgot to
add the -pthread above.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section><info><title>Building OpenSSL for the SCA 6000 on Solaris</title></info>
<!-- Example 2 -->
- <title>Building OpenSSL for the SCA 6000 on Solaris</title>
+
<para>
The SCA-6000 PKCS#11 provider is installed as a system
library, libpkcs11. It is a true crypto accelerator, up to 4
<command>make</command> and
<command>make test</command>.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section><info><title>Building OpenSSL for SoftHSM</title></info>
<!-- Example 3 -->
- <title>Building OpenSSL for SoftHSM</title>
+
<para>
SoftHSM (version 1) is a software library developed by the
OpenDNSSEC project
- (<ulink url="http://www.opendnssec.org">
+ (<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.opendnssec.org">
http://www.opendnssec.org
- </ulink>)
+ </link>)
which provides a
PKCS#11 interface to a virtual HSM, implemented in the form of
a SQLite3 database on the local filesystem. SoftHSM uses
$ <userinput> make </userinput>
$ <userinput> make install </userinput>
$ <userinput> export SOFTHSM_CONF=/opt/pkcs11/softhsm.conf </userinput>
-$ <userinput> echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF </userinput>
+$ <userinput> echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF </userinput>
$ <userinput> /opt/pkcs11/usr/bin/softhsm --init-token 0 --slot 0 --label softhsm </userinput>
</screen>
<para>
After configuring, run "<command>make</command>"
and "<command>make test</command>".
</para>
- </sect3>
+ </section>
<para>
Once you have built OpenSSL, run
"<command>apps/openssl engine pkcs11</command>" to confirm
"<command>make install</command>" which will install the
modified OpenSSL suite to <filename>/opt/pkcs11/usr</filename>.
</para>
- <sect3>
+ <section><info><title>Configuring BIND 9 for Linux with the AEP Keyper</title></info>
<!-- Example 4 -->
- <title>Configuring BIND 9 for Linux with the AEP Keyper</title>
+
<para>
To link with the PKCS#11 provider, threads must be
enabled in the BIND 9 build.
--with-openssl=/opt/pkcs11/usr \
--with-pkcs11=/opt/pkcs11/usr/lib/libpkcs11.so</userinput>
</screen>
- </sect3>
- <sect3>
+ </section>
+ <section><info><title>Configuring BIND 9 for Solaris with the SCA 6000</title></info>
<!-- Example 5 -->
- <title>Configuring BIND 9 for Solaris with the SCA 6000</title>
+
<para>
To link with the PKCS#11 provider, threads must be
enabled in the BIND 9 build.
same as the --prefix argument to the OpenSSL
Configure).
</para>
- </sect3>
- <sect3>
+ </section>
+ <section><info><title>Configuring BIND 9 for SoftHSM</title></info>
<!-- Example 6 -->
- <title>Configuring BIND 9 for SoftHSM</title>
+
<screen>
$ <userinput>cd ../bind9</userinput>
$ <userinput>./configure --enable-threads \
--with-openssl=/opt/pkcs11/usr \
--with-pkcs11=/opt/pkcs11/usr/lib/libsofthsm.so</userinput>
</screen>
- </sect3>
+ </section>
<para>
After configuring, run
"<command>make</command>",
(Note: If "make test" fails in the "pkcs11" system test, you may
have forgotten to set the SOFTHSM_CONF environment variable.)
</para>
- </sect2>
- <sect2>
- <title>PKCS#11 Tools</title>
+ </section>
+ <section><info><title>PKCS#11 Tools</title></info>
+
<para>
BIND 9 includes a minimal set of tools to operate the
HSM, including
PKCS11_PROVIDER environment variable to specify the path to the
provider.)
</para>
- </sect2>
- <sect2>
- <title>Using the HSM</title>
+ </section>
+ <section><info><title>Using the HSM</title></info>
+
<para>
For OpenSSL-based PKCS#11, we must first set up the runtime
environment so the OpenSSL and PKCS#11 libraries can be loaded:
Algorithm: NSEC3RSASHA1: ZSKs: 1, KSKs: 1 active, 0 revoked, 0 stand-by
example.net.signed
</screen>
- </sect2>
- <sect2>
- <title>Specifying the engine on the command line</title>
+ </section>
+ <section><info><title>Specifying the engine on the command line</title></info>
+
<para>
When using OpenSSL-based PKCS#11, the "engine" to be used by
OpenSSL can be specified in <command>named</command> and all of
different meaning: it specifies the path to the PKCS#11 provider
library. This may be useful when testing a new provider library.
</para>
- </sect2>
- <sect2>
- <title>Running named with automatic zone re-signing</title>
+ </section>
+ <section><info><title>Running named with automatic zone re-signing</title></info>
+
<para>
If you want <command>named</command> to dynamically re-sign zones
using HSM keys, and/or to to sign new records inserted via nsupdate,
do before configuring the system in this way.
</para>
</warning>
- </sect2>
-</sect1>
+ </section>
+</section>
--- /dev/null
+armstyle.sty
-#!/usr/bin/perl -w
-#
-# Copyright (C) 2015 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2005, 2007, 2012, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
#
# Permission to use, copy, modify, and/or distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
# PERFORMANCE OF THIS SOFTWARE.
-while (<>) {
- s/쎶/ö/;
- print;
-}
+srcdir = @srcdir@
+VPATH = @srcdir@
+top_srcdir = @top_srcdir@
+
+SUBDIRS =
+TARGETS =
+
+@BIND9_MAKE_RULES@
+
+distclean::
+ rm -f armstyle.sty
--- /dev/null
+%%
+%% This style is derivated from the docbook one
+%%
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{armstyle}[]
+
+%% Just use the original package and pass the options
+\RequirePackageWithOptions{db2latex}
+
+% 2015-09-03 reed -- used with figure
+\usepackage{float}
+
+% For page layout
+\usepackage{geometry}
+
+% don't want date on the cover page
+\let\@date\@empty
+
+% get rid of "Chapter" on start of each chapter
+\def\@makechapterhead#1{%
+ \vspace*{50\p@}%
+ {\parindent \z@ \raggedright \normalfont
+ \ifnum \c@secnumdepth >\m@ne
+ \if@mainmatter
+ \Huge\bfseries\sffamily \thechapter\space\space\space\space%
+ \fi
+ \fi
+ \interlinepenalty\@M
+ \Huge \bfseries \sffamily #1\par\nobreak
+ \vskip 40\p@
+ }}
+
+% for use of \titleformat
+\usepackage{titlesec}
+
+\titleformat*{\section}{\Large\bfseries\scshape\sffamily}
+\titleformat*{\subsection}{\large\bfseries\sffamily}
+
+% Contents font too ; note I don't know what last parts of this are for
+\titleformat{\chapter}{\Huge\bfseries\sffamily}{\thechapter}{1em}{} \vspace{6pt}
+
+% font for the Index headline also
+\titleformat{\index}{\Huge\bfseries\sffamily}{Index}{1em}{} \vspace{6pt}
+
+% following two lines for no indenting paragraphs and spacing between
+\setlength\parskip{\medskipamount}
+\setlength\parindent{0pt}
+
+% fancy footers
+\pagestyle{fancy}
+\fancyfoot[ce,co]{\thepage}
+\fancyfoot[le,ro]{@BIND9_VERSIONSHORT@}
+\renewcommand{\headrulewidth}{0.4 pt}
+\fancypagestyle{plain}{%
+ \fancyhf{}%
+ \fancyfoot[ce,co]{\thepage}%
+ \fancyfoot[le,ro]{@BIND9_VERSIONSHORT@}
+ \renewcommand{\headrulewidth}{0 pt}
+}
+\fancypagestyle{empty}{%
+ \fancyhf{}%
+ \renewcommand{\headrulewidth}{0 pt}
+ \renewcommand{\footrulewidth}{0 pt}
+}
+
+% custom title and copyright pages
+\def\maketitle{
+ \thispagestyle{empty}
+ \null\vfil
+ \vskip 60pt
+ \begin{center}%
+ { %\LARGE
+ \Huge
+ \bfseries
+ \DBKtitle \\
+ \par
+ }
+ \vskip 3em%
+ { %\large
+ \Large
+ \lineskip .75em%
+ @BIND9_VERSIONSTRING@
+ \par
+ }
+ \vfil\null
+ % Not sure exactly how much to trim logo, but given that
+ % this is a centered environment, we need not be too precise
+ % so long as the image is centered in the input PDF, we
+ % trim enough for it to fit on page, and we do not trim
+ % so much that we clip out part of the graphic itself.
+ % This seems to work, anyway.
+ \includegraphics[trim=400 400 400 400,scale=2.5]{isc-logo}
+ \end{center}\par
+ \newpage
+ \thispagestyle{empty}
+ \vfill
+ \DBKcopyright \\
+ \vfill\null
+ \begin{center}
+ Internet Systems Consortium \\
+ 950 Charter Street \\
+ Redwood City, California \\
+ USA \\
+ https://www.isc.org/
+ \end{center}
+ \vfil\null
+}
--- /dev/null
+%%
+%% This style is derivated from the docbook one
+%%
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{notestyle}[]
+
+%% Just use the original package and pass the options
+\RequirePackageWithOptions{db2latex}
+
+%% My Cover Page
+\def\maketitle{%
+}
+
+%% Suppress header
+\fancyhead{}
+\renewcommand{\headrulewidth}{0pt}
+\renewcommand{\footrulewidth}{0pt}
distclean::
rm -f isc-docbook-chunk.xsl isc-docbook-html.xsl \
- isc-docbook-latex.xsl isc-manpage.xsl \
- isc-notes-html.xsl isc-notes-latex.xsl
+ isc-manpage.xsl isc-notes-html.xsl
--- /dev/null
+<?xml version='1.0' encoding="iso-8859-1"?>
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ xmlns:db="http://docbook.org/ns/docbook">
+
+ <!-- <optional> and <command> rendered in <programlisting>s.
+ For each overriden element, the parameters must be defined.
+ They are mandatory, and $probe must be set to 0 by default.
+
+ Only dblatex 0.2.12, with the verbatim.boldseq template works
+ here.
+ -->
+ <xsl:template match="optional|command" mode="latex.programlisting">
+ <xsl:param name="co-tagin" select="'<:'"/>
+ <xsl:param name="rnode" select="/"/>
+ <xsl:param name="probe" select="0"/>
+
+ <xsl:call-template name="verbatim.boldseq">
+ <xsl:with-param name="co-tagin" select="$co-tagin"/>
+ <xsl:with-param name="rnode" select="$rnode"/>
+ <xsl:with-param name="probe" select="$probe"/>
+ </xsl:call-template>
+ </xsl:template>
+
+ <!-- skip over docinfo section when including man pages in ARM -->
+ <xsl:template match="docinfo"/>
+
+ <!-- Skip abstracts and sidebars -->
+ <xsl:template match="abstract"/>
+ <xsl:template match="sidebar"/>
+
+ <!-- Two section level in the Table of contents -->
+ <xsl:param name="toc.section.depth">2</xsl:param>
+
+ <!-- Do not show the collaborators listed in bookinfo -->
+ <xsl:param name="doc.collab.show" select="0"/>
+
+ <!-- No revision history in the front matter -->
+ <xsl:param name="latex.output.revhistory" select="0"/>
+
+ <!-- Do not put sections for appendixes in TOC (set tocdepth=0) -->
+ <!-- Do not put appendixes in TOC (set tocdepth=-1) -->
+ <xsl:template match="appendix">
+ <xsl:if test="not (preceding-sibling::appendix)">
+ <xsl:call-template name="set-tocdepth">
+ <!-- -1 for not appendix -->
+ <!-- 0 for no sections from appendix -->
+ <xsl:with-param name="depth" select="0"/>
+ </xsl:call-template>
+ </xsl:if>
+ <xsl:apply-imports/>
+ </xsl:template>
+
+ <!-- Use the book class layout (instead of report) -->
+ <xsl:param name="latex.class.book">book</xsl:param>
+
+ <!-- Printable version -->
+ <!-- the blue boxes won't show up in print, but change to black and the boxes
+ disappeared -->
+ <!-- urlcolor=black is for email addresses etc -->
+ <xsl:param name="latex.class.options">nohyperlink,colorlinks,linkcolor=black,urlcolor=black</xsl:param>
+
+ <!-- Variable list terms on line by themselves -->
+ <xsl:param name="term.breakline">1</xsl:param>
+
+ <!-- preface heading in TOC, 2 to get sections also -->
+ <xsl:param name="preface.tocdepth">2</xsl:param>
+
+ <!-- set latex secnumdepth, choose level of subsections to number -->
+ <xsl:param name="doc.section.depth">1</xsl:param>
+
+ <!-- custom for menu labels -->
+ <!-- I don't use guisubmenu -->
+ <!-- TODO: guimenu and guimenuitem not doing anything here -->
+ <xsl:template match="guimenu|guimenuitem">
+ <xsl:call-template name="inline.sansserifseq"/>
+ </xsl:template>
+ <xsl:template match="guibutton">
+ <xsl:call-template name="inline.sansserifseq"/>
+ </xsl:template>
+ <xsl:template match="guilabel">
+ <xsl:call-template name="inline.sansserifseq"/>
+ </xsl:template>
+
+ <xsl:template name="inline.sansserifseq">
+ <xsl:param name="content">
+ <xsl:apply-templates/>
+ </xsl:param>
+ <xsl:text>\textsf{</xsl:text>
+ <xsl:copy-of select="$content"/>
+ <xsl:text>}</xsl:text>
+ </xsl:template>
+
+ <xsl:template match="othercredit|othername"/>
+
+ <!-- 21/Oct/2009 reed - don't widen tables -->
+ <xsl:param name="newtbl.autowidth">default</xsl:param>
+
+ <!-- 2014-09-25 reed - use Q and A instead of number -->
+ <xsl:param name="qanda.defaultlabel">qanda</xsl:param>
+
+ <!-- 2014-10-07 reed - add index to table of contents -->
+ <xsl:param name="index.tocdepth">5</xsl:param>
+ <xsl:param name="index.numbered">0</xsl:param>
+
+ <!-- Include our copyright generator -->
+ <xsl:include href="copyright.xsl"/>
+ <xsl:param name="isc.copyright.leader"/>
+ <xsl:param name="isc.copyright.breakline"> \\</xsl:param>
+
+ <xsl:template match="book" mode="docinfo">
+ <xsl:apply-imports/>
+ <xsl:text>\def\DBKtitle{</xsl:text>
+ <xsl:value-of select="info/title"/>
+ <xsl:text>} </xsl:text>
+
+ <xsl:text>\def\DBKcopyright{</xsl:text>
+ <xsl:value-of select="$isc.copyright"/>
+ <xsl:text>} </xsl:text>
+ </xsl:template>
+
+</xsl:stylesheet>
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id: copyright.xsl,v 1.8 2009/07/10 23:47:58 tbox Exp $ -->
-
<!-- Generate ISC copyright comments from Docbook copyright metadata. -->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ xmlns:db="http://docbook.org/ns/docbook">
<xsl:template name="isc.copyright.format">
<xsl:param name="text"/>
<xsl:variable name="isc.copyright">
<xsl:call-template name="isc.copyright.format">
<xsl:with-param name="text">
- <xsl:for-each select="/refentry/docinfo/copyright | /book/bookinfo/copyright">
+ <xsl:for-each select="db:book/db:info/db:copyright | db:refentry/db:docinfo/db:copyright">
<xsl:text>Copyright (C) </xsl:text>
<xsl:call-template name="copyright.years">
- <xsl:with-param name="years" select="year"/>
+ <xsl:with-param name="years" select="db:year"/>
</xsl:call-template>
<xsl:text> </xsl:text>
- <xsl:value-of select="holder"/>
+ <xsl:value-of select="db:holder"/>
+ <xsl:value-of select="$isc.copyright.breakline"/>
<xsl:text> </xsl:text>
</xsl:for-each>
<xsl:value-of select="$isc.copyright.text"/>
</xsl:with-param>
</xsl:call-template>
</xsl:variable>
-
</xsl:stylesheet>
<!--
--- /dev/null
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-3
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/12/05 8:20 PM
+%%BoundingBox: 0 0 29 29
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-3
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-3
+%ALDBoundingBox: -2 -2 29 29
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed {
+_NXLevel2 not {
+/colorimage where {
+userdict eq {
+/_rci false def
+} if
+} if
+} if
+} if
+/md defed{
+md type /dicttype eq {
+/colorimage where {
+md eq {
+/_rci false def
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf
+}ifelse
+/privrectpath {
+4 -2 roll m
+dtransform round exch round exch idtransform
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/`
+{
+false setoverprint
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1
+statusdict begin
+/processcolors defed
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end
+def
+/printerRes
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency}
+{GrayAngle GrayFrequency}
+{0 Width Height matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60}
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch
+}
+ifelse
+printerRes 300 max exch div exch
+2 copy
+sin mul round dup mul
+3 1 roll
+cos mul round dup mul
+add 1 add
+dup maxsteps gt {pop maxsteps} if
+dup minsteps lt {pop minsteps} if
+}
+ifelse
+} bdf
+/nextrelease defed {
+/languagelevel defed not {
+/framebuffer defed {
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps
+{
+forcemaxsteps
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max
+printerRes div
+gradfrequency mul
+round
+5 max
+min
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def
+/delta -0 def
+/frac -0 def
+/height -0 def
+/left -0 def
+/numsteps1 -0 def
+/radius -0 def
+/right -0 def
+/top -0 def
+/width -0 def
+/xt -0 def
+/yt -0 def
+/df currentflat def
+/tempstr 1 string def
+/clipflatness currentflat def
+/inverted?
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def
+/tc2 [0 0 0 1] def
+/storerect{/top xdf /right xdf /bottom xdf /left xdf
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup}
+{dup} ifelse
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def
+{
+exch dup
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall
+NF
+}bdf
+/MN{
+1 index length
+/Len exch def
+dup length Len add
+string dup
+Len
+4 -1 roll
+putinterval
+dup
+0
+4 -1 roll
+putinterval
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFJ
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFJ{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCJ}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup
+hasfont
+not
+{
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFJ
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup
+hasfont
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFK
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFK{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCK}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup
+hasfont
+not
+{
+pop
+/JCsm
+hasfont
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFK{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFK
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFTC
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFTC{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCTC}
+ifelse
+}bdf
+/FDFTC
+{
+dup
+hasfont
+not
+{
+pop
+/DFMing-Lt-HK-BF
+hasfont
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFTC
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat
+exch
+dup 0 le{pop 1}if
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if}
+{exit}
+ifelse
+}loop
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh
+
+_efh
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor {
+max max max
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{
+4 index 1 index get 0.3 mul
+4 index 2 index get 0.59 mul
+4 index 3 index get 0.11 mul
+4 index 4 index get
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx
+6 -1 roll/exec cvx
+7 -1 roll/exec cvx
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub
+1.0 dup im ik add min sub
+1.0 dup iy ik add min sub
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf
+/setspotcolor {
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def
+/_lfp4 {
+1 pop
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def
+/_lfs4 {
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 2 lt {pop 2} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def
+/vc{
+AltsysDict /cvc 2 index put
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf
+0 setseparationgray
+/imgr {1692.47 1570.59 1723.65 1601.77 } def
+/bleed 0 def
+/clpr {1692.47 1570.59 1723.65 1601.77 } def
+/xs 1 def
+/ys 1 def
+/botx 0 def
+/overlap 0 def
+/wdist 18 def
+0 2 mul fhsetspreadsize
+0 0 ne {/df 0 def /clipflatness 0 def} if
+/maxsteps 256 def
+/forcemaxsteps false def
+/minsteps 0 def
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end
+vms
+-1694 -1572 translate
+
+/currentpacking defed{false setpacking}if
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+q
+[1 0 0 1 -249.981674 -586.867554] concat
+vms
+1946.9506 2177.5114 m
+1954.4907 2185.0516 L
+1956.7047 2187.2656 1960.2943 2187.2656 1962.5083 2185.0516 C
+1970.0485 2177.5114 L
+1972.2625 2175.2974 1972.2625 2171.7078 1970.0485 2169.4938 C
+1962.5083 2161.9537 L
+1960.2943 2159.7396 1956.7047 2159.7396 1954.4907 2161.9537 C
+1946.9506 2169.4938 L
+1944.7365 2171.7078 1944.7365 2175.2974 1946.9506 2177.5114 C
+s
+n
+true eomode
+1958.5469 2181.0039 m
+1959.2148 2181.0039 1959.7012 2180.9296 1960.0059 2180.7813 C
+1960.3142 2180.6326 1960.4684 2180.363 1960.4688 2179.9727 C
+1960.4688 2179.7383 1960.3398 2178.8026 1960.082 2177.166 C
+1959.0742 2170.4219 L
+1958.9373 2170.3241 1958.7615 2170.2754 1958.5469 2170.2754 C
+1958.3319 2170.2754 1958.1561 2170.3241 1958.0195 2170.4219 C
+1957.0117 2177.166 L
+1956.7539 2178.8026 1956.625 2179.7379 1956.625 2179.9727 C
+1956.625 2180.363 1956.7792 2180.6326 1957.0879 2180.7813 C
+1957.4003 2180.9296 1957.8866 2181.0035 1958.5469 2181.0039 C
+h
+1958.5469 2165.166 m
+1958.0389 2165.166 1957.5878 2165.3499 1957.1934 2165.7168 C
+1956.7986 2166.0837 1956.6016 2166.5485 1956.6016 2167.1113 C
+1956.6016 2167.6698 1956.7891 2168.1404 1957.1641 2168.5234 C
+1957.5427 2168.9102 1958.0038 2169.1035 1958.5469 2169.1035 C
+1959.1094 2169.1035 1959.5741 2168.9043 1959.9414 2168.5059 C
+1960.3083 2168.1074 1960.4918 2167.6423 1960.4922 2167.1113 C
+1960.4922 2166.748 1960.4102 2166.4177 1960.2461 2166.1211 C
+1960.082 2165.8241 1959.8513 2165.5916 1959.5547 2165.4238 C
+1959.2577 2165.2521 1958.9219 2165.1664 1958.5469 2165.166 C
+true setoverprint
+f
+false setoverprint
+n
+vmr
+Q
+false eomode
+vmr
+vmr
+end
+%%Trailer
--- /dev/null
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-3
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/12/05 8:20 PM
+%%BoundingBox: 0 0 29 29
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-3
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-3
+%ALDBoundingBox: -2 -2 29 29
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed {
+_NXLevel2 not {
+/colorimage where {
+userdict eq {
+/_rci false def
+} if
+} if
+} if
+} if
+/md defed{
+md type /dicttype eq {
+/colorimage where {
+md eq {
+/_rci false def
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf
+}ifelse
+/privrectpath {
+4 -2 roll m
+dtransform round exch round exch idtransform
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/`
+{
+false setoverprint
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1
+statusdict begin
+/processcolors defed
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end
+def
+/printerRes
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency}
+{GrayAngle GrayFrequency}
+{0 Width Height matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60}
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch
+}
+ifelse
+printerRes 300 max exch div exch
+2 copy
+sin mul round dup mul
+3 1 roll
+cos mul round dup mul
+add 1 add
+dup maxsteps gt {pop maxsteps} if
+dup minsteps lt {pop minsteps} if
+}
+ifelse
+} bdf
+/nextrelease defed {
+/languagelevel defed not {
+/framebuffer defed {
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps
+{
+forcemaxsteps
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max
+printerRes div
+gradfrequency mul
+round
+5 max
+min
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def
+/delta -0 def
+/frac -0 def
+/height -0 def
+/left -0 def
+/numsteps1 -0 def
+/radius -0 def
+/right -0 def
+/top -0 def
+/width -0 def
+/xt -0 def
+/yt -0 def
+/df currentflat def
+/tempstr 1 string def
+/clipflatness currentflat def
+/inverted?
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def
+/tc2 [0 0 0 1] def
+/storerect{/top xdf /right xdf /bottom xdf /left xdf
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup}
+{dup} ifelse
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def
+{
+exch dup
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall
+NF
+}bdf
+/MN{
+1 index length
+/Len exch def
+dup length Len add
+string dup
+Len
+4 -1 roll
+putinterval
+dup
+0
+4 -1 roll
+putinterval
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFJ
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFJ{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCJ}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup
+hasfont
+not
+{
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFJ
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup
+hasfont
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFK
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFK{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCK}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup
+hasfont
+not
+{
+pop
+/JCsm
+hasfont
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFK{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFK
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFTC
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFTC{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCTC}
+ifelse
+}bdf
+/FDFTC
+{
+dup
+hasfont
+not
+{
+pop
+/DFMing-Lt-HK-BF
+hasfont
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFTC
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat
+exch
+dup 0 le{pop 1}if
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if}
+{exit}
+ifelse
+}loop
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh
+
+_efh
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor {
+max max max
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{
+4 index 1 index get 0.3 mul
+4 index 2 index get 0.59 mul
+4 index 3 index get 0.11 mul
+4 index 4 index get
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx
+6 -1 roll/exec cvx
+7 -1 roll/exec cvx
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub
+1.0 dup im ik add min sub
+1.0 dup iy ik add min sub
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf
+/setspotcolor {
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def
+/_lfp4 {
+1 pop
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def
+/_lfs4 {
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 2 lt {pop 2} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def
+/vc{
+AltsysDict /cvc 2 index put
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf
+0 setseparationgray
+/imgr {1692.47 1570.59 1723.65 1601.77 } def
+/bleed 0 def
+/clpr {1692.47 1570.59 1723.65 1601.77 } def
+/xs 1 def
+/ys 1 def
+/botx 0 def
+/overlap 0 def
+/wdist 18 def
+0 2 mul fhsetspreadsize
+0 0 ne {/df 0 def /clipflatness 0 def} if
+/maxsteps 256 def
+/forcemaxsteps false def
+/minsteps 0 def
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end
+vms
+-1694 -1572 translate
+
+/currentpacking defed{false setpacking}if
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+q
+[1 0 0 1 -249.981674 -586.867554] concat
+vms
+1946.9506 2177.5114 m
+1954.4907 2185.0516 L
+1956.7047 2187.2656 1960.2943 2187.2656 1962.5083 2185.0516 C
+1970.0485 2177.5114 L
+1972.2625 2175.2974 1972.2625 2171.7078 1970.0485 2169.4938 C
+1962.5083 2161.9537 L
+1960.2943 2159.7396 1956.7047 2159.7396 1954.4907 2161.9537 C
+1946.9506 2169.4938 L
+1944.7365 2171.7078 1944.7365 2175.2974 1946.9506 2177.5114 C
+s
+n
+true eomode
+1958.5469 2181.0039 m
+1959.2148 2181.0039 1959.7012 2180.9296 1960.0059 2180.7813 C
+1960.3142 2180.6326 1960.4684 2180.363 1960.4688 2179.9727 C
+1960.4688 2179.7383 1960.3398 2178.8026 1960.082 2177.166 C
+1959.0742 2170.4219 L
+1958.9373 2170.3241 1958.7615 2170.2754 1958.5469 2170.2754 C
+1958.3319 2170.2754 1958.1561 2170.3241 1958.0195 2170.4219 C
+1957.0117 2177.166 L
+1956.7539 2178.8026 1956.625 2179.7379 1956.625 2179.9727 C
+1956.625 2180.363 1956.7792 2180.6326 1957.0879 2180.7813 C
+1957.4003 2180.9296 1957.8866 2181.0035 1958.5469 2181.0039 C
+h
+1958.5469 2165.166 m
+1958.0389 2165.166 1957.5878 2165.3499 1957.1934 2165.7168 C
+1956.7986 2166.0837 1956.6016 2166.5485 1956.6016 2167.1113 C
+1956.6016 2167.6698 1956.7891 2168.1404 1957.1641 2168.5234 C
+1957.5427 2168.9102 1958.0038 2169.1035 1958.5469 2169.1035 C
+1959.1094 2169.1035 1959.5741 2168.9043 1959.9414 2168.5059 C
+1960.3083 2168.1074 1960.4918 2167.6423 1960.4922 2167.1113 C
+1960.4922 2166.748 1960.4102 2166.4177 1960.2461 2166.1211 C
+1960.082 2165.8241 1959.8513 2165.5916 1959.5547 2165.4238 C
+1959.2577 2165.2521 1958.9219 2165.1664 1958.5469 2165.166 C
+true setoverprint
+f
+false setoverprint
+n
+vmr
+Q
+false eomode
+vmr
+vmr
+end
+%%Trailer
--- /dev/null
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-1
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/07/16 10:41 PM
+%%BoundingBox: 0 0 27 27
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-1
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-1
+%ALDBoundingBox: -153 -436 442 406
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed {
+_NXLevel2 not {
+/colorimage where {
+userdict eq {
+/_rci false def
+} if
+} if
+} if
+} if
+/md defed{
+md type /dicttype eq {
+/colorimage where {
+md eq {
+/_rci false def
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf
+}ifelse
+/privrectpath {
+4 -2 roll m
+dtransform round exch round exch idtransform
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/`
+{
+false setoverprint
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1
+statusdict begin
+/processcolors defed
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end
+def
+/printerRes
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency}
+{GrayAngle GrayFrequency}
+{0 Width Height matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60}
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch
+}
+ifelse
+printerRes 300 max exch div exch
+2 copy
+sin mul round dup mul
+3 1 roll
+cos mul round dup mul
+add 1 add
+dup maxsteps gt {pop maxsteps} if
+dup minsteps lt {pop minsteps} if
+}
+ifelse
+} bdf
+/nextrelease defed {
+/languagelevel defed not {
+/framebuffer defed {
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps
+{
+forcemaxsteps
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max
+printerRes div
+gradfrequency mul
+round
+5 max
+min
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def
+/delta -0 def
+/frac -0 def
+/height -0 def
+/left -0 def
+/numsteps1 -0 def
+/radius -0 def
+/right -0 def
+/top -0 def
+/width -0 def
+/xt -0 def
+/yt -0 def
+/df currentflat def
+/tempstr 1 string def
+/clipflatness currentflat def
+/inverted?
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def
+/tc2 [0 0 0 1] def
+/storerect{/top xdf /right xdf /bottom xdf /left xdf
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup}
+{dup} ifelse
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def
+{
+exch dup
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall
+NF
+}bdf
+/MN{
+1 index length
+/Len exch def
+dup length Len add
+string dup
+Len
+4 -1 roll
+putinterval
+dup
+0
+4 -1 roll
+putinterval
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFJ
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFJ{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCJ}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup
+hasfont
+not
+{
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFJ
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup
+hasfont
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFK
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFK{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCK}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup
+hasfont
+not
+{
+pop
+/JCsm
+hasfont
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFK{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFK
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFTC
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFTC{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCTC}
+ifelse
+}bdf
+/FDFTC
+{
+dup
+hasfont
+not
+{
+pop
+/DFMing-Lt-HK-BF
+hasfont
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFTC
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat
+exch
+dup 0 le{pop 1}if
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if}
+{exit}
+ifelse
+}loop
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh
+
+_efh
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor {
+max max max
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{
+4 index 1 index get 0.3 mul
+4 index 2 index get 0.59 mul
+4 index 3 index get 0.11 mul
+4 index 4 index get
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx
+6 -1 roll/exec cvx
+7 -1 roll/exec cvx
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub
+1.0 dup im ik add min sub
+1.0 dup iy ik add min sub
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf
+/setspotcolor {
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def
+/_lfp4 {
+1 pop
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def
+/_lfs4 {
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 2 lt {pop 2} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def
+/vc{
+AltsysDict /cvc 2 index put
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf
+0 setseparationgray
+/imgr {1692.47 1570.59 2287.75 2412.48 } def
+/bleed 0 def
+/clpr {1692.47 1570.59 2287.75 2412.48 } def
+/xs 1 def
+/ys 1 def
+/botx 0 def
+/overlap 0 def
+/wdist 18 def
+0 2 mul fhsetspreadsize
+0 0 ne {/df 0 def /clipflatness 0 def} if
+/maxsteps 256 def
+/forcemaxsteps false def
+/minsteps 0 def
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end
+vms
+0.15 0.15 scale %JND
+-1845 -2006 translate
+
+/currentpacking defed{false setpacking}if
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+1848.4365 2094.0422 m
+1848.4365 2140.987 1886.4917 2179.0422 1933.4365 2179.0422 C
+1980.3813 2179.0422 2018.4365 2140.987 2018.4365 2094.0422 C
+2018.4365 2047.0974 1980.3813 2009.0422 1933.4365 2009.0422 C
+1886.4917 2009.0422 1848.4365 2047.0974 1848.4365 2094.0422 C
+5.3858 w
+3.863693 M
+s
+n
+true eomode
+1880.5612 2118.7403 m
+1880.5612 2121.7396 1881.6862 2124.8795 1883.9362 2128.1622 C
+1886.1862 2131.4889 1888.4581 2133.1522 1890.7565 2133.1544 C
+1892.2089 2133.1544 1893.4042 2132.5677 1894.3424 2131.3966 C
+1895.3268 2130.2233 1895.819 2128.7467 1895.819 2126.9669 C
+1895.819 2124.0599 1894.6237 2121.0826 1892.233 2118.0372 C
+1889.8885 2114.9896 1887.6144 2113.4669 1885.4127 2113.4669 C
+1884.0526 2113.4669 1882.9034 2113.9591 1881.9674 2114.9435 C
+1881.0292 2115.974 1880.5612 2117.2396 1880.5612 2118.7403 C
+h
+1948.2018 2061.1544 m
+1978.4362 2061.0138 L
+1980.451 2062.6068 1981.9034 2064.3163 1982.7955 2066.1466 C
+1983.7316 2068.0209 1984.1996 2070.2005 1984.2018 2072.6857 C
+1984.2018 2073.2482 L
+1969.2252 2099.6153 L
+1969.2252 2099.3341 1969.2472 2098.8639 1969.2955 2098.2091 C
+1969.3417 2097.5983 1969.3636 2097.1544 1969.3658 2096.8732 C
+1969.3658 2089.888 1967.5597 2083.3732 1963.9518 2077.3263 C
+1960.3878 2071.2794 1955.1385 2065.8873 1948.2018 2061.1544 C
+h
+1905.8737 2139.4825 m
+1910.0924 2124.2247 L
+1964.233 2092.5841 L
+1964.6066 2094.3177 1964.8636 2095.724 1965.0065 2096.8028 C
+1965.1471 2097.9278 1965.2174 2098.9122 1965.2174 2099.756 C
+1965.2174 2100.4108 1965.1691 2101.5599 1965.0768 2103.2013 C
+1964.9823 2103.5748 1964.9362 2103.8561 1964.9362 2104.045 C
+1905.8737 2139.4825 L
+h
+1908.4752 2120.3575 m
+1898.983 2105.5216 L
+1954.3893 2072.8263 L
+1956.4987 2074.7005 1958.2565 2076.8561 1959.6627 2079.295 C
+1961.1151 2081.7779 1962.2863 2084.6608 1963.1783 2087.9435 C
+1908.4752 2120.3575 L
+h
+1896.2408 2102.3575 m
+1880.5612 2099.0528 L
+1942.9283 2062.631 L
+1944.5675 2063.5209 1946.0682 2064.5272 1947.4283 2065.6544 C
+1948.7863 2066.7794 1950.0057 2068.0209 1951.0846 2069.381 C
+1896.2408 2102.3575 L
+h
+1871.2096 2120.7794 m
+1876.3424 2102.3575 L
+1894.2018 2105.9435 L
+1906.1549 2125.2794 L
+1900.8815 2142.506 L
+1882.7408 2139.2013 L
+1871.2096 2120.7794 L
+h
+1866.7096 2121.4825 m
+1880.1393 2142.3653 L
+1901.3033 2146.5841 L
+1963.6705 2109.3888 L
+1968.0299 2106.8092 1971.005 2103.9747 1972.6002 2100.881 C
+1972.8815 2100.2701 1973.1144 2099.8021 1973.3033 2099.4747 C
+1991.444 2068.256 L
+1991.6769 2067.8341 1992.0043 2067.2474 1992.4283 2066.4982 C
+1994.0675 2064.013 1994.8871 2062.0904 1994.8893 2060.7325 C
+1994.8893 2059.4186 1994.3971 2058.4825 1993.4127 2057.92 C
+1992.4745 2057.4037 1990.6705 2057.1466 1987.9987 2057.1466 C
+1948.0612 2057.1466 L
+1946.4198 2057.1466 1944.7784 2057.4037 1943.1393 2057.92 C
+1941.4979 2058.4825 1939.4127 2059.513 1936.8815 2061.0138 C
+1873.6705 2098.631 L
+1866.7096 2121.4825 L
+true setoverprint
+f
+false setoverprint
+n
+vmr
+vmr
+end
+%%Trailer
--- /dev/null
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-1
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/07/16 10:41 PM
+%%BoundingBox: 0 0 27 27
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-1
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-1
+%ALDBoundingBox: -153 -436 442 406
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed {
+_NXLevel2 not {
+/colorimage where {
+userdict eq {
+/_rci false def
+} if
+} if
+} if
+} if
+/md defed{
+md type /dicttype eq {
+/colorimage where {
+md eq {
+/_rci false def
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf
+}ifelse
+/privrectpath {
+4 -2 roll m
+dtransform round exch round exch idtransform
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/`
+{
+false setoverprint
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1
+statusdict begin
+/processcolors defed
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end
+def
+/printerRes
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency}
+{GrayAngle GrayFrequency}
+{0 Width Height matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60}
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch
+}
+ifelse
+printerRes 300 max exch div exch
+2 copy
+sin mul round dup mul
+3 1 roll
+cos mul round dup mul
+add 1 add
+dup maxsteps gt {pop maxsteps} if
+dup minsteps lt {pop minsteps} if
+}
+ifelse
+} bdf
+/nextrelease defed {
+/languagelevel defed not {
+/framebuffer defed {
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps
+{
+forcemaxsteps
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max
+printerRes div
+gradfrequency mul
+round
+5 max
+min
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def
+/delta -0 def
+/frac -0 def
+/height -0 def
+/left -0 def
+/numsteps1 -0 def
+/radius -0 def
+/right -0 def
+/top -0 def
+/width -0 def
+/xt -0 def
+/yt -0 def
+/df currentflat def
+/tempstr 1 string def
+/clipflatness currentflat def
+/inverted?
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def
+/tc2 [0 0 0 1] def
+/storerect{/top xdf /right xdf /bottom xdf /left xdf
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup}
+{dup} ifelse
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def
+{
+exch dup
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall
+NF
+}bdf
+/MN{
+1 index length
+/Len exch def
+dup length Len add
+string dup
+Len
+4 -1 roll
+putinterval
+dup
+0
+4 -1 roll
+putinterval
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFJ
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFJ{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCJ}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup
+hasfont
+not
+{
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFJ
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup
+hasfont
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFK
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFK{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCK}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup
+hasfont
+not
+{
+pop
+/JCsm
+hasfont
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFK{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFK
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFTC
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFTC{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCTC}
+ifelse
+}bdf
+/FDFTC
+{
+dup
+hasfont
+not
+{
+pop
+/DFMing-Lt-HK-BF
+hasfont
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFTC
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat
+exch
+dup 0 le{pop 1}if
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if}
+{exit}
+ifelse
+}loop
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh
+
+_efh
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor {
+max max max
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{
+4 index 1 index get 0.3 mul
+4 index 2 index get 0.59 mul
+4 index 3 index get 0.11 mul
+4 index 4 index get
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx
+6 -1 roll/exec cvx
+7 -1 roll/exec cvx
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub
+1.0 dup im ik add min sub
+1.0 dup iy ik add min sub
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf
+/setspotcolor {
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def
+/_lfp4 {
+1 pop
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def
+/_lfs4 {
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 2 lt {pop 2} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def
+/vc{
+AltsysDict /cvc 2 index put
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf
+0 setseparationgray
+/imgr {1692.47 1570.59 2287.75 2412.48 } def
+/bleed 0 def
+/clpr {1692.47 1570.59 2287.75 2412.48 } def
+/xs 1 def
+/ys 1 def
+/botx 0 def
+/overlap 0 def
+/wdist 18 def
+0 2 mul fhsetspreadsize
+0 0 ne {/df 0 def /clipflatness 0 def} if
+/maxsteps 256 def
+/forcemaxsteps false def
+/minsteps 0 def
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end
+vms
+0.15 0.15 scale %JND
+-1845 -2006 translate
+
+/currentpacking defed{false setpacking}if
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+1848.4365 2094.0422 m
+1848.4365 2140.987 1886.4917 2179.0422 1933.4365 2179.0422 C
+1980.3813 2179.0422 2018.4365 2140.987 2018.4365 2094.0422 C
+2018.4365 2047.0974 1980.3813 2009.0422 1933.4365 2009.0422 C
+1886.4917 2009.0422 1848.4365 2047.0974 1848.4365 2094.0422 C
+5.3858 w
+3.863693 M
+s
+n
+true eomode
+1897.6516 2067.1709 m
+1897.6087 2066.5538 L
+1885.3743 2066.1319 L
+1883.1946 2062.4053 L
+1869.9055 2063.9522 L
+1869.9055 2067.1712 L
+1897.6516 2067.1709 L
+h
+1944.0852 2067.1709 m
+1944.0852 2067.0077 1944.0852 2066.8741 1944.0852 2066.7647 C
+1944.1314 2066.5757 1944.1775 2066.4131 1944.2258 2066.2725 C
+1945.0213 2065.0992 1946.0056 2064.2554 1947.179 2063.7413 C
+1948.3963 2063.2249 1950.0134 2062.9678 1952.0305 2062.9678 C
+1956.0142 2062.9678 1959.7627 2063.9522 1963.2805 2065.9209 C
+1964.0204 2066.3353 1964.6824 2066.7527 1965.2665 2067.1732 C
+1971.313 2067.1709 L
+1970.2122 2065.693 1968.5893 2064.3153 1966.4446 2063.0381 C
+1962.0369 2060.4585 1956.8821 2059.1709 1950.9758 2059.1709 C
+1948.6775 2059.1709 1946.7791 2059.5445 1945.2805 2060.2959 C
+1943.7798 2061.0914 1942.5142 2062.357 1941.4837 2064.0928 C
+1941.2486 2064.0928 1940.8728 2064.0928 1940.3587 2064.0928 C
+1937.5462 2063.9039 1935.4829 2063.8116 1934.1712 2063.8116 C
+1929.2954 2063.8116 1925.1228 2064.2796 1921.6555 2065.2178 C
+1919.9787 2065.6936 1918.2362 2066.3443 1916.4282 2067.1704 C
+1944.0852 2067.1709 L
+true setoverprint
+f
+false setoverprint
+n
+1884.4125 2075.1709 m
+1884.4602 2073.585 L
+1893.1087 2073.0225 L
+1893.1087 2075.1712 L
+1910.8456 2075.1709 L
+1910.98 2075.0913 1911.1146 2075.0069 1911.2493 2074.9209 C
+1911.9986 2074.3584 1912.583 2073.9585 1913.0071 2073.7256 C
+1916.804 2071.4756 1920.2954 2069.9288 1923.4837 2069.085 C
+1926.718 2068.2413 1931.0071 2067.8194 1936.3508 2067.8194 C
+1940.3587 2067.8194 L
+1940.7805 2070.7022 L
+1938.9524 2070.8428 1937.522 2071.4053 1936.4915 2072.3897 C
+1935.7726 2073.1422 1935.3163 2074.0693 1935.1223 2075.1726 C
+1940.1696 2075.1709 L
+1940.3293 2074.9768 1940.5095 2074.8018 1940.7102 2074.6397 C
+1941.7407 2073.8421 1943.147 2073.4444 1944.929 2073.4444 C
+1948.4128 2073.4444 1951.8259 2074.0193 1955.1674 2075.169 C
+1963.5704 2075.1709 L
+1962.8877 2074.843 1962.0411 2074.4337 1961.0305 2073.9366 C
+1958.1697 2072.5303 1955.2166 2071.4976 1952.1712 2070.8428 C
+1951.3274 2070.7022 1950.2244 2070.5132 1948.8665 2070.2803 C
+1945.6782 2069.7178 1944.0852 2068.8038 1944.0852 2067.5381 C
+1944.0852 2067.4017 1944.0852 2067.2776 1944.0852 2067.1658 C
+1916.4282 2067.1709 L
+1914.4953 2068.0535 1912.4877 2069.1369 1910.4055 2070.4209 C
+1910.0759 2070.6539 1909.6321 2070.9593 1909.0696 2071.335 C
+1905.9275 2073.5367 1902.9041 2074.6375 1899.9993 2074.6397 C
+1899.9509 2074.6397 1899.6939 2074.6155 1899.2258 2074.5694 C
+1898.7556 2074.521 1898.4041 2074.5452 1898.1712 2074.6397 C
+1897.6516 2067.1709 L
+1869.9055 2067.1709 L
+1869.9055 2075.1714 L
+1884.4125 2075.1709 L
+h
+1972.5022 2075.1709 m
+1972.8687 2074.2606 1973.0523 2073.2652 1973.054 2072.1788 C
+1973.054 2070.3983 1972.4736 2068.7289 1971.313 2067.1709 C
+1965.2666 2067.1709 L
+1967.4581 2068.751 1968.554 2070.3727 1968.554 2072.0381 C
+1968.554 2073.0686 1968.2486 2073.9827 1967.6399 2074.7803 C
+1967.5373 2074.922 1967.4334 2075.0518 1967.3283 2075.1698 C
+1972.5022 2075.1709 L
+true setoverprint
+f
+false setoverprint
+n
+1869.9055 2075.1709 m
+1869.9055 2119.0772 L
+1897.1868 2119.8506 L
+1897.8899 2114.2256 L
+1899.2962 2114.2256 L
+1901.0759 2114.2256 1902.7876 2114.5069 1904.429 2115.0694 C
+1906.1165 2115.678 1908.2478 2116.825 1910.8274 2118.5147 C
+1911.9524 2119.2178 L
+1919.5923 2124.1397 1925.4041 2126.6006 1929.3899 2126.6006 C
+1930.8423 2126.6006 1932.3408 2126.3655 1933.8899 2125.8975 C
+1935.4368 2125.4756 1937.1463 2124.7945 1939.0227 2123.8584 C
+1940.1939 2123.9046 1941.8814 2123.9507 1944.0852 2123.9991 C
+1950.0376 2124.0914 1954.0674 2124.1375 1956.179 2124.1397 C
+1972.7244 2124.1397 1984.583 2123.1311 1991.7571 2121.1163 C
+1998.9751 2119.1475 2002.583 2115.9351 2002.5852 2111.4834 C
+2002.5852 2107.8272 2000.2869 2105.2959 1995.6946 2103.8897 C
+1991.1463 2102.5296 1981.865 2101.8506 1967.8508 2101.8506 C
+1963.5618 2101.8506 L
+1964.6384 2100.8179 1965.4361 2099.8116 1965.9524 2098.8272 C
+1966.4666 2097.8428 1966.7236 2096.8343 1966.7258 2095.8038 C
+1966.7258 2095.3335 1966.6314 2094.7952 1966.4446 2094.1866 C
+1966.2556 2093.6241 1965.9041 2092.8506 1965.3899 2091.8663 C
+1967.1697 2091.1631 1968.5056 2090.1788 1969.3977 2088.9131 C
+1970.2876 2087.6936 1970.7315 2086.1929 1970.7337 2084.4131 C
+1970.7337 2083.521 1970.615 2082.6311 1970.3821 2081.7413 C
+1970.147 2080.8492 1969.7954 2079.9593 1969.3274 2079.0694 C
+1970.5447 2078.2256 1971.4588 2077.2171 1972.0696 2076.0459 C
+1972.2346 2075.7625 1972.3788 2075.4685 1972.5022 2075.1642 C
+1967.3284 2075.1709 L
+1966.8077 2075.7539 1966.2562 2076.0459 1965.6712 2076.0459 C
+1965.5191 2076.0459 1964.8189 2075.7521 1963.5704 2075.1643 C
+1955.1674 2075.1709 L
+1956.5004 2075.6277 1957.8219 2076.1778 1959.1321 2076.8194 C
+1963.7727 2079.1155 1966.093 2081.5523 1966.093 2084.1319 C
+1966.093 2085.303 1965.7173 2086.2632 1964.968 2087.0147 C
+1964.2649 2087.764 1963.3508 2088.1375 1962.2258 2088.1397 C
+1961.7556 2088.1397 1959.0838 2086.9905 1954.2102 2084.6944 C
+1949.3806 2082.396 1944.4368 2080.6624 1939.3743 2079.4913 C
+1939.2798 2079.3023 1939.2337 2079.0914 1939.2337 2078.8584 C
+1939.2337 2078.6695 1939.2337 2078.3663 1939.2337 2077.9444 C
+1939.2337 2076.8248 1939.5456 2075.8974 1940.1695 2075.1644 C
+1935.1224 2075.1709 L
+1935.0507 2075.5803 1935.0149 2076.012 1935.0149 2076.4678 C
+1935.0149 2076.8414 1935.0369 2077.2391 1935.0852 2077.6631 C
+1935.1775 2078.085 1935.294 2078.5992 1935.4368 2079.21 C
+1934.7337 2079.21 L
+1931.9673 2079.21 1929.7876 2080.0296 1928.1946 2081.6709 C
+1926.5994 2083.3101 1925.804 2085.514 1925.804 2088.2803 C
+1925.804 2088.9834 L
+1924.3032 2088.6077 1922.9673 2088.3265 1921.7962 2088.1397 C
+1920.6712 2087.9507 1919.6626 2087.8584 1918.7727 2087.8584 C
+1916.8501 2087.8584 1914.9517 2088.232 1913.0774 2088.9834 C
+1911.2493 2089.7789 1909.2102 2091.0906 1906.9602 2092.9209 C
+1906.8196 2094.6084 L
+1909.1619 2093.7647 1911.2713 2093.1077 1913.1477 2092.6397 C
+1915.022 2092.2178 1916.7556 2092.0069 1918.3508 2092.0069 C
+1920.6931 2092.0069 1922.9431 2092.521 1925.1008 2093.5538 C
+1927.3025 2094.5843 1929.5986 2096.2476 1931.9915 2098.5459 C
+1925.804 2107.7569 L
+1927.0696 2109.4444 L
+1928.4275 2108.3655 1930.2556 2106.7945 1932.554 2104.7334 C
+1938.2251 2099.6226 1942.9361 2097.0694 1946.6868 2097.0694 C
+1948.5149 2097.0694 1950.1782 2097.5132 1951.679 2098.4053 C
+1953.2258 2099.2952 1953.9993 2100.1851 1953.9993 2101.0772 C
+1953.9993 2101.6397 1952.9446 2103.1866 1950.8352 2105.7178 C
+1948.772 2108.2491 1946.1946 2111.0374 1943.1008 2114.085 C
+1939.4446 2117.6006 1936.7244 2119.8023 1934.9446 2120.6944 C
+1933.2088 2121.6304 1931.3103 2122.0984 1929.2493 2122.1006 C
+1925.3579 2122.1006 1920.3657 2120.0374 1914.2727 2115.9131 C
+1913.5696 2115.4913 1913.0532 2115.1617 1912.7258 2114.9288 C
+1909.6321 2112.8194 1907.1228 2111.4131 1905.2024 2110.71 C
+1903.2798 2110.053 1901.2166 2109.7256 1899.0149 2109.7256 C
+1898.0305 2109.7256 L
+1898.0305 2078.6475 L
+1899.8587 2078.6475 L
+1903.4329 2078.6475 1907.0952 2077.4884 1910.8456 2075.1742 C
+1893.1087 2075.1709 L
+1893.1087 2115.7725 L
+1883.1946 2115.6319 L
+1884.4125 2075.171 L
+1869.9055 2075.1709 L
+h
+1957.9368 2101.0772 m
+1957.3259 2098.5459 1956.0603 2096.6695 1954.1399 2095.4522 C
+1952.2634 2094.2327 1949.6399 2093.6241 1946.2649 2093.6241 C
+1945.1861 2093.6241 1943.615 2093.9273 1941.554 2094.5381 C
+1939.5369 2095.1929 1938.0383 2095.5203 1937.054 2095.5225 C
+1935.3665 2095.5225 1933.679 2094.8194 1931.9915 2093.4131 C
+1930.3501 2092.0069 1929.5305 2090.5765 1929.5305 2089.1241 C
+1929.5305 2087.107 1930.0447 2085.5601 1931.0774 2084.4834 C
+1932.1079 2083.4507 1933.6065 2082.9366 1935.5774 2082.9366 C
+1937.5462 2082.9366 1940.1477 2083.4046 1943.3821 2084.3428 C
+1946.6626 2085.3272 1949.9673 2086.5928 1953.2962 2088.1397 C
+1956.3416 2089.5459 1958.5674 2090.8819 1959.9758 2092.1475 C
+1961.3821 2093.4131 1962.0852 2094.6788 1962.0852 2095.9444 C
+1962.0852 2096.8343 1961.7556 2097.678 1961.1008 2098.4756 C
+1960.4439 2099.3194 1959.3892 2100.1851 1957.9368 2101.0772 C
+h
+1943.3821 2119.71 m
+1946.054 2117.1788 1948.3501 2114.8584 1950.2727 2112.7491 C
+1952.2415 2110.6397 1954.0213 2108.5303 1955.6165 2106.4209 C
+1958.5696 2106.1397 1961.2876 2105.9288 1963.7727 2105.7881 C
+1966.304 2105.6475 1968.6243 2105.5772 1970.7337 2105.5772 C
+1980.7642 2105.5772 1987.7471 2106.021 1991.6868 2106.9131 C
+1995.6704 2107.803 1997.6611 2109.3719 1997.6633 2111.6241 C
+1997.6633 2114.4366 1994.2883 2116.5459 1987.5383 2117.9522 C
+1980.8345 2119.4046 1970.8259 2120.1297 1957.5149 2120.1319 C
+1955.4055 2120.1319 1953.1555 2120.0835 1950.7649 2119.9913 C
+1948.4204 2119.9429 1945.9595 2119.8506 1943.3821 2119.71 C
+true setoverprint
+f
+false setoverprint
+n
+vmr
+vmr
+end
+%%Trailer
--- /dev/null
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-3
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/12/05 8:20 PM
+%%BoundingBox: 0 0 29 29
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-3
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-3
+%ALDBoundingBox: -2 -2 29 29
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed {
+_NXLevel2 not {
+/colorimage where {
+userdict eq {
+/_rci false def
+} if
+} if
+} if
+} if
+/md defed{
+md type /dicttype eq {
+/colorimage where {
+md eq {
+/_rci false def
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf
+}ifelse
+/privrectpath {
+4 -2 roll m
+dtransform round exch round exch idtransform
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/`
+{
+false setoverprint
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1
+statusdict begin
+/processcolors defed
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end
+def
+/printerRes
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency}
+{GrayAngle GrayFrequency}
+{0 Width Height matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform
+dup mul exch dup mul add sqrt 72 exch div}
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60}
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch
+}
+ifelse
+printerRes 300 max exch div exch
+2 copy
+sin mul round dup mul
+3 1 roll
+cos mul round dup mul
+add 1 add
+dup maxsteps gt {pop maxsteps} if
+dup minsteps lt {pop minsteps} if
+}
+ifelse
+} bdf
+/nextrelease defed {
+/languagelevel defed not {
+/framebuffer defed {
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps
+{
+forcemaxsteps
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max
+printerRes div
+gradfrequency mul
+round
+5 max
+min
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def
+/delta -0 def
+/frac -0 def
+/height -0 def
+/left -0 def
+/numsteps1 -0 def
+/radius -0 def
+/right -0 def
+/top -0 def
+/width -0 def
+/xt -0 def
+/yt -0 def
+/df currentflat def
+/tempstr 1 string def
+/clipflatness currentflat def
+/inverted?
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def
+/tc2 [0 0 0 1] def
+/storerect{/top xdf /right xdf /bottom xdf /left xdf
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup}
+{dup} ifelse
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def
+{
+exch dup
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall
+NF
+}bdf
+/MN{
+1 index length
+/Len exch def
+dup length Len add
+string dup
+Len
+4 -1 roll
+putinterval
+dup
+0
+4 -1 roll
+putinterval
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFJ
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFJ{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCJ}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup
+hasfont
+not
+{
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFJ
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup
+hasfont
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFK
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFK{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCK}
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where
+{
+pop
+/Font resourcestatus
+{
+pop pop true
+}
+{
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup
+hasfont
+not
+{
+pop
+/JCsm
+hasfont
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFK{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFK
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll
+/ourvec xdf
+256 string cvs
+(|______) anchorsearch
+{pop
+cvn
+dup FDFTC
+exch
+1 index
+eq
+{
+_bfh findfont _efh
+dup
+maxlength dict
+CD
+dup
+/FontName
+3 index
+put
+dup
+/Encoding ourvec put
+1 index
+exch
+definefont
+pop
+}
+{exch pop}
+ifelse
+}
+{pop}
+ifelse
+}bdf
+/RFTC{
+dup
+FontDirectory exch
+known
+{pop 3 -1 roll pop}
+{RCTC}
+ifelse
+}bdf
+/FDFTC
+{
+dup
+hasfont
+not
+{
+pop
+/DFMing-Lt-HK-BF
+hasfont
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup
+256 string cvs
+(|______)exch MN
+cvn
+dup
+FontDirectory
+exch known
+{
+exch
+pop
+findfont
+3 -1 roll
+pop
+}
+{
+pop
+FDFTC
+dup findfont
+dup maxlength dict
+CD
+dup dup
+/Encoding exch
+/Encoding get
+256 array copy
+7 -1 roll
+{
+3 -1 roll
+dup
+4 -2 roll
+put
+}forall
+put
+definefont
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat
+exch
+dup 0 le{pop 1}if
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if}
+{exit}
+ifelse
+}loop
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh
+
+_efh
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor {
+max max max
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{
+4 index 1 index get 0.3 mul
+4 index 2 index get 0.59 mul
+4 index 3 index get 0.11 mul
+4 index 4 index get
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx
+6 -1 roll/exec cvx
+7 -1 roll/exec cvx
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub
+1.0 dup im ik add min sub
+1.0 dup iy ik add min sub
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf
+/setspotcolor {
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def
+/_lfp4 {
+1 pop
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def
+/_lfs4 {
+/yt xdf
+/xt xdf
+/ang xdf
+storerect
+/taperfcn xdf
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+height abs adjnumsteps
+dup 2 lt {pop 2} if
+1 sub /numsteps1 xdf
+currentflat mark
+currentflat clipflatness
+/delta top bottom sub numsteps1 1 add div def
+/right right left sub def
+/botsv top delta sub def
+{
+{
+W
+xt yt translate
+ang rotate
+xt neg yt neg translate
+dup setflat
+/bottom botsv def
+0 1 numsteps1
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat
+{
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf
+/tint1 xdf
+bcs exch 1 exch put
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+tint1 tint2 sub abs
+bcs 1 get maxspot
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf
+/radius xdf
+/yt xdf
+/xt xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor
+calcgraysteps mul abs round
+radius inrad sub abs
+adjnumsteps
+dup 1 lt {pop 1} if
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse
+2 div /halfstep xdf
+currentflat mark
+currentflat clipflatness
+{
+{
+dup setflat
+W
+0 1 numsteps1
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat
+{
+newpath mark
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne
+inrad 0 gt or
+{
+xt yt
+numsteps1 0 eq
+{ inrad }
+{
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def
+/vc{
+AltsysDict /cvc 2 index put
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf
+0 setseparationgray
+/imgr {1692.47 1570.59 1723.65 1601.77 } def
+/bleed 0 def
+/clpr {1692.47 1570.59 1723.65 1601.77 } def
+/xs 1 def
+/ys 1 def
+/botx 0 def
+/overlap 0 def
+/wdist 18 def
+0 2 mul fhsetspreadsize
+0 0 ne {/df 0 def /clipflatness 0 def} if
+/maxsteps 256 def
+/forcemaxsteps false def
+/minsteps 0 def
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end
+vms
+-1694 -1572 translate
+
+/currentpacking defed{false setpacking}if
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+q
+[1 0 0 1 -249.981674 -586.867554] concat
+vms
+1946.9506 2177.5114 m
+1954.4907 2185.0516 L
+1956.7047 2187.2656 1960.2943 2187.2656 1962.5083 2185.0516 C
+1970.0485 2177.5114 L
+1972.2625 2175.2974 1972.2625 2171.7078 1970.0485 2169.4938 C
+1962.5083 2161.9537 L
+1960.2943 2159.7396 1956.7047 2159.7396 1954.4907 2161.9537 C
+1946.9506 2169.4938 L
+1944.7365 2171.7078 1944.7365 2175.2974 1946.9506 2177.5114 C
+s
+n
+true eomode
+1958.5469 2181.0039 m
+1959.2148 2181.0039 1959.7012 2180.9296 1960.0059 2180.7813 C
+1960.3142 2180.6326 1960.4684 2180.363 1960.4688 2179.9727 C
+1960.4688 2179.7383 1960.3398 2178.8026 1960.082 2177.166 C
+1959.0742 2170.4219 L
+1958.9373 2170.3241 1958.7615 2170.2754 1958.5469 2170.2754 C
+1958.3319 2170.2754 1958.1561 2170.3241 1958.0195 2170.4219 C
+1957.0117 2177.166 L
+1956.7539 2178.8026 1956.625 2179.7379 1956.625 2179.9727 C
+1956.625 2180.363 1956.7792 2180.6326 1957.0879 2180.7813 C
+1957.4003 2180.9296 1957.8866 2181.0035 1958.5469 2181.0039 C
+h
+1958.5469 2165.166 m
+1958.0389 2165.166 1957.5878 2165.3499 1957.1934 2165.7168 C
+1956.7986 2166.0837 1956.6016 2166.5485 1956.6016 2167.1113 C
+1956.6016 2167.6698 1956.7891 2168.1404 1957.1641 2168.5234 C
+1957.5427 2168.9102 1958.0038 2169.1035 1958.5469 2169.1035 C
+1959.1094 2169.1035 1959.5741 2168.9043 1959.9414 2168.5059 C
+1960.3083 2168.1074 1960.4918 2167.6423 1960.4922 2167.1113 C
+1960.4922 2166.748 1960.4102 2166.4177 1960.2461 2166.1211 C
+1960.082 2165.8241 1959.8513 2165.5916 1959.5547 2165.4238 C
+1959.2577 2165.2521 1958.9219 2165.1664 1958.5469 2165.166 C
+true setoverprint
+f
+false setoverprint
+n
+vmr
+Q
+false eomode
+vmr
+vmr
+end
+%%Trailer
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id: isc-docbook-chunk.xsl.in,v 1.6 2007/06/19 23:47:13 tbox Exp $ -->
-
<!-- ISC customizations for Docbook-XSL chunked HTML generator -->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:db="http://docbook.org/ns/docbook">
<!-- Import the Docbook HTML stuff -->
<xsl:import href="@XSLT_DOCBOOK_CHUNK_HTML@"/>
<!-- Set comment convention for this output format -->
<xsl:param name="isc.copyright.leader"> - </xsl:param>
+ <xsl:param name="isc.copyright.breakline"/>
+
+ <!-- Generate consistent id attributes -->
+ <xsl:param name="generate.consistent.ids" select="1"/>
<!-- Override Docbook template to insert copyright -->
<xsl:template name="user.preroot">
<xsl:value-of select="$isc.copyright"/>
</xsl:comment>
<xsl:text> </xsl:text>
- <xsl:comment> $Id$ </xsl:comment>
- <xsl:text> </xsl:text>
</xsl:template>
<xsl:template name="user.footer.navigation">
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id: isc-docbook-html.xsl.in,v 1.6 2007/06/19 23:47:13 tbox Exp $ -->
-
<!-- ISC customizations for Docbook-XSL HTML generator -->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:db="http://docbook.org/ns/docbook">
<!-- Import the Docbook HTML stuff -->
<xsl:import href="@XSLT_DOCBOOK_STYLE_HTML@"/>
<!-- Set comment convention for this output format -->
<xsl:param name="isc.copyright.leader"> - </xsl:param>
+ <xsl:param name="isc.copyright.breakline"/>
+
+ <!-- Generate consistent id attributes -->
+ <xsl:param name="generate.consistent.ids" select="1"/>
<!-- Override Docbook template to insert copyright -->
<xsl:template name="user.preroot">
<xsl:value-of select="$isc.copyright"/>
</xsl:comment>
<xsl:text> </xsl:text>
- <xsl:comment> $Id$ </xsl:comment>
- <xsl:text> </xsl:text>
</xsl:template>
<xsl:template name="user.footer.navigation">
+++ /dev/null
-<!--
- - Copyright (C) 2005, 2007 Internet Systems Consortium, Inc. ("ISC")
- -
- - Permission to use, copy, modify, and/or distribute this software for any
- - purpose with or without fee is hereby granted, provided that the above
- - copyright notice and this permission notice appear in all copies.
- -
- - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
- - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
- - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
- - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
- - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
- - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- - PERFORMANCE OF THIS SOFTWARE.
--->
-
-<!-- $Id: isc-docbook-latex-mappings.xml,v 1.4 2007/06/19 23:47:13 tbox Exp $ -->
-
-<!--
- - ISC modifications to db2latex mapping rules.
- -
- - We want <refentry/> elements to show up in the table of contents,
- - so we need to generate \section{}, not \section*{}.
- -->
-
-<latexbindings>
- <latexmapping role="begin">
- <mapping key="refentry" text="">
- <line>% </line>
- <line>% ------------------------------------------------------------- </line>
- <line>% Refentry </line>
- <line>% ------------------------------------------------------------- </line>
- <line>\section{%title%} </line>
- <line>\label{%id%}\hypertarget{%id%}{}% </line>
- </mapping>
- </latexmapping>
-</latexbindings>
+++ /dev/null
-<!--
- - Copyright (C) 2005, 2007, 2010, 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
- -
- - Permission to use, copy, modify, and/or distribute this software for any
- - purpose with or without fee is hereby granted, provided that the above
- - copyright notice and this permission notice appear in all copies.
- -
- - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
- - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
- - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
- - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
- - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
- - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- - PERFORMANCE OF THIS SOFTWARE.
--->
-
-<!-- $Id$ -->
-
-<!-- ISC customizations for db2latex generator -->
-
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
-
- <!-- Import the db2latex stuff -->
- <xsl:import href="@XSLT_DB2LATEX_STYLE@"/>
-
- <!-- Blank lines between paragraphs, please -->
- <xsl:param name="latex.use.parskip" select="1"/>
-
- <!-- Least bad current option for constructing tables -->
- <xsl:param name="latex.use.ltxtable" select="1"/>
- <xsl:param name="latex.use.longtable" select="1"/>
-
- <!-- LaTeX2e documentclass options. -->
- <xsl:param name="latex.documentclass.common"/>
- <xsl:param name="latex.documentclass.book">10pt,twoside,openright</xsl:param>
-
- <!-- This documentation is in English (or maybe Bad English) -->
- <xsl:param name="latex.babel.language" select="'english'"/>
- <xsl:param name="l10n.gentext.default.language" select="'en'"/>
-
- <!-- Where to find "admonition" graphics -->
- <xsl:param name="admon.graphics.path" select="'@XSLT_DB2LATEX_ADMONITIONS@'"/>
-
- <!-- ANSI C function prototypes, please -->
- <xsl:param name="funcsynopsis.style">ansi</xsl:param>
-
- <!-- Local modifications to db2latex's mapping rules -->
- <xsl:param name="latex.mapping.xml" select="document('isc-docbook-latex-mappings.xml')"/>
-
- <!-- Patch around db2latex (0.8pre1) bug -->
- <xsl:template match="copyright/year">
- <xsl:apply-templates />
- <xsl:if test="position() != last()">
- <xsl:text>, </xsl:text>
- </xsl:if>
- </xsl:template>
-
- <!-- Include our copyright generator -->
- <xsl:include href="copyright.xsl"/>
-
- <!-- Set comment convention for this output format -->
- <xsl:param name="isc.copyright.leader">% </xsl:param>
-
- <!-- Intercept top level to prepend copyright -->
- <xsl:template match="/">
- <xsl:value-of select="$isc.copyright"/>
- <xsl:apply-imports/>
- </xsl:template>
-
- <!--
- - Add support for multiple <para/> elements in a table entry.
- - db2latex is already typesetting the table entry as a parbox,
- - so we just have to insert the paragraph breaks.
- -->
- <xsl:template match="tbody/row/entry/para[position() != last()]">
- <xsl:apply-imports/>
- <xsl:text> \par </xsl:text>
- </xsl:template>
-
- <!--
- - Add support for <optional/> in <programlisting/>.
- -->
- <xsl:template match="optional" mode="latex.verbatim">
- <xsl:text>[</xsl:text>
- <xsl:apply-templates mode="latex.verbatim"/>
- <xsl:text>]</xsl:text>
- </xsl:template>
-
- <!--
- - Customize the title page. Are we having fun yet?
- -
- - NB: filename of graphic specified without extension.
- - LaTeX includes file.eps, PDFLaTeX includes file.pdf.
- -
- - Spacing and font sizes could probably use some work.
- -->
- <xsl:param name="latex.maketitle">
- <xsl:text>
- \begin{titlepage}
- \null\vfil
- \vskip 60pt
- \begin{center}%
- { %\LARGE
- \Huge
- \bfseries
- </xsl:text>
- <xsl:for-each select="/book/title">
- <xsl:call-template name="text"/>
- </xsl:for-each>
- <xsl:text>
- \par}%
- \vskip 3em%
- { %\large
- \Large
- \lineskip .75em%
- </xsl:text>
- <xsl:for-each select="/book/bookinfo/releaseinfo[1]">
- <xsl:call-template name="text"/>
- </xsl:for-each>
- <xsl:text>
- \par}
- %\vskip 1.5em%
- \vfil
- % Not sure exactly how much to trim logo, but given that
- % this is a centered environment, we need not be too precise
- % so long as the image is centered in the input PDF, we
- % trim enough for it to fit on page, and we do not trim
- % so much that we clip out part of the graphic itself.
- % This seems to work, anyway.
- \includegraphics[trim=400 400 400 400,scale=2.5]{isc-logo}
- \end{center}\par
- \vfil\null
- \end{titlepage}
- </xsl:text>
- <xsl:text> </xsl:text>
- </xsl:param>
-
- <!-- Add version in footer. -->
- <xsl:param name="latex.book.preamble.post">
- <xsl:text>
- \pagestyle{fancy}
- \fancyfoot[ce,co]{\thepage}
- \fancyfoot[le,ro]{@BIND9_VERSIONSTRING@}
- \renewcommand{\headrulewidth}{0.4 pt}
- \fancypagestyle{plain}{%
- \fancyhf{}%
- \fancyfoot[ce,co]{\thepage}%
- \fancyfoot[le,ro]{@BIND9_VERSIONSTRING@}%
- \renewcommand{\headrulewidth}{0 pt}
- }
- </xsl:text>
- </xsl:param>
-
- <!--
- - More front matter: copyright notice, CVS revision number, table
- - of contents.
- -->
- <xsl:template match="book/bookinfo">
- <xsl:text>\thispagestyle{empty} </xsl:text>
- <xsl:apply-imports/>
- <xsl:text>\begin{center} </xsl:text>
- <xsl:value-of select="$isc.copyright.text"/>
- <xsl:text>\end{center} </xsl:text>
- <xsl:for-each select="/book/bookinfo/releaseinfo[position() > 1]">
- <xsl:text>\begin{center}</xsl:text>
- <xsl:call-template name="text"/>
- <xsl:text>\end{center} </xsl:text>
- </xsl:for-each>
- <xsl:text>
- \vfill
- \begin{center}
- Internet Systems Consortium \\
- 950 Charter Street \\
- Redwood City, California \\
- USA \\
- http://www.isc.org/
- \end{center}
- </xsl:text>
- <xsl:text>
- \newpage
- \pagenumbering{roman}
- \tableofcontents
- \newpage
- \pagenumbering{arabic}
- </xsl:text>
- </xsl:template>
-
- <!--
- - Try to avoid some weird looking line breaks.
- -
- - This doesn't really work right, so disable for now.
- -->
- <xsl:template match="literal" mode="disabled">
- <xsl:text>\mbox{</xsl:text>
- <xsl:apply-imports/>
- <xsl:text>}</xsl:text>
- </xsl:template>
-
-</xsl:stylesheet>
-
-<!--
- - Local variables:
- - mode: sgml
- - End:
- -->
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id: isc-docbook-text.xsl,v 1.3 2007/06/19 23:47:13 tbox Exp $ -->
-
<!-- Tweaks to Docbook-XSL HTML for producing flat ASCII text. -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id: isc-manpage.xsl.in,v 1.9 2007/06/18 23:47:34 tbox Exp $ -->
-
<!-- ISC customizations for Docbook-XSL manual page generator. -->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:db="http://docbook.org/ns/docbook">
<!-- Import the Docbook manpages stuff -->
- <xsl:import href="@XSLT_DOCBOOK_STYLE_MAN@"/>
-
+ <xsl:include href="@XSLT_DOCBOOK_STYLE_MAN@"/>
+
<!-- Include our copyright generator -->
<xsl:include href="copyright.xsl"/>
<!-- Set comment string for this output format -->
<xsl:param name="isc.copyright.leader">.\" </xsl:param>
+ <xsl:param name="isc.copyright.breakline"/>
<!-- We're not writing any kind of SGML, thanks -->
- <xsl:output method="text" encoding="us-ascii"/>
+ <xsl:output method="text" encoding="us-ascii" indent="no"/>
<!-- ANSI C function prototypes, please -->
<xsl:param name="funcsynopsis.style">ansi</xsl:param>
<!-- Stuff we want in our nroff preamble. -->
<xsl:variable name="isc.nroff.preamble">
- <xsl:text>.\" </xsl:text>
- <xsl:text>.\" $Id$ </xsl:text>
<xsl:text>.\" </xsl:text>
<xsl:text>.hy 0 </xsl:text>
<xsl:text>.ad l </xsl:text>
<!-- ISC customizations for Docbook-XSL HTML generator -->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:db="http://docbook.org/ns/docbook">
<!-- Import the Docbook HTML stuff -->
<xsl:import href="@XSLT_DOCBOOK_STYLE_HTML@"/>
<!-- Set comment convention for this output format -->
<xsl:param name="isc.copyright.leader"> - </xsl:param>
+ <xsl:param name="isc.copyright.breakline"/>
+
+ <!-- Generate consistent id attributes -->
+ <xsl:param name="generate.consistent.ids" select="1"/>
<!-- Override Docbook template to insert copyright -->
<xsl:template name="user.preroot">
+++ /dev/null
-<!--
- - Copyright (C) 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
- -
- - Permission to use, copy, modify, and/or distribute this software for any
- - purpose with or without fee is hereby granted, provided that the above
- - copyright notice and this permission notice appear in all copies.
- -
- - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
- - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
- - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
- - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
- - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
- - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- - PERFORMANCE OF THIS SOFTWARE.
--->
-
-<!-- ISC customizations for db2latex generator -->
-
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
-
- <!-- Import the db2latex stuff -->
- <xsl:import href="@XSLT_DB2LATEX_STYLE@"/>
-
- <!-- Blank lines between paragraphs, please -->
- <xsl:param name="latex.use.parskip" select="1"/>
-
- <!-- Least bad current option for constructing tables -->
- <xsl:param name="latex.use.ltxtable" select="1"/>
- <xsl:param name="latex.use.longtable" select="1"/>
-
- <!-- LaTeX2e documentclass options. -->
- <xsl:param name="latex.documentclass.common"/>
- <xsl:param name="latex.documentclass.book">10pt,twoside,openright</xsl:param>
-
- <!-- This documentation is in English (or maybe Bad English) -->
- <xsl:param name="latex.babel.language" select="'english'"/>
- <xsl:param name="l10n.gentext.default.language" select="'en'"/>
-
- <!-- Where to find "admonition" graphics -->
- <xsl:param name="admon.graphics.path" select="'@XSLT_DB2LATEX_ADMONITIONS@'"/>
-
- <!-- ANSI C function prototypes, please -->
- <xsl:param name="funcsynopsis.style">ansi</xsl:param>
-
- <!-- Local modifications to db2latex's mapping rules -->
- <xsl:param name="latex.mapping.xml" select="document('isc-docbook-latex-mappings.xml')"/>
-
- <!-- Patch around db2latex (0.8pre1) bug -->
- <xsl:template match="copyright/year">
- <xsl:apply-templates />
- <xsl:if test="position() != last()">
- <xsl:text>, </xsl:text>
- </xsl:if>
- </xsl:template>
-
- <!-- Number by section, not chapter -->
- <xsl:param name="chapter.autolabel" select="1"/>
- <xsl:param name="section.autolabel" select="1"/>
- <xsl:param name="section.label.includes.component.label" select="0"/>
-
- <!-- Suppress title page, header -->
- <xsl:param name="latex.maketitle"/>
- <xsl:param name="latex.use.fancyhdr"/>
-
- <!-- Single column -->
- <xsl:param name="latex.documentclass.article">a4paper,10pt,twoside,openright</xsl:param>
-
- <!--
- - Add support for multiple <para/> elements in a table entry.
- - db2latex is already typesetting the table entry as a parbox,
- - so we just have to insert the paragraph breaks.
- -->
- <xsl:template match="tbody/row/entry/para[position() != last()]">
- <xsl:apply-imports/>
- <xsl:text> \par </xsl:text>
- </xsl:template>
-
- <!--
- - Add support for <optional/> in <programlisting/>.
- -->
- <xsl:template match="optional" mode="latex.verbatim">
- <xsl:text>[</xsl:text>
- <xsl:apply-templates mode="latex.verbatim"/>
- <xsl:text>]</xsl:text>
- </xsl:template>
-
- <!--
- - Try to avoid some weird looking line breaks.
- -
- - This doesn't really work right, so disable for now.
- -->
- <xsl:template match="literal" mode="disabled">
- <xsl:text>\mbox{</xsl:text>
- <xsl:apply-imports/>
- <xsl:text>}</xsl:text>
- </xsl:template>
-
-</xsl:stylesheet>
-
-<!--
- - Local variables:
- - mode: sgml
- - End:
- -->
--- /dev/null
+<!--
+ - Copyright (C) 2014, 2015 Internet Systems Consortium, Inc. ("ISC")
+ -
+ - Permission to use, copy, modify, and/or distribute this software for any
+ - purpose with or without fee is hereby granted, provided that the above
+ - copyright notice and this permission notice appear in all copies.
+ -
+ - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
+ - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
+ - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
+ - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
+ - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
+ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+ - PERFORMANCE OF THIS SOFTWARE.
+-->
+
+<!-- ISC customizations for dblatex generator -->
+
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:db="http://docbook.org/ns/docbook">
+</xsl:stylesheet>
+
+<!--
+ - Local variables:
+ - mode: sgml
+ - End:
+ -->
- There's probably a better way to do this, but this will work for now.
-->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:db="http://docbook.org/ns/docbook">
<xsl:variable name="mdash" select="'—'"/>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2009, 2014 Internet Systems Consortium, Inc. ("ISC")
-
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry id="man.isc-config.sh">
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.isc-config.sh">
+ <info>
+ <date>2009-02-18</date>
+ </info>
<refentryinfo>
- <date>February 18, 2009</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</refnamediv>
<refsynopsisdiv>
- <cmdsynopsis>
+ <cmdsynopsis sepchar=" ">
<command>isc-config.sh</command>
- <arg><option>--cflags</option></arg>
- <arg><option>--exec-prefix</option></arg>
- <arg><option>--libs</option></arg>
- <arg><option>--prefix</option></arg>
- <arg><option>--version</option></arg>
+ <arg choice="opt" rep="norepeat"><option>--cflags</option></arg>
+ <arg choice="opt" rep="norepeat"><option>--exec-prefix</option></arg>
+ <arg choice="opt" rep="norepeat"><option>--libs</option></arg>
+ <arg choice="opt" rep="norepeat"><option>--prefix</option></arg>
+ <arg choice="opt" rep="norepeat"><option>--version</option></arg>
<arg choice="opt" rep="repeat">libraries</arg>
</cmdsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><command>isc-config.sh</command>
prints information related to the installed version of ISC BIND,
such as the compiler and linker flags required to compile
(Some libraries require other libraries, so are implied.)
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OPTIONS</title>
+ <refsection><info><title>OPTIONS</title></info>
+
<variablelist>
</variablelist>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para><command>isc-config.sh</command>
returns an exit status of 1 if
invoked with invalid arguments or no arguments at all.
It returns 0 if information was successfully printed.
</para>
- </refsect1>
-
- <refsect1>
- <title>AUTHOR</title>
- <para><corpauthor>Internet Systems Consortium</corpauthor>
- </para>
- </refsect1>
+ </refsection>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
The BIND 9 lightweight resolver library is a simple, name service
independent stub resolver library. It provides hostname-to-address
The library and resolver daemon communicate using a simple
UDP-based protocol.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>OVERVIEW</title>
+ <refsection><info><title>OVERVIEW</title></info>
+
<para>
The lwresd library implements multiple name service APIs.
The standard
resolver daemon. The use of this low-level API in clients
and servers is outlined in the following sections.
</para>
- </refsect1>
- <refsect1>
- <title>CLIENT-SIDE LOW-LEVEL API CALL FLOW</title>
+ </refsection>
+ <refsection><info><title>CLIENT-SIDE LOW-LEVEL API CALL FLOW</title></info>
+
<para>
When a client program wishes to make an lwres request using the
native low-level API, it typically performs the following
called <varname>pkt</varname> below.
</para>
<para>
- (2) Set <structfield>pkt.recvlength</structfield> to the maximum length
+ (2) Set <varname remap="structfield">pkt.recvlength</varname> to the maximum length
we will accept.
This is done so the receiver of our packets knows how large our receive
buffer is. The "default" is a constant in
<filename>lwres.h</filename>: <constant>LWRES_RECVLENGTH = 4096</constant>.
</para>
<para>
- (3) Set <structfield>pkt.serial</structfield>
+ (3) Set <varname remap="structfield">pkt.serial</varname>
to a unique serial number. This value is echoed
back to the application by the remote server.
</para>
<para>
- (4) Set <structfield>pkt.pktflags</structfield>. Usually this is set to
+ (4) Set <varname remap="structfield">pkt.pktflags</varname>. Usually this is set to
0.
</para>
<para>
- (5) Set <structfield>pkt.result</structfield> to 0.
+ (5) Set <varname remap="structfield">pkt.result</varname> to 0.
</para>
<para>
(6) Call <function>lwres_*request_render()</function>,
(9) Verify that the opcode and serial match a request, and process the
packet specific information contained in the body.
</para>
- </refsect1>
- <refsect1>
- <title>SERVER-SIDE LOW-LEVEL API CALL FLOW</title>
+ </refsection>
+ <refsection><info><title>SERVER-SIDE LOW-LEVEL API CALL FLOW</title></info>
+
<para>
When implementing the server side of the lightweight resolver
protocol using the lwres library, a sequence of actions like the
(2) Process the request in the data specific type.
</para>
<para>
- (3) Set the <structfield>pkt.result</structfield>,
- <structfield>pkt.recvlength</structfield> as above. All other fields
+ (3) Set the <varname remap="structfield">pkt.result</varname>,
+ <varname remap="structfield">pkt.recvlength</varname> as above. All other fields
can
be left untouched since they were filled in by the <function>*_parse()</function> call
above. If using <function>lwres_*response_render()</function>,
- <structfield>pkt.pktflags</structfield> will be set up
+ <varname remap="structfield">pkt.pktflags</varname> will be set up
properly. Otherwise, the <constant>LWRES_LWPACKETFLAG_RESPONSE</constant> bit should be
set.
</para>
<para>
(5) Send the resulting packet to the client.
</para>
- <para></para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ <para/>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres_gethostent</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
+ <refsection><info><title>DESCRIPTION</title></info>
- <title>DESCRIPTION</title>
+
<para>
These functions provide bounds checked access to a region of memory
where data is being read or written.
checks for underflow.
These functions do not allocate or deallocate memory.
They just change the value of
- <structfield>used</structfield>.
+ <varname remap="structfield">used</varname>.
</para>
<para>
A buffer is re-initialised by
<function>lwres_buffer_clear()</function>.
The function sets
- <structfield>used</structfield>,
- <structfield>current</structfield>
+ <varname remap="structfield">used</varname>,
+ <varname remap="structfield">current</varname>
and
- <structfield>active</structfield>
+ <varname remap="structfield">active</varname>
to zero.
</para>
<para><function>lwres_buffer_first</function>
makes the consumed region of buffer
<parameter>*p</parameter>
empty by setting
- <structfield>current</structfield>
+ <varname remap="structfield">current</varname>
to zero (the start of the buffer).
</para>
<para><function>lwres_buffer_forward()</function>
to
<parameter>base</parameter>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
-
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_conf_init()</function>
creates an empty
<type>FILE</type>
<parameter>fp</parameter>.
</para>
- </refsect1>
- <refsect1>
+ </refsection>
+ <refsection><info><title>RETURN VALUES</title></info>
- <title>RETURN VALUES</title>
+
<para><function>lwres_conf_parse()</function>
returns <errorcode>LWRES_R_SUCCESS</errorcode>
If this happens, the function returns
<errorcode>LWRES_R_FAILURE</errorcode>.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>stdio</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
<refentrytitle>resolver</refentrytitle><manvolnum>5</manvolnum>
</citerefentry>.
</para>
- </refsect1>
- <refsect1>
- <title>FILES</title>
+ </refsection>
+ <refsection><info><title>FILES</title></info>
+
<para><filename>/etc/resolv.conf</filename>
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001, 2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_context_create()</function>
creates a <type>lwres_context_t</type> structure for use in
written to this receive buffer is returned in
<parameter>*recvd_len</parameter>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para><function>lwres_context_create()</function>
returns <errorcode>LWRES_R_NOMEMORY</errorcode> if memory for
<function>lwres_context_sendrecv()</function>
times out waiting for a response.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres_conf_init</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
<refentrytitle>free</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
These are low-level routines for creating and parsing
lightweight resolver name-to-address lookup request and
Any memory associated with ancillary buffers and strings for
those structures is also discarded.
</para>
- </refsect1>
- <refsect1>
- <title>RETURN VALUES</title>
+ </refsection>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
The getaddrbyname opcode functions
<function>lwres_gabnrequest_render()</function>,
These functions will return
<errorcode>LWRES_R_FAILURE</errorcode>
if
- <structfield>pktflags</structfield>
+ <varname remap="structfield">pktflags</varname>
in the packet header structure
<type>lwres_lwpacket_t</type>
indicate that the packet is not a response to an earlier query.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres_packet</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_gai_strerror()</function>
returns an error message corresponding to an error code returned by
used by
<function>lwres_getaddrinfo()</function>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>SEE ALSO</title>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>strerror</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
<refentrytitle>RFC2133</refentrytitle>
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001, 2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_getaddrinfo()</function>
is used to get a list of IP addresses and port numbers for host
<function>lwres_getaddrinfo()</function>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para><function>lwres_getaddrinfo()</function>
returns zero on success or one of the error codes listed in
<function>lwres_getaddrinfo()</function> returns
<errorcode>EAI_NONAME</errorcode>.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
These functions provide hostname-to-address and
address-to-hostname lookups by means of the lightweight resolver.
<function>struct hostent()</function> it created.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
The functions
<function>lwres_gethostbyname()</function>,
<type>errno</type> to <errorcode>ERANGE</errorcode>.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>gethostent</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
<refentrytitle>lwres_hstrerror</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>BUGS</title>
+ <refsection><info><title>BUGS</title></info>
+
<para><function>lwres_gethostbyname()</function>,
<function>lwres_gethostbyname2()</function>,
<function>lwres_gethostbyaddr()</function>
<type>NIS</type>,
consequently the above functions don't, either.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001, 2003 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
These functions perform thread safe, protocol independent
<constant>h_aliases</constant> is freed, as is the memory for
the <type>hostent</type> structure itself.
</para>
- </refsect1>
- <refsect1>
- <title>RETURN VALUES</title>
+ </refsection>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
If an error occurs,
<function>lwres_getipnodebyname()</function>
</citerefentry>
translates these error codes to suitable error messages.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>RFC2553</refentrytitle>
</citerefentry>,
<refentrytitle>lwres_hstrerror</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
This function is equivalent to the
</varlistentry>
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para><function>lwres_getnameinfo()</function>
returns 0 on success or a non-zero error code if an error occurs.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>RFC2133</refentrytitle>
</citerefentry>,
<refentrytitle>lwres_net_ntop</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>.
</para>
- </refsect1>
- <refsect1>
- <title>BUGS</title>
+ </refsection>
+ <refsection><info><title>BUGS</title></info>
+
<para>
RFC2133 fails to define what the nonzero return values of
<citerefentry>
</citerefentry>
are.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</para>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_getrrsetbyname()</function>
gets a set of resource records associated with a
<parameter>hostname</parameter>, <parameter>class</parameter>,
rrset</type> created by a call to
<function>lwres_getrrsetbyname()</function>.
</para>
- <para></para>
- </refsect1>
- <refsect1>
- <title>RETURN VALUES</title>
+ <para/>
+ </refsection>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para><function>lwres_getrrsetbyname()</function>
returns zero on success, and one of the following error codes if
an error occurred:
<varlistentry>
<term><constant/></term>
<listitem>
- <para></para>
+ <para/>
</listitem>
</varlistentry>
</variablelist>
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
These are low-level routines for creating and parsing
lightweight resolver address-to-name lookup request and
ancillary buffers and strings for those structures is also
discarded.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
The getnamebyaddr opcode functions
<function>lwres_gnbarequest_render()</function>,
These functions will return
<errorcode>LWRES_R_FAILURE</errorcode>
if
- <structfield>pktflags</structfield>
+ <varname remap="structfield">pktflags</varname>
in the packet header structure
<type>lwres_lwpacket_t</type>
indicate that the packet is not a response to an earlier query.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres_packet</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_herror()</function>
prints the string <parameter>s</parameter> on
</varlistentry>
</variablelist>
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
The string <errorname>Unknown resolver error</errorname> is returned by
<function>lwres_hstrerror()</function>
<constant>lwres_h_errno</constant>
is not a valid error code.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>herror</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_net_ntop()</function>
converts an IP address of protocol family
ASCII representation of the address.
</para>
- </refsect1>
- <refsect1>
- <title>RETURN VALUES</title>
+ </refsection>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
If successful, the function returns <parameter>dst</parameter>:
supported.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>RFC1884</refentrytitle>
</citerefentry>,
<refentrytitle>errno</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
+<!DOCTYPE book [
+<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
These are low-level routines for creating and parsing
lightweight resolver no-op request and response messages.
<parameter>structp</parameter>.
</para>
- </refsect1>
- <refsect1>
- <title>RETURN VALUES</title>
+ </refsection>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
The no-op opcode functions
<function>lwres_nooprequest_render()</function>,
<type>lwres_lwpacket_t</type>
indicate that the packet is not a response to an earlier query.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres_packet</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para>
These functions rely on a
<type>struct lwres_lwpacket</type>
<type>lwres_lwpacket_t</type>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
Successful calls to
<function>lwres_lwpacket_renderheader()</function> and
return <errorcode>LWRES_R_UNEXPECTEDEND</errorcode>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
- [<!ENTITY mdash "—">]>
<!--
- Copyright (C) 2004, 2005, 2007, 2014 Internet Systems Consortium, Inc. ("ISC")
- Copyright (C) 2000, 2001 Internet Software Consortium.
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
-<refentry>
-
+<!-- Converted by db4-upgrade version 1.0 -->
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0">
+ <info>
+ <date>2007-06-18</date>
+ </info>
<refentryinfo>
- <date>June 18, 2007</date>
+ <corpname>ISC</corpname>
+ <corpauthor>Internet Systems Consortium, Inc.</corpauthor>
</refentryinfo>
<refmeta>
</funcsynopsis>
</refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
+ <refsection><info><title>DESCRIPTION</title></info>
+
<para><function>lwres_string_parse()</function>
retrieves a DNS-encoded string starting the current pointer of
function call is made available through
<parameter>*structp</parameter>.
</para>
- </refsect1>
+ </refsection>
- <refsect1>
- <title>RETURN VALUES</title>
+ <refsection><info><title>RETURN VALUES</title></info>
+
<para>
Successful calls to
<function>lwres_string_parse()</function>
small.
</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
+ </refsection>
+ <refsection><info><title>SEE ALSO</title></info>
+
<para><citerefentry>
<refentrytitle>lwres_buffer</refentrytitle><manvolnum>3</manvolnum>
</citerefentry>,
</citerefentry>.
</para>
- </refsect1>
-</refentry><!--
- - Local variables:
- - mode: sgml
- - End:
--->
+ </refsection>
+</refentry>
PERL = @PERL@
LATEX = @LATEX@
PDFLATEX = @PDFLATEX@
+DBLATEX = @DBLATEX@
W3M = @W3M@
###
projects / thirdparty / bind9.git / commitdiff
