upstream/bind9
1
0
Fork 0
mirror of https://github.com/isc-projects/bind9.git synced 2026-03-03 05:50:39 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

regen

Browse source
This commit is contained in:
Mark Andrews 2004-08-22 23:53:39 +00:00
parent d5bf55ac93
commit 5b7b2ddd6c
41 changed files with 5076 additions and 8825 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
bin/check/named-checkconf.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: named-checkconf.html,v 1.9.18.3 2004/06/03 04:17:52 marka Exp $ -->
<!-- $Id: named-checkconf.html,v 1.9.18.4 2004/08/22 23:53:24 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>named-checkconf</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>named-checkconf</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,23 +62,21 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>named-checkconf</B
> [<TT
> [<VAR
CLASS="OPTION"
>-v</TT
>] [<TT
>-v</VAR
>] [<VAR
CLASS="OPTION"
>-j</TT
>] [<TT
>-j</VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
></TT
>] {filename} [<TT
>directory</VAR
></VAR
>] {filename} [<VAR
CLASS="OPTION"
>-z</TT
>-z</VAR
>]</P
></DIV
><DIV
@ -109,11 +107,9 @@ NAME="AEN30"
CLASS="VARIABLELIST"
><DL
><DT
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
></DT
><DD
><P

124
bin/check/named-checkzone.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: named-checkzone.html,v 1.11.18.3 2004/06/03 04:17:52 marka Exp $ -->
<!-- $Id: named-checkzone.html,v 1.11.18.4 2004/08/22 23:53:24 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>named-checkzone</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>named-checkzone</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,69 +62,57 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>named-checkzone</B
> [<TT
> [<VAR
CLASS="OPTION"
>-d</TT
>] [<TT
>-d</VAR
>] [<VAR
CLASS="OPTION"
>-j</TT
>] [<TT
>-j</VAR
>] [<VAR
CLASS="OPTION"
>-q</TT
>] [<TT
>-q</VAR
>] [<VAR
CLASS="OPTION"
>-v</TT
>] [<TT
>-v</VAR
>] [<VAR
CLASS="OPTION"
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>class</I
></TT
></TT
>] [<TT
>class</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>mode</I
></TT
></TT
>] [<TT
>mode</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>mode</I
></TT
></TT
>] [<TT
>mode</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-o <TT
>-o <VAR
CLASS="REPLACEABLE"
><I
>filename</I
></TT
></TT
>] [<TT
>filename</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
></TT
>] [<TT
>directory</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-w <TT
>-w <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
></TT
>] [<TT
>directory</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-D</TT
>-D</VAR
>] {zonename} {filename}</P
></DIV
><DIV
@ -196,11 +184,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>class</I
></TT
>class</VAR
></DT
><DD
><P
@ -208,11 +194,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>mode</I
></TT
>mode</VAR
></DT
><DD
><P
@ -235,11 +219,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>mode</I
></TT
>mode</VAR
></DT
><DD
><P
@ -259,11 +241,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-o <TT
>-o <VAR
CLASS="REPLACEABLE"
><I
>filename</I
></TT
>filename</VAR
></DT
><DD
><P
@ -274,11 +254,9 @@ CLASS="FILENAME"
</P
></DD
><DT
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
></DT
><DD
><P
@ -291,11 +269,9 @@ CLASS="FILENAME"
</P
></DD
><DT
>-w <TT
>-w <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
></DT
><DD
><P

596
bin/dig/dig.html
View file

File diff suppressed because it is too large Load diff

246
bin/dig/host.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: host.html,v 1.7.18.3 2004/04/13 12:17:09 marka Exp $ -->
<!-- $Id: host.html,v 1.7.18.4 2004/08/22 23:53:25 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>host</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>host</A
></H1
></A
>host</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -56,55 +56,45 @@ NAME="AEN11"
><B
CLASS="COMMAND"
>host</B
> [<TT
> [<VAR
CLASS="OPTION"
>-aCdlnrTwv</TT
>] [<TT
>-aCdlnrTwv</VAR
>] [<VAR
CLASS="OPTION"
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>class</I
></TT
></TT
>] [<TT
>class</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-N <TT
>-N <VAR
CLASS="REPLACEABLE"
><I
>ndots</I
></TT
></TT
>] [<TT
>ndots</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-R <TT
>-R <VAR
CLASS="REPLACEABLE"
><I
>number</I
></TT
></TT
>] [<TT
>number</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>type</I
></TT
></TT
>] [<TT
>type</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-W <TT
>-W <VAR
CLASS="REPLACEABLE"
><I
>wait</I
></TT
></TT
>] [<TT
>wait</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-4</TT
>] [<TT
>-4</VAR
>] [<VAR
CLASS="OPTION"
>-6</TT
>-6</VAR
>] {name} [server]</P
></DIV
><DIV
@ -128,11 +118,9 @@ CLASS="COMMAND"
>
prints a short summary of its command line arguments and options.</P
><P
><TT
><VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
> 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 <B
@ -140,11 +128,9 @@ CLASS="COMMAND"
>host</B
> will by default
perform a reverse lookup for that address.
<TT
<VAR
CLASS="PARAMETER"
><I
>server</I
></TT
>server</VAR
> is an optional argument which is either
the name or IP address of the name server that <B
CLASS="COMMAND"
@ -156,45 +142,41 @@ CLASS="FILENAME"
>/etc/resolv.conf</TT
>.</P
><P
>The <TT
>The <VAR
CLASS="OPTION"
>-a</TT
>-a</VAR
> (all) option is equivalent to setting the
<TT
<VAR
CLASS="OPTION"
>-v</TT
>-v</VAR
> option and asking <B
CLASS="COMMAND"
>host</B
> to make
a query of type ANY.</P
><P
>When the <TT
>When the <VAR
CLASS="OPTION"
>-C</TT
>-C</VAR
> option is used, <B
CLASS="COMMAND"
>host</B
>
will attempt to display the SOA records for zone
<TT
<VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
> 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
>The <TT
>The <VAR
CLASS="OPTION"
>-c</TT
>-c</VAR
> option instructs to make a DNS query of class
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>. This can be used to lookup Hesiod or
Chaosnet class resource records. The default class is IN (Internet).</P
><P
@ -202,61 +184,57 @@ Chaosnet class resource records. The default class is IN (Internet).</P
CLASS="COMMAND"
>host</B
> when the
<TT
<VAR
CLASS="OPTION"
>-d</TT
> or <TT
>-d</VAR
> or <VAR
CLASS="OPTION"
>-v</TT
>-v</VAR
> option is used. The two
options are equivalent. They have been provided for backwards
compatibility. In previous versions, the <TT
compatibility. In previous versions, the <VAR
CLASS="OPTION"
>-d</TT
>-d</VAR
> option
switched on debugging traces and <TT
switched on debugging traces and <VAR
CLASS="OPTION"
>-v</TT
>-v</VAR
> enabled verbose
output.</P
><P
>List mode is selected by the <TT
>List mode is selected by the <VAR
CLASS="OPTION"
>-l</TT
>-l</VAR
> option. This makes
<B
CLASS="COMMAND"
>host</B
> perform a zone transfer for zone
<TT
<VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
>. Transfer the zone printing out the NS, PTR
and address records (A/AAAA). If combined with <TT
and address records (A/AAAA). If combined with <VAR
CLASS="OPTION"
>-a</TT
>-a</VAR
>
all records will be printed. </P
><P
>The <TT
>The <VAR
CLASS="OPTION"
>-i</TT
>-i</VAR
>
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
>The <TT
>The <VAR
CLASS="OPTION"
>-N</TT
>-N</VAR
> option sets the number of dots that have to be
in <TT
in <VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
> for it to be considered absolute. The
default value is that defined using the ndots statement in
<TT
@ -278,31 +256,27 @@ CLASS="FILENAME"
>.</P
><P
>The number of UDP retries for a lookup can be changed with the
<TT
<VAR
CLASS="OPTION"
>-R</TT
> option. <TT
>-R</VAR
> option. <VAR
CLASS="PARAMETER"
><I
>number</I
></TT
>number</VAR
> indicates
how many times <B
CLASS="COMMAND"
>host</B
> will repeat a query that does
not get answered. The default number of retries is 1. If
<TT
<VAR
CLASS="PARAMETER"
><I
>number</I
></TT
>number</VAR
> is negative or zero, the number of
retries will default to 1.</P
><P
>Non-recursive queries can be made via the <TT
>Non-recursive queries can be made via the <VAR
CLASS="OPTION"
>-r</TT
>-r</VAR
> option.
Setting this option clears the <SPAN
CLASS="TYPE"
@ -313,15 +287,13 @@ CLASS="COMMAND"
>host</B
> makes.
This should mean that the name server receiving the query will not
attempt to resolve <TT
attempt to resolve <VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
>. The
<TT
<VAR
CLASS="OPTION"
>-r</TT
>-r</VAR
> option enables <B
CLASS="COMMAND"
>host</B
@ -334,38 +306,36 @@ referrals to other name servers.</P
CLASS="COMMAND"
>host</B
> uses UDP when making queries. The
<TT
<VAR
CLASS="OPTION"
>-T</TT
>-T</VAR
> 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 <TT
>The <VAR
CLASS="OPTION"
>-4</TT
>-4</VAR
> option forces <B
CLASS="COMMAND"
>host</B
> to only
use IPv4 query transport. The <TT
use IPv4 query transport. The <VAR
CLASS="OPTION"
>-6</TT
>-6</VAR
> option forces
<B
CLASS="COMMAND"
>host</B
> to only use IPv6 query transport.</P
><P
>The <TT
>The <VAR
CLASS="OPTION"
>-t</TT
>-t</VAR
> option is used to select the query type.
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
> can be any recognised query type: CNAME,
NS, SOA, SIG, KEY, AXFR, etc. When no query type is specified,
<B
@ -373,15 +343,13 @@ CLASS="COMMAND"
>host</B
> automatically selects an appropriate query
type. By default it looks for A records, but if the
<TT
<VAR
CLASS="OPTION"
>-C</TT
>-C</VAR
> option was given, queries will be made for SOA
records, and if <TT
records, and if <VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
> is a dotted-decimal IPv4
address or colon-delimited IPv6 address, <B
CLASS="COMMAND"
@ -392,35 +360,31 @@ serial number can be specified by appending an equal followed by the
starting serial number (e.g. -t IXFR=12345678).</P
><P
>The time to wait for a reply can be controlled through the
<TT
<VAR
CLASS="OPTION"
>-W</TT
> and <TT
>-W</VAR
> and <VAR
CLASS="OPTION"
>-w</TT
>-w</VAR
> options. The
<TT
<VAR
CLASS="OPTION"
>-W</TT
>-W</VAR
> option makes <B
CLASS="COMMAND"
>host</B
> wait for
<TT
<VAR
CLASS="PARAMETER"
><I
>wait</I
></TT
> seconds. If <TT
>wait</VAR
> seconds. If <VAR
CLASS="PARAMETER"
><I
>wait</I
></TT
>wait</VAR
>
is less than one, the wait interval is set to one second. When the
<TT
<VAR
CLASS="OPTION"
>-w</TT
>-w</VAR
> option is used, <B
CLASS="COMMAND"
>host</B

248
bin/dig/nslookup.html
View file

@ -14,16 +14,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: nslookup.html,v 1.1.10.2 2004/08/21 07:35:34 marka Exp $ -->
<!-- $Id: nslookup.html,v 1.1.10.3 2004/08/22 23:53:25 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>nslookup</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -34,8 +34,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>nslookup</A
></H1
></A
>nslookup</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -55,9 +55,9 @@ NAME="AEN11"
><B
CLASS="COMMAND"
>nslookup</B
> [<TT
> [<VAR
CLASS="OPTION"
>-option</TT
>-option</VAR
>] [name | -] [server]</P
></DIV
><DIV
@ -116,11 +116,11 @@ arguments and are prefixed with a hyphen. For example, to
change the default query type to host information, and the initial timeout to 10 seconds, type:
<DIV
CLASS="INFORMALEXAMPLE"
><P
></P
><A
NAME="AEN33"
></A
><P
></P
><PRE
CLASS="PROGRAMLISTING"
>nslookup -query=hinfo -timeout=10</PRE
@ -158,128 +158,118 @@ search list is used to qualify the name.</P
the name.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>server</TT
> <TT
>server</CODE
> <VAR
CLASS="REPLACEABLE"
><I
>domain</I
></TT
>domain</VAR
></DT
><DD
><P
></P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>lserver</TT
> <TT
>lserver</CODE
> <VAR
CLASS="REPLACEABLE"
><I
>domain</I
></TT
>domain</VAR
></DT
><DD
><P
>Change the default server to <TT
>Change the default server to <VAR
CLASS="REPLACEABLE"
><I
>domain</I
></TT
>; <TT
>domain</VAR
>; <CODE
CLASS="CONSTANT"
>lserver</TT
>lserver</CODE
> uses the initial
server to look up information about <TT
server to look up information about <VAR
CLASS="REPLACEABLE"
><I
>domain</I
></TT
>, while <TT
>domain</VAR
>, while <CODE
CLASS="CONSTANT"
>server</TT
>server</CODE
> uses
the current default server. If an authoritative answer can't be
found, the names of servers that might have the answer are
returned.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>root</TT
>root</CODE
></DT
><DD
><P
>not implemented</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>finger</TT
>finger</CODE
></DT
><DD
><P
>not implemented</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ls</TT
>ls</CODE
></DT
><DD
><P
>not implemented</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>view</TT
>view</CODE
></DT
><DD
><P
>not implemented</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>help</TT
>help</CODE
></DT
><DD
><P
>not implemented</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>?</TT
>?</CODE
></DT
><DD
><P
>not implemented</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>exit</TT
>exit</CODE
></DT
><DD
><P
>Exits the program.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>set</TT
> <TT
>set</CODE
> <VAR
CLASS="REPLACEABLE"
><I
>keyword[<SPAN
CLASS="OPTIONAL"
>=value</SPAN
>]</I
></TT
>]</VAR
></DT
><DD
><P
@ -291,9 +281,9 @@ the lookups. Valid keywords are:
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>all</TT
>all</CODE
></DT
><DD
><P
@ -306,14 +296,12 @@ CLASS="COMMAND"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>class=</TT
><TT
>class=</CODE
><VAR
CLASS="REPLACEABLE"
><I
>value</I
></TT
>value</VAR
></DT
><DD
><P
@ -324,36 +312,36 @@ CLASS="REPLACEABLE"
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>IN</TT
>IN</CODE
></DT
><DD
><P
>the Internet class</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>CH</TT
>CH</CODE
></DT
><DD
><P
>the Chaos class</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>HS</TT
>HS</CODE
></DT
><DD
><P
>the Hesiod class</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ANY</TT
>ANY</CODE
></DT
><DD
><P
@ -369,17 +357,15 @@ CLASS="CONSTANT"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
><TT
><VAR
CLASS="REPLACEABLE"
><I
>[<SPAN
CLASS="OPTIONAL"
>no</SPAN
>]</I
></TT
>debug</TT
>]</VAR
>debug</CODE
></DT
><DD
><P
@ -395,17 +381,15 @@ CLASS="OPTIONAL"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
><TT
><VAR
CLASS="REPLACEABLE"
><I
>[<SPAN
CLASS="OPTIONAL"
>no</SPAN
>]</I
></TT
>d2</TT
>]</VAR
>d2</CODE
></DT
><DD
><P
@ -418,37 +402,31 @@ CLASS="OPTIONAL"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>domain=</TT
><TT
>domain=</CODE
><VAR
CLASS="REPLACEABLE"
><I
>name</I
></TT
>name</VAR
></DT
><DD
><P
> Sets the search list to <TT
> Sets the search list to <VAR
CLASS="REPLACEABLE"
><I
>name</I
></TT
>name</VAR
>.
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
><TT
><VAR
CLASS="REPLACEABLE"
><I
>[<SPAN
CLASS="OPTIONAL"
>no</SPAN
>]</I
></TT
>search</TT
>]</VAR
>search</CODE
></DT
><DD
><P
@ -462,22 +440,18 @@ CLASS="OPTIONAL"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>port=</TT
><TT
>port=</CODE
><VAR
CLASS="REPLACEABLE"
><I
>value</I
></TT
>value</VAR
></DT
><DD
><P
> Change the default TCP/UDP name server port to <TT
> Change the default TCP/UDP name server port to <VAR
CLASS="REPLACEABLE"
><I
>value</I
></TT
>value</VAR
>.
</P
><P
@ -485,28 +459,24 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>querytype=</TT
><TT
>querytype=</CODE
><VAR
CLASS="REPLACEABLE"
><I
>value</I
></TT
>value</VAR
></DT
><DD
><P
></P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>type=</TT
><TT
>type=</CODE
><VAR
CLASS="REPLACEABLE"
><I
>value</I
></TT
>value</VAR
></DT
><DD
><P
@ -517,17 +487,15 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
><TT
><VAR
CLASS="REPLACEABLE"
><I
>[<SPAN
CLASS="OPTIONAL"
>no</SPAN
>]</I
></TT
>recurse</TT
>]</VAR
>recurse</CODE
></DT
><DD
><P
@ -539,14 +507,12 @@ CLASS="OPTIONAL"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>retry=</TT
><TT
>retry=</CODE
><VAR
CLASS="REPLACEABLE"
><I
>number</I
></TT
>number</VAR
></DT
><DD
><P
@ -554,14 +520,12 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>timeout=</TT
><TT
>timeout=</CODE
><VAR
CLASS="REPLACEABLE"
><I
>number</I
></TT
>number</VAR
></DT
><DD
><P
@ -570,17 +534,15 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
><TT
><VAR
CLASS="REPLACEABLE"
><I
>[<SPAN
CLASS="OPTIONAL"
>no</SPAN
>]</I
></TT
>vc</TT
>]</VAR
>vc</CODE
></DT
><DD
><P

214
bin/dnssec/dnssec-keygen.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: dnssec-keygen.html,v 1.9.18.4 2004/06/11 02:49:00 marka Exp $ -->
<!-- $Id: dnssec-keygen.html,v 1.9.18.5 2004/08/22 23:53:26 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>dnssec-keygen</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>dnssec-keygen</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,94 +62,72 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>dnssec-keygen</B
> {-a <TT
> {-a <VAR
CLASS="REPLACEABLE"
><I
>algorithm</I
></TT
>} {-b <TT
>algorithm</VAR
>} {-b <VAR
CLASS="REPLACEABLE"
><I
>keysize</I
></TT
>} {-n <TT
>keysize</VAR
>} {-n <VAR
CLASS="REPLACEABLE"
><I
>nametype</I
></TT
>} [<TT
>nametype</VAR
>} [<VAR
CLASS="OPTION"
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>class</I
></TT
></TT
>] [<TT
>class</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-e</TT
>] [<TT
>-e</VAR
>] [<VAR
CLASS="OPTION"
>-f <TT
>-f <VAR
CLASS="REPLACEABLE"
><I
>flag</I
></TT
></TT
>] [<TT
>flag</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-g <TT
>-g <VAR
CLASS="REPLACEABLE"
><I
>generator</I
></TT
></TT
>] [<TT
>generator</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-h</TT
>] [<TT
>-h</VAR
>] [<VAR
CLASS="OPTION"
>-k</TT
>] [<TT
>-k</VAR
>] [<VAR
CLASS="OPTION"
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>protocol</I
></TT
></TT
>] [<TT
>protocol</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-r <TT
>-r <VAR
CLASS="REPLACEABLE"
><I
>randomdev</I
></TT
></TT
>] [<TT
>randomdev</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>strength</I
></TT
></TT
>] [<TT
>strength</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>type</I
></TT
></TT
>] [<TT
>type</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-v <TT
>-v <VAR
CLASS="REPLACEABLE"
><I
>level</I
></TT
></TT
>level</VAR
></VAR
>] {name}</P
></DIV
><DIV
@ -182,18 +160,16 @@ NAME="AEN57"
CLASS="VARIABLELIST"
><DL
><DT
>-a <TT
>-a <VAR
CLASS="REPLACEABLE"
><I
>algorithm</I
></TT
>algorithm</VAR
></DT
><DD
><P
> Selects the cryptographic algorithm. The value of
<TT
<VAR
CLASS="OPTION"
>algorithm</TT
>algorithm</VAR
> must be one of RSAMD5 (RSA) or RSASHA1,
DSA, DH (Diffie Hellman), or HMAC-MD5. These values
are case insensitive.
@ -207,11 +183,9 @@ CLASS="OPTION"
</P
></DD
><DT
>-b <TT
>-b <VAR
CLASS="REPLACEABLE"
><I
>keysize</I
></TT
>keysize</VAR
></DT
><DD
><P
@ -224,18 +198,16 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>nametype</I
></TT
>nametype</VAR
></DT
><DD
><P
> Specifies the owner type of the key. The value of
<TT
<VAR
CLASS="OPTION"
>nametype</TT
>nametype</VAR
> 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
@ -243,11 +215,9 @@ CLASS="OPTION"
</P
></DD
><DT
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>class</I
></TT
>class</VAR
></DT
><DD
><P
@ -263,11 +233,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-f <TT
>-f <VAR
CLASS="REPLACEABLE"
><I
>flag</I
></TT
>flag</VAR
></DT
><DD
><P
@ -276,11 +244,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-g <TT
>-g <VAR
CLASS="REPLACEABLE"
><I
>generator</I
></TT
>generator</VAR
></DT
><DD
><P
@ -309,11 +275,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>protocol</I
></TT
>protocol</VAR
></DT
><DD
><P
@ -324,11 +288,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-r <TT
>-r <VAR
CLASS="REPLACEABLE"
><I
>randomdev</I
></TT
>randomdev</VAR
></DT
><DD
><P
@ -352,11 +314,9 @@ CLASS="FILENAME"
</P
></DD
><DT
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>strength</I
></TT
>strength</VAR
></DT
><DD
><P
@ -366,17 +326,15 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>type</I
></TT
>type</VAR
></DT
><DD
><P
> Indicates the use of the key. <TT
> Indicates the use of the key. <VAR
CLASS="OPTION"
>type</TT
>type</VAR
> must be
one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default
is AUTHCONF. AUTH refers to the ability to authenticate
@ -384,11 +342,9 @@ CLASS="OPTION"
</P
></DD
><DT
>-v <TT
>-v <VAR
CLASS="REPLACEABLE"
><I
>level</I
></TT
>level</VAR
></DT
><DD
><P
@ -503,31 +459,25 @@ NAME="AEN163"
>EXAMPLE</H2
><P
> To generate a 768-bit DSA key for the domain
<TT
<KBD
CLASS="USERINPUT"
><B
>example.com</B
></TT
>example.com</KBD
>, the following command would be
issued:
</P
><P
> <TT
> <KBD
CLASS="USERINPUT"
><B
>dnssec-keygen -a DSA -b 768 -n ZONE example.com</B
></TT
>dnssec-keygen -a DSA -b 768 -n ZONE example.com</KBD
>
</P
><P
> The command would print a string of the form:
</P
><P
> <TT
> <KBD
CLASS="USERINPUT"
><B
>Kexample.com.+003+26160</B
></TT
>Kexample.com.+003+26160</KBD
>
</P
><P

270
bin/dnssec/dnssec-signzone.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: dnssec-signzone.html,v 1.8.18.4 2004/06/11 02:49:01 marka Exp $ -->
<!-- $Id: dnssec-signzone.html,v 1.8.18.5 2004/08/22 23:53:27 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>dnssec-signzone</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>dnssec-signzone</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,120 +62,96 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>dnssec-signzone</B
> [<TT
> [<VAR
CLASS="OPTION"
>-a</TT
>] [<TT
>-a</VAR
>] [<VAR
CLASS="OPTION"
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>class</I
></TT
></TT
>] [<TT
>class</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-d <TT
>-d <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
></TT
>] [<TT
>directory</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-e <TT
>-e <VAR
CLASS="REPLACEABLE"
><I
>end-time</I
></TT
></TT
>] [<TT
>end-time</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-f <TT
>-f <VAR
CLASS="REPLACEABLE"
><I
>output-file</I
></TT
></TT
>] [<TT
>output-file</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-g</TT
>] [<TT
>-g</VAR
>] [<VAR
CLASS="OPTION"
>-h</TT
>] [<TT
>-h</VAR
>] [<VAR
CLASS="OPTION"
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>key</I
></TT
></TT
>] [<TT
>key</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-l <TT
>-l <VAR
CLASS="REPLACEABLE"
><I
>domain</I
></TT
></TT
>] [<TT
>domain</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-i <TT
>-i <VAR
CLASS="REPLACEABLE"
><I
>interval</I
></TT
></TT
>] [<TT
>interval</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>nthreads</I
></TT
></TT
>] [<TT
>nthreads</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-o <TT
>-o <VAR
CLASS="REPLACEABLE"
><I
>origin</I
></TT
></TT
>] [<TT
>origin</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-p</TT
>] [<TT
>-p</VAR
>] [<VAR
CLASS="OPTION"
>-r <TT
>-r <VAR
CLASS="REPLACEABLE"
><I
>randomdev</I
></TT
></TT
>] [<TT
>randomdev</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>start-time</I
></TT
></TT
>] [<TT
>start-time</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-t</TT
>] [<TT
>-t</VAR
>] [<VAR
CLASS="OPTION"
>-v <TT
>-v <VAR
CLASS="REPLACEABLE"
><I
>level</I
></TT
></TT
>] [<TT
>level</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-z</TT
>-z</VAR
>] {zonefile} [key...]</P
></DIV
><DIV
@ -220,11 +196,9 @@ CLASS="VARIABLELIST"
</P
></DD
><DT
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>class</I
></TT
>class</VAR
></DT
><DD
><P
@ -232,11 +206,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>key</I
></TT
>key</VAR
></DT
><DD
><P
@ -245,11 +217,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-l <TT
>-l <VAR
CLASS="REPLACEABLE"
><I
>domain</I
></TT
>domain</VAR
></DT
><DD
><P
@ -258,11 +228,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-d <TT
>-d <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
></DT
><DD
><P
@ -270,9 +238,9 @@ CLASS="REPLACEABLE"
CLASS="FILENAME"
>keyset</TT
> files in
<TT
<VAR
CLASS="OPTION"
>directory</TT
>directory</VAR
> as the directory
</P
></DD
@ -285,11 +253,9 @@ CLASS="OPTION"
</P
></DD
><DT
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>start-time</I
></TT
>start-time</VAR
></DT
><DD
><P
@ -299,43 +265,39 @@ CLASS="REPLACEABLE"
in YYYYMMDDHHMMSS notation; 20000530144500 denotes
14:45:00 UTC on May 30th, 2000. A relative start time is
indicated by +N, which is N seconds from the current time.
If no <TT
If no <VAR
CLASS="OPTION"
>start-time</TT
>start-time</VAR
> is specified, the current
time minus 1 hour (to allow for clock skew) is used.
</P
></DD
><DT
>-e <TT
>-e <VAR
CLASS="REPLACEABLE"
><I
>end-time</I
></TT
>end-time</VAR
></DT
><DD
><P
> Specify the date and time when the generated RRSIG records
expire. As with <TT
expire. As with <VAR
CLASS="OPTION"
>start-time</TT
>start-time</VAR
>, an absolute
time is indicated in YYYYMMDDHHMMSS notation. A time relative
to the start time is indicated with +N, which is N seconds from
the start time. A time relative to the current time is
indicated with now+N. If no <TT
indicated with now+N. If no <VAR
CLASS="OPTION"
>end-time</TT
>end-time</VAR
> is
specified, 30 days from the start time is used as a default.
</P
></DD
><DT
>-f <TT
>-f <VAR
CLASS="REPLACEABLE"
><I
>output-file</I
></TT
>output-file</VAR
></DT
><DD
><P
@ -359,18 +321,16 @@ CLASS="COMMAND"
</P
></DD
><DT
>-i <TT
>-i <VAR
CLASS="REPLACEABLE"
><I
>interval</I
></TT
>interval</VAR
></DT
><DD
><P
> When a previously signed zone is passed as input, records
may be resigned. The <TT
may be resigned. The <VAR
CLASS="OPTION"
>interval</TT
>interval</VAR
> option
specifies the cycle interval as an offset from the current
time (in seconds). If a RRSIG record expires after the
@ -380,12 +340,12 @@ CLASS="OPTION"
><P
> The default cycle interval is one quarter of the difference
between the signature end and start times. So if neither
<TT
<VAR
CLASS="OPTION"
>end-time</TT
> or <TT
>end-time</VAR
> or <VAR
CLASS="OPTION"
>start-time</TT
>start-time</VAR
>
are specified, <B
CLASS="COMMAND"
@ -398,11 +358,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>ncpus</I
></TT
>ncpus</VAR
></DT
><DD
><P
@ -411,11 +369,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-o <TT
>-o <VAR
CLASS="REPLACEABLE"
><I
>origin</I
></TT
>origin</VAR
></DT
><DD
><P
@ -434,11 +390,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-r <TT
>-r <VAR
CLASS="REPLACEABLE"
><I
>randomdev</I
></TT
>randomdev</VAR
></DT
><DD
><P
@ -469,11 +423,9 @@ CLASS="FILENAME"
</P
></DD
><DT
>-v <TT
>-v <VAR
CLASS="REPLACEABLE"
><I
>level</I
></TT
>level</VAR
></DT
><DD
><P
@ -515,11 +467,9 @@ NAME="AEN181"
><H2
>EXAMPLE</H2
><P
> The following command signs the <TT
> The following command signs the <KBD
CLASS="USERINPUT"
><B
>example.com</B
></TT
>example.com</KBD
>
zone with the DSA key generated in the <B
CLASS="COMMAND"
@ -531,20 +481,16 @@ CLASS="FILENAME"
>keyset</TT
> files associated with child zones,
they must be in the current directory.
<TT
<KBD
CLASS="USERINPUT"
><B
>example.com</B
></TT
>example.com</KBD
>, the following command would be
issued:
</P
><P
> <TT
> <KBD
CLASS="USERINPUT"
><B
>dnssec-signzone -o example.com db.example.com Kexample.com.+003+26160</B
></TT
>dnssec-signzone -o example.com db.example.com Kexample.com.+003+26160</KBD
>
</P
><P

212
bin/named/lwresd.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwresd.html,v 1.5.18.3 2004/06/03 04:17:54 marka Exp $ -->
<!-- $Id: lwresd.html,v 1.5.18.4 2004/08/22 23:53:27 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwresd</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>lwresd</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,82 +62,66 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>lwresd</B
> [<TT
> [<VAR
CLASS="OPTION"
>-C <TT
>-C <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
></TT
>] [<TT
>config-file</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-d <TT
>-d <VAR
CLASS="REPLACEABLE"
><I
>debug-level</I
></TT
></TT
>] [<TT
>debug-level</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-f</TT
>] [<TT
>-f</VAR
>] [<VAR
CLASS="OPTION"
>-g</TT
>] [<TT
>-g</VAR
>] [<VAR
CLASS="OPTION"
>-i <TT
>-i <VAR
CLASS="REPLACEABLE"
><I
>pid-file</I
></TT
></TT
>] [<TT
>pid-file</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>#cpus</I
></TT
></TT
>] [<TT
>#cpus</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-P <TT
>-P <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
></TT
>] [<TT
>port</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
></TT
>] [<TT
>port</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-s</TT
>] [<TT
>-s</VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
></TT
>] [<TT
>directory</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-u <TT
>-u <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
></TT
>] [<TT
>user</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-v</TT
>-v</VAR
>]</P
></DIV
><DIV
@ -186,18 +170,18 @@ CLASS="COMMAND"
CLASS="FILENAME"
>/etc/resolv.conf</TT
> contains any
<TT
<VAR
CLASS="OPTION"
>nameserver</TT
>nameserver</VAR
> entries, <B
CLASS="COMMAND"
>lwresd</B
>
sends recursive DNS queries to those servers. This is similar
to the use of forwarders in a caching name server. If no
<TT
<VAR
CLASS="OPTION"
>nameserver</TT
>nameserver</VAR
> entries are present, or if
forwarding fails, <B
CLASS="COMMAND"
@ -220,19 +204,15 @@ NAME="AEN63"
CLASS="VARIABLELIST"
><DL
><DT
>-C <TT
>-C <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
></DT
><DD
><P
> Use <TT
> Use <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
> as the
configuration file instead of the default,
<TT
@ -242,19 +222,15 @@ CLASS="FILENAME"
</P
></DD
><DT
>-d <TT
>-d <VAR
CLASS="REPLACEABLE"
><I
>debug-level</I
></TT
>debug-level</VAR
></DT
><DD
><P
> Set the daemon's debug level to <TT
> Set the daemon's debug level to <VAR
CLASS="REPLACEABLE"
><I
>debug-level</I
></TT
>debug-level</VAR
>.
Debugging traces from <B
CLASS="COMMAND"
@ -282,19 +258,15 @@ CLASS="FILENAME"
</P
></DD
><DT
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>#cpus</I
></TT
>#cpus</VAR
></DT
><DD
><P
> Create <TT
> Create <VAR
CLASS="REPLACEABLE"
><I
>#cpus</I
></TT
>#cpus</VAR
> worker threads
to take advantage of multiple CPUs. If not specified,
<B
@ -307,38 +279,30 @@ CLASS="COMMAND"
</P
></DD
><DT
>-P <TT
>-P <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
></DT
><DD
><P
> Listen for lightweight resolver queries on port
<TT
<VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
>. If
not specified, the default is port 921.
</P
></DD
><DT
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
></DT
><DD
><P
> Send DNS lookups to port <TT
> Send DNS lookups to port <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
>. If not
specified, the default is port 53. This provides a
way of testing the lightweight resolver daemon with a
@ -370,22 +334,18 @@ CLASS="NOTE"
></DIV
></DD
><DT
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
></DT
><DD
><P
> <TT
> <CODE
CLASS="FUNCTION"
>chroot()</TT
> to <TT
>chroot()</CODE
> to <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
> after
processing the command line arguments, but before
reading the configuration file.
@ -410,14 +370,14 @@ ALIGN="CENTER"
ALIGN="LEFT"
><P
> This option should be used in conjunction with the
<TT
<VAR
CLASS="OPTION"
>-u</TT
>-u</VAR
> option, as chrooting a process
running as root doesn't enhance security on most
systems; the way <TT
systems; the way <CODE
CLASS="FUNCTION"
>chroot()</TT
>chroot()</CODE
> is
defined allows a process with root privileges to
escape a chroot jail.
@ -428,22 +388,18 @@ CLASS="FUNCTION"
></DIV
></DD
><DT
>-u <TT
>-u <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
>user</VAR
></DT
><DD
><P
> <TT
> <CODE
CLASS="FUNCTION"
>setuid()</TT
> to <TT
>setuid()</CODE
> to <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
>user</VAR
> after completing
privileged operations, such as creating sockets that
listen on privileged ports.

2168
bin/named/named.conf.html
View file

File diff suppressed because it is too large Load diff

240
bin/named/named.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: named.html,v 1.6.18.3 2004/06/03 04:17:54 marka Exp $ -->
<!-- $Id: named.html,v 1.6.18.4 2004/08/22 23:53:28 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>named</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>named</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,80 +62,66 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>named</B
> [<TT
> [<VAR
CLASS="OPTION"
>-4</TT
>] [<TT
>-4</VAR
>] [<VAR
CLASS="OPTION"
>-6</TT
>] [<TT
>-6</VAR
>] [<VAR
CLASS="OPTION"
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
></TT
>] [<TT
>config-file</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-d <TT
>-d <VAR
CLASS="REPLACEABLE"
><I
>debug-level</I
></TT
></TT
>] [<TT
>debug-level</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-f</TT
>] [<TT
>-f</VAR
>] [<VAR
CLASS="OPTION"
>-g</TT
>] [<TT
>-g</VAR
>] [<VAR
CLASS="OPTION"
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>#cpus</I
></TT
></TT
>] [<TT
>#cpus</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
></TT
>] [<TT
>port</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-s</TT
>] [<TT
>-s</VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
></TT
>] [<TT
>directory</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-u <TT
>-u <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
></TT
>] [<TT
>user</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-v</TT
>] [<TT
>-v</VAR
>] [<VAR
CLASS="OPTION"
>-x <TT
>-x <VAR
CLASS="REPLACEABLE"
><I
>cache-file</I
></TT
></TT
>cache-file</VAR
></VAR
>]</P
></DIV
><DIV
@ -183,12 +169,12 @@ CLASS="VARIABLELIST"
><DD
><P
> Use IPv4 only even if the host machine is capable of IPv6.
<TT
<VAR
CLASS="OPTION"
>-4</TT
> and <TT
>-4</VAR
> and <VAR
CLASS="OPTION"
>-6</TT
>-6</VAR
> are mutually
exclusive.
</P
@ -198,30 +184,26 @@ CLASS="OPTION"
><DD
><P
> Use IPv6 only even if the host machine is capable of IPv4.
<TT
<VAR
CLASS="OPTION"
>-4</TT
> and <TT
>-4</VAR
> and <VAR
CLASS="OPTION"
>-6</TT
>-6</VAR
> are mutually
exclusive.
</P
></DD
><DT
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
></DT
><DD
><P
> Use <TT
> Use <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
> as the
configuration file instead of the default,
<TT
@ -231,33 +213,27 @@ CLASS="FILENAME"
ensure that reloading the configuration file continues
to work after the server has changed its working
directory due to to a possible
<TT
<VAR
CLASS="OPTION"
>directory</TT
>directory</VAR
> option in the configuration
file, <TT
file, <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
> should be
an absolute pathname.
</P
></DD
><DT
>-d <TT
>-d <VAR
CLASS="REPLACEABLE"
><I
>debug-level</I
></TT
>debug-level</VAR
></DT
><DD
><P
> Set the daemon's debug level to <TT
> Set the daemon's debug level to <VAR
CLASS="REPLACEABLE"
><I
>debug-level</I
></TT
>debug-level</VAR
>.
Debugging traces from <B
CLASS="COMMAND"
@ -285,19 +261,15 @@ CLASS="FILENAME"
</P
></DD
><DT
>-n <TT
>-n <VAR
CLASS="REPLACEABLE"
><I
>#cpus</I
></TT
>#cpus</VAR
></DT
><DD
><P
> Create <TT
> Create <VAR
CLASS="REPLACEABLE"
><I
>#cpus</I
></TT
>#cpus</VAR
> worker threads
to take advantage of multiple CPUs. If not specified,
<B
@ -310,19 +282,15 @@ CLASS="COMMAND"
</P
></DD
><DT
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
></DT
><DD
><P
> Listen for queries on port <TT
> Listen for queries on port <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
>. If not
specified, the default is port 53.
</P
@ -350,22 +318,18 @@ CLASS="NOTE"
></DIV
></DD
><DT
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
></DT
><DD
><P
> <TT
> <CODE
CLASS="FUNCTION"
>chroot()</TT
> to <TT
>chroot()</CODE
> to <VAR
CLASS="REPLACEABLE"
><I
>directory</I
></TT
>directory</VAR
> after
processing the command line arguments, but before
reading the configuration file.
@ -390,14 +354,14 @@ ALIGN="CENTER"
ALIGN="LEFT"
><P
> This option should be used in conjunction with the
<TT
<VAR
CLASS="OPTION"
>-u</TT
>-u</VAR
> option, as chrooting a process
running as root doesn't enhance security on most
systems; the way <TT
systems; the way <CODE
CLASS="FUNCTION"
>chroot()</TT
>chroot()</CODE
> is
defined allows a process with root privileges to
escape a chroot jail.
@ -408,22 +372,18 @@ CLASS="FUNCTION"
></DIV
></DD
><DT
>-u <TT
>-u <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
>user</VAR
></DT
><DD
><P
> <TT
> <CODE
CLASS="FUNCTION"
>setuid()</TT
> to <TT
>setuid()</CODE
> to <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
>user</VAR
> after completing
privileged operations, such as creating sockets that
listen on privileged ports.
@ -440,14 +400,14 @@ CLASS="COMMAND"
>named</B
> uses the kernel's
capability mechanism to drop all root privileges
except the ability to <TT
except the ability to <CODE
CLASS="FUNCTION"
>bind()</TT
>bind()</CODE
> to a
privileged port and set process resource limits.
Unfortunately, this means that the <TT
Unfortunately, this means that the <VAR
CLASS="OPTION"
>-u</TT
>-u</VAR
>
option only works when <B
CLASS="COMMAND"
@ -455,9 +415,9 @@ CLASS="COMMAND"
> 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 <TT
to be retained after <CODE
CLASS="FUNCTION"
>setuid()</TT
>setuid()</CODE
>.
</P
></BLOCKQUOTE
@ -471,19 +431,15 @@ CLASS="FUNCTION"
</P
></DD
><DT
>-x <TT
>-x <VAR
CLASS="REPLACEABLE"
><I
>cache-file</I
></TT
>cache-file</VAR
></DT
><DD
><P
> Load data from <TT
> Load data from <VAR
CLASS="REPLACEABLE"
><I
>cache-file</I
></TT
>cache-file</VAR
> into the
cache of the default view.
</P

384
bin/nsupdate/nsupdate.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: nsupdate.html,v 1.14.18.2 2004/04/07 00:58:12 marka Exp $ -->
<!-- $Id: nsupdate.html,v 1.14.18.3 2004/08/22 23:53:28 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>nsupdate</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>nsupdate</A
></H1
></A
>nsupdate</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -56,52 +56,42 @@ NAME="AEN11"
><B
CLASS="COMMAND"
>nsupdate</B
> [<TT
> [<VAR
CLASS="OPTION"
>-d</TT
>] [<TT
>-d</VAR
>] [<VAR
CLASS="OPTION"
>-y <TT
>-y <VAR
CLASS="REPLACEABLE"
><I
>keyname:secret</I
></TT
></TT
> | <TT
>keyname:secret</VAR
></VAR
> | <VAR
CLASS="OPTION"
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>keyfile</I
></TT
></TT
>] [<TT
>keyfile</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>timeout</I
></TT
></TT
>] [<TT
>timeout</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-u <TT
>-u <VAR
CLASS="REPLACEABLE"
><I
>udptimeout</I
></TT
></TT
>] [<TT
>udptimeout</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-r <TT
>-r <VAR
CLASS="REPLACEABLE"
><I
>udpretries</I
></TT
></TT
>] [<TT
>udpretries</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-v</TT
>-v</VAR
>] [filename]</P
></DIV
><DIV
@ -142,9 +132,9 @@ Requests are sent to the zone's master server.
This is identified by the MNAME field of the zone's SOA record.</P
><P
>The
<TT
<VAR
CLASS="OPTION"
>-d</TT
>-d</VAR
>
option makes
<B
@ -204,22 +194,22 @@ CLASS="COMMAND"
>nsupdate</B
>
uses the
<TT
<VAR
CLASS="OPTION"
>-y</TT
>-y</VAR
>
or
<TT
<VAR
CLASS="OPTION"
>-k</TT
>-k</VAR
>
option (with an HMAC-MD5 key) to provide the shared secret needed to generate
a TSIG record for authenticating Dynamic DNS update requests.
These options are mutually exclusive.
With the
<TT
<VAR
CLASS="OPTION"
>-k</TT
>-k</VAR
>
option,
<B
@ -227,11 +217,9 @@ CLASS="COMMAND"
>nsupdate</B
>
reads the shared secret from the file
<TT
<VAR
CLASS="PARAMETER"
><I
>keyfile</I
></TT
>keyfile</VAR
>,
whose name is of the form
<TT
@ -245,36 +233,30 @@ CLASS="FILENAME"
>K{name}.+157.+{random}.key</TT
>
must also be present. When the
<TT
<VAR
CLASS="OPTION"
>-y</TT
>-y</VAR
>
option is used, a signature is generated from
<TT
<VAR
CLASS="PARAMETER"
><I
>keyname:secret.</I
></TT
>keyname:secret.</VAR
>
<TT
<VAR
CLASS="PARAMETER"
><I
>keyname</I
></TT
>keyname</VAR
>
is the name of the key,
and
<TT
<VAR
CLASS="PARAMETER"
><I
>secret</I
></TT
>secret</VAR
>
is the base64 encoded shared secret.
Use of the
<TT
<VAR
CLASS="OPTION"
>-y</TT
>-y</VAR
>
option is discouraged because the shared secret is supplied as a command
line argument in clear text.
@ -288,9 +270,9 @@ CLASS="REFENTRYTITLE"
>
or in a history file maintained by the user's shell.</P
><P
>The <TT
>The <VAR
CLASS="OPTION"
>-k</TT
>-k</VAR
> 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
@ -303,9 +285,9 @@ CLASS="COMMAND"
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.
The
<TT
<VAR
CLASS="OPTION"
>-v</TT
>-v</VAR
>
option makes
<B
@ -315,23 +297,23 @@ CLASS="COMMAND"
use a TCP connection.
This may be preferable when a batch of update requests is made.</P
><P
>The <TT
>The <VAR
CLASS="OPTION"
>-t</TT
>-t</VAR
> option sets the maximum time a update request can
take before it is aborted. The default is 300 seconds. Zero can be used
to disable the timeout.</P
><P
>The <TT
>The <VAR
CLASS="OPTION"
>-u</TT
>-u</VAR
> option sets 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
><P
>The <TT
>The <VAR
CLASS="OPTION"
>-r</TT
>-r</VAR
> option sets the number of UDP retries. The default is
3. If zero only one update request will be made.</P
></DIV
@ -348,11 +330,9 @@ CLASS="COMMAND"
>nsupdate</B
>
reads input from
<TT
<VAR
CLASS="PARAMETER"
><I
>filename</I
></TT
>filename</VAR
>
or standard input.
Each command is supplied on exactly one line of input.
@ -391,11 +371,9 @@ CLASS="COMMAND"
><DD
><P
>Sends all dynamic update requests to the name server
<TT
<VAR
CLASS="PARAMETER"
><I
>servername</I
></TT
>servername</VAR
>.
When no server statement is provided,
<B
@ -405,18 +383,14 @@ CLASS="COMMAND"
will send updates to the master server of the correct zone.
The MNAME field of that zone's SOA record will identify the master
server for that zone.
<TT
<VAR
CLASS="PARAMETER"
><I
>port</I
></TT
>port</VAR
>
is the port number on
<TT
<VAR
CLASS="PARAMETER"
><I
>servername</I
></TT
>servername</VAR
>
where the dynamic update requests get sent.
If no port number is specified, the default DNS port number of 53 is
@ -432,11 +406,9 @@ CLASS="COMMAND"
><DD
><P
>Sends all dynamic update requests using the local
<TT
<VAR
CLASS="PARAMETER"
><I
>address</I
></TT
>address</VAR
>.
When no local statement is provided,
@ -445,11 +417,9 @@ CLASS="COMMAND"
>nsupdate</B
>
will send updates using an address and port chosen by the system.
<TT
<VAR
CLASS="PARAMETER"
><I
>port</I
></TT
>port</VAR
>
can additionally be used to make requests come from a specific port.
If no port number is specified, the system will assign one.&#13;</P
@ -464,18 +434,14 @@ CLASS="COMMAND"
><DD
><P
>Specifies that all updates are to be made to the zone
<TT
<VAR
CLASS="PARAMETER"
><I
>zonename</I
></TT
>zonename</VAR
>.
If no
<TT
<VAR
CLASS="PARAMETER"
><I
>zone</I
></TT
>zone</VAR
>
statement is provided,
<B
@ -494,17 +460,13 @@ CLASS="COMMAND"
><DD
><P
>Specify the default class.
If no <TT
If no <VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
> is specified the default class is
<TT
<VAR
CLASS="PARAMETER"
><I
>IN</I
></TT
>IN</VAR
>.</P
></DD
><DT
@ -517,28 +479,24 @@ CLASS="COMMAND"
><DD
><P
>Specifies that all updates are to be TSIG signed using the
<TT
<VAR
CLASS="PARAMETER"
><I
>keyname</I
></TT
> <TT
>keyname</VAR
> <VAR
CLASS="PARAMETER"
><I
>keysecret</I
></TT
>keysecret</VAR
> pair.
The <B
CLASS="COMMAND"
>key</B
> command
overrides any key specified on the command line via
<TT
<VAR
CLASS="OPTION"
>-y</TT
> or <TT
>-y</VAR
> or <VAR
CLASS="OPTION"
>-k</TT
>-k</VAR
>.</P
></DD
><DT
@ -551,11 +509,9 @@ CLASS="COMMAND"
><DD
><P
>Requires that no resource record of any type exists with name
<TT
<VAR
CLASS="PARAMETER"
><I
>domain-name</I
></TT
>domain-name</VAR
>.</P
></DD
><DT
@ -568,11 +524,9 @@ CLASS="COMMAND"
><DD
><P
>Requires that
<TT
<VAR
CLASS="PARAMETER"
><I
>domain-name</I
></TT
>domain-name</VAR
>
exists (has as at least one resource record, of any type).</P
></DD
@ -586,31 +540,23 @@ CLASS="COMMAND"
><DD
><P
>Requires that no resource record exists of the specified
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>domain-name</I
></TT
>domain-name</VAR
>.
If
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>
is omitted, IN (internet) is assumed.</P
></DD
@ -624,32 +570,24 @@ CLASS="COMMAND"
><DD
><P
>This requires that a resource record of the specified
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>domain-name</I
></TT
>domain-name</VAR
>
must exist.
If
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>
is omitted, IN (internet) is assumed.</P
></DD
@ -663,61 +601,45 @@ CLASS="COMMAND"
><DD
><P
>The
<TT
<VAR
CLASS="PARAMETER"
><I
>data</I
></TT
>data</VAR
>
from each set of prerequisites of this form
sharing a common
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>,
and
<TT
<VAR
CLASS="PARAMETER"
><I
>domain-name</I
></TT
>domain-name</VAR
>
are combined to form a set of RRs. This set of RRs must
exactly match the set of RRs existing in the zone at the
given
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>,
and
<TT
<VAR
CLASS="PARAMETER"
><I
>domain-name</I
></TT
>domain-name</VAR
>.
The
<TT
<VAR
CLASS="PARAMETER"
><I
>data</I
></TT
>data</VAR
>
are written in the standard text representation of the resource record's
RDATA.</P
@ -732,40 +654,30 @@ CLASS="COMMAND"
><DD
><P
>Deletes any resource records named
<TT
<VAR
CLASS="PARAMETER"
><I
>domain-name</I
></TT
>domain-name</VAR
>.
If
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>data</I
></TT
>data</VAR
>
is provided, only matching resource records will be removed.
The internet class is assumed if
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>
is not supplied. The
<TT
<VAR
CLASS="PARAMETER"
><I
>ttl</I
></TT
>ttl</VAR
>
is ignored, and is only allowed for compatibility.</P
></DD
@ -779,24 +691,18 @@ CLASS="COMMAND"
><DD
><P
>Adds a new resource record with the specified
<TT
<VAR
CLASS="PARAMETER"
><I
>ttl</I
></TT
>ttl</VAR
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>data</I
></TT
>data</VAR
>.</P
></DD
><DT
@ -923,18 +829,18 @@ NAME="AEN268"
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>/etc/resolv.conf</TT
>/etc/resolv.conf</CODE
></DT
><DD
><P
>used to identify default name server</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>K{name}.+157.+{random}.key</TT
>K{name}.+157.+{random}.key</CODE
></DT
><DD
><P
@ -948,9 +854,9 @@ CLASS="REFENTRYTITLE"
>.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>K{name}.+157.+{random}.private</TT
>K{name}.+157.+{random}.private</CODE
></DT
><DD
><P

168
bin/rndc/rndc-confgen.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: rndc-confgen.html,v 1.8.18.3 2004/06/03 04:17:55 marka Exp $ -->
<!-- $Id: rndc-confgen.html,v 1.8.18.4 2004/08/22 23:53:29 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>rndc-confgen</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>rndc-confgen</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,76 +62,60 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>rndc-confgen</B
> [<TT
> [<VAR
CLASS="OPTION"
>-a</TT
>] [<TT
>-a</VAR
>] [<VAR
CLASS="OPTION"
>-b <TT
>-b <VAR
CLASS="REPLACEABLE"
><I
>keysize</I
></TT
></TT
>] [<TT
>keysize</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>keyfile</I
></TT
></TT
>] [<TT
>keyfile</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-h</TT
>] [<TT
>-h</VAR
>] [<VAR
CLASS="OPTION"
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>keyname</I
></TT
></TT
>] [<TT
>keyname</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
></TT
>] [<TT
>port</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-r <TT
>-r <VAR
CLASS="REPLACEABLE"
><I
>randomfile</I
></TT
></TT
>] [<TT
>randomfile</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>address</I
></TT
></TT
>] [<TT
>address</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>chrootdir</I
></TT
></TT
>] [<TT
>chrootdir</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-u <TT
>-u <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
></TT
>user</VAR
></VAR
>]</P
></DIV
><DIV
@ -213,13 +197,13 @@ CLASS="FILENAME"
CLASS="FILENAME"
>/etc</TT
> (or whatever
<TT
<VAR
CLASS="VARNAME"
>sysconfdir</TT
>sysconfdir</VAR
>
was specified as when <SPAN
was specified as when <ACRONYM
CLASS="ACRONYM"
>BIND</SPAN
>BIND</ACRONYM
> was built)
that is read by both <B
CLASS="COMMAND"
@ -290,11 +274,9 @@ CLASS="FILENAME"
</P
></DD
><DT
>-b <TT
>-b <VAR
CLASS="REPLACEABLE"
><I
>keysize</I
></TT
>keysize</VAR
></DT
><DD
><P
@ -303,11 +285,9 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>keyfile</I
></TT
>keyfile</VAR
></DT
><DD
><P
@ -333,28 +313,24 @@ CLASS="COMMAND"
</P
></DD
><DT
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>keyname</I
></TT
>keyname</VAR
></DT
><DD
><P
> Specifies the key name of the rndc authentication key.
This must be a valid domain name.
The default is <TT
The default is <CODE
CLASS="CONSTANT"
>rndc-key</TT
>rndc-key</CODE
>.
</P
></DD
><DT
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
></DT
><DD
><P
@ -370,11 +346,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-r <TT
>-r <VAR
CLASS="REPLACEABLE"
><I
>randomfile</I
></TT
>randomfile</VAR
></DT
><DD
><P
@ -399,11 +373,9 @@ CLASS="FILENAME"
</P
></DD
><DT
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>address</I
></TT
>address</VAR
></DT
><DD
><P
@ -420,11 +392,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-t <TT
>-t <VAR
CLASS="REPLACEABLE"
><I
>chrootdir</I
></TT
>chrootdir</VAR
></DT
><DD
><P
@ -448,11 +418,9 @@ CLASS="COMMAND"
</P
></DD
><DT
>-u <TT
>-u <VAR
CLASS="REPLACEABLE"
><I
>user</I
></TT
>user</VAR
></DT
><DD
><P
@ -489,11 +457,9 @@ CLASS="COMMAND"
no manual configuration, run
</P
><P
> <TT
> <KBD
CLASS="USERINPUT"
><B
>rndc-confgen -a</B
></TT
>rndc-confgen -a</KBD
>
</P
><P
@ -515,11 +481,9 @@ CLASS="FILENAME"
run
</P
><P
> <TT
> <KBD
CLASS="USERINPUT"
><B
>rndc-confgen</B
></TT
>rndc-confgen</KBD
>
</P
></DIV

120
bin/rndc/rndc.conf.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: rndc.conf.html,v 1.6.18.5 2004/07/23 06:08:28 marka Exp $ -->
<!-- $Id: rndc.conf.html,v 1.6.18.6 2004/08/22 23:53:29 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>rndc.conf</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><TT
CLASS="FILENAME"
>rndc.conf</TT
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -111,114 +111,114 @@ CLASS="FILENAME"
and a key statement.
</P
><P
> The <TT
> The <VAR
CLASS="OPTION"
>options</TT
>options</VAR
> statement contains five clauses.
The <TT
The <VAR
CLASS="OPTION"
>default-server</TT
>default-server</VAR
> 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
<B
CLASS="COMMAND"
>rndc</B
>. The <TT
>. The <VAR
CLASS="OPTION"
>default-key</TT
>default-key</VAR
>
clause is followed by the name of a key which is identified by
a <TT
a <VAR
CLASS="OPTION"
>key</TT
>key</VAR
> statement. If no
<TT
<VAR
CLASS="OPTION"
>keyid</TT
>keyid</VAR
> is provided on the rndc command line,
and no <TT
and no <VAR
CLASS="OPTION"
>key</TT
>key</VAR
> clause is found in a matching
<TT
<VAR
CLASS="OPTION"
>server</TT
>server</VAR
> statement, this default key will be
used to authenticate the server's commands and responses. The
<TT
<VAR
CLASS="OPTION"
>default-port</TT
>default-port</VAR
> clause is followed by the port
to connect to on the remote name server. If no
<TT
<VAR
CLASS="OPTION"
>port</TT
>port</VAR
> option is provided on the rndc command
line, and no <TT
line, and no <VAR
CLASS="OPTION"
>port</TT
>port</VAR
> clause is found in a
matching <TT
matching <VAR
CLASS="OPTION"
>server</TT
>server</VAR
> statement, this default port
will be used to connect.
The <TT
The <VAR
CLASS="OPTION"
>default-source-address</TT
>default-source-address</VAR
> and
<TT
<VAR
CLASS="OPTION"
>default-source-address-v6</TT
>default-source-address-v6</VAR
> clauses which
can be used to set the IPv4 and IPv6 source addresses
respectively.
</P
><P
> After the <TT
> After the <VAR
CLASS="OPTION"
>server</TT
>server</VAR
> keyword, the server
statement includes a string which is the hostname or address
for a name server. The statement has three possible clauses:
<TT
<VAR
CLASS="OPTION"
>key</TT
>, <TT
>key</VAR
>, <VAR
CLASS="OPTION"
>port</TT
>port</VAR
> and
<TT
<VAR
CLASS="OPTION"
>addresses</TT
>addresses</VAR
>. The key name must match the
name of a key statement in the file. The port number
specifies the port to connect to. If an <TT
specifies the port to connect to. If an <VAR
CLASS="OPTION"
>addresses</TT
>addresses</VAR
>
clause is supplied these addresses will be used instead of
the server name. Each address can take a optional port.
If an <TT
If an <VAR
CLASS="OPTION"
>source-address</TT
> or <TT
>source-address</VAR
> or <VAR
CLASS="OPTION"
>source-address-v6</TT
>source-address-v6</VAR
>
of supplied then these will be used to specify the IPv4 and IPv6
source addresses respectively.
</P
><P
> The <TT
> The <VAR
CLASS="OPTION"
>key</TT
>key</VAR
> statement begins with an identifying
string, the name of the key. The statement has two clauses.
<TT
<VAR
CLASS="OPTION"
>algorithm</TT
>algorithm</VAR
> identifies the encryption algorithm
for <B
CLASS="COMMAND"
@ -313,11 +313,9 @@ CLASS="COMMAND"
>:
</P
><P
> <TT
> <KBD
CLASS="USERINPUT"
><B
>rndc-confgen</B
></TT
>rndc-confgen</KBD
>
</P
><P
@ -326,13 +324,13 @@ CLASS="FILENAME"
>rndc.conf</TT
> file, including the
randomly generated key, will be written to the standard
output. Commented out <TT
output. Commented out <VAR
CLASS="OPTION"
>key</TT
>key</VAR
> and
<TT
<VAR
CLASS="OPTION"
>controls</TT
>controls</VAR
> statements for
<TT
CLASS="FILENAME"
@ -346,11 +344,9 @@ CLASS="COMMAND"
>:
</P
><P
> <TT
> <KBD
CLASS="USERINPUT"
><B
>echo "known plaintext for a secret" | mmencode</B
></TT
>echo "known plaintext for a secret" | mmencode</KBD
>
</P
></DIV
@ -371,9 +367,9 @@ CLASS="FILENAME"
CLASS="FILENAME"
>named.conf</TT
>.
See the sections on the <TT
See the sections on the <VAR
CLASS="OPTION"
>controls</TT
>controls</VAR
> statement in the
BIND 9 Administrator Reference Manual for details.
</P

166
bin/rndc/rndc.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: rndc.html,v 1.8.18.4 2004/07/23 06:08:28 marka Exp $ -->
<!-- $Id: rndc.html,v 1.8.18.5 2004/08/22 23:53:30 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>rndc</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,10 +35,10 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
><SPAN
CLASS="APPLICATION"
>rndc</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
@ -62,57 +62,45 @@ NAME="AEN13"
><B
CLASS="COMMAND"
>rndc</B
> [<TT
> [<VAR
CLASS="OPTION"
>-b <TT
>-b <VAR
CLASS="REPLACEABLE"
><I
>source-address</I
></TT
></TT
>] [<TT
>source-address</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
></TT
>] [<TT
>config-file</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>key-file</I
></TT
></TT
>] [<TT
>key-file</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>server</I
></TT
></TT
>] [<TT
>server</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
></TT
>] [<TT
>port</VAR
></VAR
>] [<VAR
CLASS="OPTION"
>-V</TT
>] [<TT
>-V</VAR
>] [<VAR
CLASS="OPTION"
>-y <TT
>-y <VAR
CLASS="REPLACEABLE"
><I
>key_id</I
></TT
></TT
>key_id</VAR
></VAR
>] {command}</P
></DIV
><DIV
@ -183,19 +171,15 @@ NAME="AEN49"
CLASS="VARIABLELIST"
><DL
><DT
>-b <TT
>-b <VAR
CLASS="REPLACEABLE"
><I
>source-address</I
></TT
>source-address</VAR
></DT
><DD
><P
> Use <TT
> Use <VAR
CLASS="REPLACEABLE"
><I
>source-address</I
></TT
>source-address</VAR
>
as the source address for the connection to the server.
Multiple instances are permitted to allow setting of both
@ -203,19 +187,15 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-c <TT
>-c <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
></DT
><DD
><P
> Use <TT
> Use <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
>
as the configuration file instead of the default,
<TT
@ -225,19 +205,15 @@ CLASS="FILENAME"
</P
></DD
><DT
>-k <TT
>-k <VAR
CLASS="REPLACEABLE"
><I
>key-file</I
></TT
>key-file</VAR
></DT
><DD
><P
> Use <TT
> Use <VAR
CLASS="REPLACEABLE"
><I
>key-file</I
></TT
>key-file</VAR
>
as the key file instead of the default,
<TT
@ -248,29 +224,23 @@ CLASS="FILENAME"
CLASS="FILENAME"
>/etc/rndc.key</TT
> will be used to authenticate
commands sent to the server if the <TT
commands sent to the server if the <VAR
CLASS="REPLACEABLE"
><I
>config-file</I
></TT
>config-file</VAR
>
does not exist.
</P
></DD
><DT
>-s <TT
>-s <VAR
CLASS="REPLACEABLE"
><I
>server</I
></TT
>server</VAR
></DT
><DD
><P
> <TT
> <VAR
CLASS="REPLACEABLE"
><I
>server</I
></TT
>server</VAR
> is
the name or address of the server which matches a
server statement in the configuration file for
@ -284,20 +254,16 @@ CLASS="COMMAND"
</P
></DD
><DT
>-p <TT
>-p <VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
></DT
><DD
><P
> Send commands to TCP port
<TT
<VAR
CLASS="REPLACEABLE"
><I
>port</I
></TT
>port</VAR
> instead
of BIND 9's default control channel port, 953.
</P
@ -310,34 +276,26 @@ CLASS="REPLACEABLE"
</P
></DD
><DT
>-y <TT
>-y <VAR
CLASS="REPLACEABLE"
><I
>keyid</I
></TT
>keyid</VAR
></DT
><DD
><P
> Use the key <TT
> Use the key <VAR
CLASS="REPLACEABLE"
><I
>keyid</I
></TT
>keyid</VAR
>
from the configuration file.
<TT
<VAR
CLASS="REPLACEABLE"
><I
>keyid</I
></TT
>keyid</VAR
> must be
known by named with the same algorithm and secret string
in order for control message validation to succeed.
If no <TT
If no <VAR
CLASS="REPLACEABLE"
><I
>keyid</I
></TT
>keyid</VAR
>
is specified, <B
CLASS="COMMAND"
@ -385,9 +343,9 @@ CLASS="COMMAND"
</P
><P
> There is currently no way to provide the shared secret for a
<TT
<VAR
CLASS="OPTION"
>key_id</TT
>key_id</VAR
> without using the configuration file.
</P
><P

234
doc/arm/Bv9ARM.ch01.html
View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Introduction </TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="BIND 9 Administrator Reference Manual"
HREF="Bv9ARM.html"><LINK
@ -70,8 +70,8 @@ CLASS="chapter"
><H1
><A
NAME="ch01"
>Chapter 1. Introduction </A
></H1
></A
>Chapter 1. Introduction </H1
><DIV
CLASS="TOC"
><DL
@ -97,24 +97,24 @@ HREF="Bv9ARM.ch01.html#AEN42"
><DT
>1.4. <A
HREF="Bv9ARM.ch01.html#AEN107"
>The Domain Name System (<SPAN
>The Domain Name System (<ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
>)</A
></DT
></DL
></DIV
><P
>The Internet Domain Name System (<SPAN
>The Internet Domain Name System (<ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
>) consists of the syntax
to specify the names of entities in the Internet in a hierarchical
manner, the rules used for delegating authority over names, and the
system implementation that actually maps names to Internet
addresses. <SPAN
addresses. <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
> data is maintained in a group of distributed
hierarchical databases.</P
><DIV
@ -126,19 +126,19 @@ NAME="AEN15"
>1.1. Scope of Document</A
></H1
><P
>The Berkeley Internet Name Domain (<SPAN
>The Berkeley Internet Name Domain (<ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
>) implements an
domain name server for a number of operating systems. This
document provides basic information about the installation and
care of the Internet Software Consortium (<SPAN
care of the Internet Software Consortium (<ACRONYM
CLASS="acronym"
>ISC</SPAN
>ISC</ACRONYM
>)
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> version 9 software package for system
administrators.</P
><P
@ -160,12 +160,12 @@ CLASS="emphasis"
>Section 1</I
></SPAN
> introduces
the basic <SPAN
the basic <ACRONYM
CLASS="acronym"
>DNS</SPAN
> and <SPAN
>DNS</ACRONYM
> and <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> concepts. <SPAN
CLASS="emphasis"
><I
@ -173,9 +173,9 @@ CLASS="emphasis"
>Section 2</I
></SPAN
>
describes resource requirements for running <SPAN
describes resource requirements for running <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> in various
environments. Information in <SPAN
CLASS="emphasis"
@ -192,9 +192,9 @@ CLASS="emphasis"
></SPAN
> in its presentation and is
organized functionally, to aid in the process of installing the
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 software. The task-oriented section is followed by
<SPAN
CLASS="emphasis"
@ -211,9 +211,9 @@ CLASS="emphasis"
>Section 5</I
></SPAN
>
describes the <SPAN
describes the <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 lightweight
resolver. The contents of <SPAN
CLASS="emphasis"
@ -253,9 +253,9 @@ CLASS="emphasis"
>Bibliography</I
></SPAN
> and
historic information related to <SPAN
historic information related to <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> and the Domain Name
System.</P
></DIV
@ -272,11 +272,11 @@ NAME="AEN42"
conventions:</P
><DIV
CLASS="informaltable"
><P
></P
><A
NAME="AEN45"
></A
><P
></P
><TABLE
CELLPADDING="3"
BORDER="1"
@ -284,9 +284,6 @@ CLASS="CALSTABLE"
><TBODY
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13;<P
><SPAN
CLASS="emphasis"
@ -298,9 +295,6 @@ describe:</I
></P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13;<P
><SPAN
CLASS="emphasis"
@ -313,17 +307,11 @@ CLASS="emphasis"
></TR
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13;<P
>a pathname, filename, URL, hostname,
mailing list name, or new term or concept</P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="filename"
@ -333,42 +321,28 @@ CLASS="filename"
></TR
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>literal user
input</P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
><KBD
CLASS="userinput"
><B
>Fixed Width Bold</B
></TT
>Fixed Width Bold</KBD
></P
></TD
></TR
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>program output</P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
><SAMP
CLASS="computeroutput"
>Fixed Width</TT
>Fixed Width</SAMP
></P
></TD
></TR
@ -379,16 +353,16 @@ CLASS="computeroutput"
></DIV
><P
>The following conventions are used in descriptions of the
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> configuration file:<DIV
CLASS="informaltable"
><P
></P
><A
NAME="AEN77"
></A
><P
></P
><TABLE
CELLPADDING="3"
BORDER="1"
@ -396,9 +370,6 @@ CLASS="CALSTABLE"
><TBODY
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><SPAN
CLASS="emphasis"
@ -410,9 +381,6 @@ describe:</I
></P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><SPAN
CLASS="emphasis"
@ -425,54 +393,36 @@ CLASS="emphasis"
></TR
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>keywords</P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
><VAR
CLASS="literal"
>Fixed Width</TT
>Fixed Width</VAR
></P
></TD
></TR
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>variables</P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
><VAR
CLASS="varname"
>Fixed Width</TT
>Fixed Width</VAR
></P
></TD
></TR
><TR
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Optional input</P
></TD
><TD
WIDTH="252"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>[<SPAN
CLASS="optional"
@ -493,24 +443,24 @@ CLASS="sect1"
CLASS="sect1"
><A
NAME="AEN107"
>1.4. The Domain Name System (<SPAN
>1.4. The Domain Name System (<ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
>)</A
></H1
><P
>The purpose of this document is to explain the installation
and upkeep of the <SPAN
and upkeep of the <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> software package, and we
begin by reviewing the fundamentals of the Domain Name System
(<SPAN
(<ACRONYM
CLASS="acronym"
>DNS</SPAN
>) as they relate to <SPAN
>DNS</ACRONYM
>) as they relate to <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
>.
</P
><DIV
@ -542,9 +492,9 @@ CLASS="emphasis"
>name servers</I
></SPAN
> and interprets the responses.
The <SPAN
The <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 software distribution contains a
name server, <B
CLASS="command"
@ -604,30 +554,30 @@ CLASS="emphasis"
>Example, Inc.</I
></SPAN
> could be
<TT
<VAR
CLASS="literal"
>mail.example.com</TT
>mail.example.com</VAR
>,
where <TT
where <VAR
CLASS="literal"
>com</TT
>com</VAR
> is the
top level domain to which
<TT
<VAR
CLASS="literal"
>ourhost.example.com</TT
>ourhost.example.com</VAR
> belongs,
<TT
<VAR
CLASS="literal"
>example</TT
>example</VAR
> is
a subdomain of <TT
a subdomain of <VAR
CLASS="literal"
>com</TT
>com</VAR
>, and
<TT
<VAR
CLASS="literal"
>ourhost</TT
>ourhost</VAR
> is the
name of the host.</P
><P
@ -664,9 +614,9 @@ CLASS="emphasis"
CLASS="emphasis"
>resource records</I
></SPAN
> (<SPAN
> (<ACRONYM
CLASS="acronym"
>RR</SPAN
>RR</ACRONYM
>s).
Some of the supported resource record types are described in
<A
@ -707,9 +657,9 @@ CLASS="emphasis"
>.</P
><P
>As we stated previously, a zone is a point of delegation in
the <SPAN
the <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
> tree. A zone consists of
those contiguous parts of the domain
tree for which a name server has complete information and over which
@ -726,36 +676,36 @@ CLASS="emphasis"
parent zone, which should be matched by equivalent NS records at
the root of the delegated zone.</P
><P
>For instance, consider the <TT
>For instance, consider the <VAR
CLASS="literal"
>example.com</TT
>example.com</VAR
>
domain which includes names
such as <TT
such as <VAR
CLASS="literal"
>host.aaa.example.com</TT
>host.aaa.example.com</VAR
> and
<TT
<VAR
CLASS="literal"
>host.bbb.example.com</TT
>host.bbb.example.com</VAR
> even though
the <TT
the <VAR
CLASS="literal"
>example.com</TT
>example.com</VAR
> zone includes
only delegations for the <TT
only delegations for the <VAR
CLASS="literal"
>aaa.example.com</TT
>aaa.example.com</VAR
> and
<TT
<VAR
CLASS="literal"
>bbb.example.com</TT
>bbb.example.com</VAR
> zones. A zone can map
exactly to a single domain, but could also include only part of a
domain, the rest of which could be delegated to other
name servers. Every name in the <SPAN
name servers. Every name in the <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
> tree is a
<SPAN
CLASS="emphasis"
@ -783,9 +733,9 @@ not intuitive and we suggest that you read RFCs 1033, 1034 and 1035 to
gain a complete understanding of this difficult and subtle
topic.</P
><P
>Though <SPAN
>Though <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> is called a "domain name server",
it deals primarily in terms of zones. The master and slave
declarations in the <TT
@ -1056,14 +1006,14 @@ and they are queried in turn until the list is exhausted or an answer
is found. Forwarders are typically used when you do not
wish all the servers at a given site to interact directly with the rest of
the Internet servers. A typical scenario would involve a number
of internal <SPAN
of internal <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
> servers and an Internet firewall. Servers unable
to pass packets through the firewall would forward to the server
that can do it, and that server would query the Internet <SPAN
that can do it, and that server would query the Internet <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
> servers
on the internal server's behalf. An added benefit of using the forwarding
feature is that the central machine develops a much more complete
@ -1080,9 +1030,9 @@ NAME="AEN218"
>1.4.6. Name Servers in Multiple Roles</A
></H2
><P
>The <SPAN
>The <ACRONYM
CLASS="acronym"
>BIND</SPAN
>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
@ -1169,9 +1119,9 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> Resource Requirements</TD
></TR
></TABLE

40
doc/arm/Bv9ARM.ch02.html
View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>BIND Resource Requirements</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="BIND 9 Administrator Reference Manual"
HREF="Bv9ARM.html"><LINK
@ -70,11 +70,11 @@ CLASS="chapter"
><H1
><A
NAME="ch02"
>Chapter 2. <SPAN
></A
>Chapter 2. <ACRONYM
CLASS="acronym"
>BIND</SPAN
> Resource Requirements</A
></H1
>BIND</ACRONYM
> Resource Requirements</H1
><DIV
CLASS="TOC"
><DL
@ -118,25 +118,25 @@ NAME="AEN228"
>2.1. Hardware requirements</A
></H1
><P
><SPAN
><ACRONYM
CLASS="acronym"
>DNS</SPAN
>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 <SPAN
active duty have performed admirably as <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
> servers.</P
><P
>The DNSSEC and IPv6 features of <SPAN
>The DNSSEC and IPv6 features of <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 may prove to be quite
CPU intensive however, so organizations that make heavy use of these
features may wish to consider larger systems for these applications.
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 is fully multithreaded, allowing full utilization of
multiprocessor systems for installations that need it.</P
></DIV
@ -149,9 +149,9 @@ NAME="AEN236"
>2.2. CPU Requirements</A
></H1
><P
>CPU requirements for <SPAN
>CPU requirements for <ACRONYM
CLASS="acronym"
>BIND</SPAN
>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
@ -172,9 +172,9 @@ CLASS="command"
>max-cache-size</B
>
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 <SPAN
at the expense of reducing cache hit rates and causing more <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
>
traffic. It is still good practice to have enough memory to load
all zone and cache data into memory &#8212; unfortunately, the best way
@ -212,9 +212,9 @@ NAME="AEN248"
>2.5. Supported Operating Systems</A
></H1
><P
>ISC <SPAN
>ISC <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 compiles and runs on a large number
of Unix-like operating system and on Windows NT / 2000. For an up-to-date
list of supported systems, see the README file in the top level directory

580
doc/arm/Bv9ARM.ch03.html
View file

File diff suppressed because it is too large Load diff

268
doc/arm/Bv9ARM.ch04.html
View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Advanced DNS Features</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="BIND 9 Administrator Reference Manual"
HREF="Bv9ARM.html"><LINK
@ -70,8 +70,8 @@ CLASS="chapter"
><H1
><A
NAME="ch04"
>Chapter 4. Advanced DNS Features</A
></H1
></A
>Chapter 4. Advanced DNS Features</H1
><DIV
CLASS="TOC"
><DL
@ -122,9 +122,9 @@ HREF="Bv9ARM.ch04.html#DNSSEC"
><DT
>4.9. <A
HREF="Bv9ARM.ch04.html#AEN1001"
>IPv6 Support in <SPAN
>IPv6 Support in <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9</A
></DT
></DL
@ -138,9 +138,9 @@ NAME="notify"
>4.1. Notify</A
></H1
><P
><SPAN
><ACRONYM
CLASS="acronym"
>DNS</SPAN
>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 <B
@ -150,9 +150,9 @@ CLASS="command"
slave will check to see that its version of the zone is the
current version and, if not, initiate a zone transfer.</P
><P
><SPAN
><ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
>
For more information about
<B
@ -261,11 +261,9 @@ CLASS="command"
to the zone using
<B
CLASS="command"
>rndc freeze <TT
>rndc freeze <VAR
CLASS="replaceable"
><I
>zone</I
></TT
>zone</VAR
></B
>.
This will also remove the zone's <TT
@ -275,11 +273,9 @@ CLASS="filename"
and update the master file. Edit the zone file. Run
<B
CLASS="command"
>rndc unfreeze <TT
>rndc unfreeze <VAR
CLASS="replaceable"
><I
>zone</I
></TT
>zone</VAR
></B
>
to reload the changed zone and re-enable dynamic updates.</P
@ -302,9 +298,9 @@ HREF="Bv9ARM.ch09.html#proposed_standards"
>Proposed Standards</A
>.</P
><P
>When acting as a master, <SPAN
>When acting as a master, <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9
supports IXFR for those zones
where the necessary change history information is available. These
@ -316,17 +312,15 @@ transfer (AXFR), IXFR is supported only if the option
CLASS="command"
>ixfr-from-differences</B
> is set
to <TT
to <KBD
CLASS="userinput"
><B
>yes</B
></TT
>yes</KBD
>.
</P
><P
>When acting as a slave, <SPAN
>When acting as a slave, <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 will
attempt to use IXFR unless
it is explicitly disabled. For more information about disabling
@ -381,9 +375,9 @@ CLASS="emphasis"
>Example, Inc.</I
></SPAN
>
(<TT
(<VAR
CLASS="literal"
>example.com</TT
>example.com</VAR
>)
has several corporate sites that have an internal network with reserved
Internet Protocol (IP) space and an external demilitarized zone (DMZ),
@ -495,9 +489,9 @@ internal hosts.</P
>Here's an example of a wildcard MX record:</P
><PRE
CLASS="programlisting"
><TT
><VAR
CLASS="literal"
>* IN MX 10 external1.example.com.</TT
>* IN MX 10 external1.example.com.</VAR
></PRE
><P
>Now that they accept mail on behalf of anything in the internal
@ -534,24 +528,24 @@ internal clients will now be able to:</P
><UL
><LI
><P
>Look up any hostnames in the <TT
>Look up any hostnames in the <VAR
CLASS="literal"
>site1</TT
>site1</VAR
> and
<TT
<VAR
CLASS="literal"
>site2.example.com</TT
>site2.example.com</VAR
> zones.</P
></LI
><LI
><P
>Look up any hostnames in the <TT
>Look up any hostnames in the <VAR
CLASS="literal"
>site1.internal</TT
>site1.internal</VAR
> and
<TT
<VAR
CLASS="literal"
>site2.internal</TT
>site2.internal</VAR
> domains.</P
></LI
><LI
@ -570,24 +564,24 @@ CLASS="literal"
><UL
><LI
><P
>Look up any hostnames in the <TT
>Look up any hostnames in the <VAR
CLASS="literal"
>site1</TT
>site1</VAR
> and
<TT
<VAR
CLASS="literal"
>site2.example.com</TT
>site2.example.com</VAR
> zones.</P
></LI
><LI
><P
>Exchange mail with anyone in the <TT
>Exchange mail with anyone in the <VAR
CLASS="literal"
>site1</TT
>site1</VAR
> and
<TT
<VAR
CLASS="literal"
>site2.example.com</TT
>site2.example.com</VAR
> zones.</P
></LI
></UL
@ -605,9 +599,9 @@ CLASS="programlisting"
>&#13;
acl internals { 172.16.72.0/24; 192.168.1.0/24; };
acl externals { <TT
acl externals { <VAR
CLASS="varname"
>bastion-ips-go-here</TT
>bastion-ips-go-here</VAR
>; };
options {
@ -615,9 +609,9 @@ options {
...
forward only;
forwarders { // forward to external servers
<TT
<VAR
CLASS="varname"
>bastion-ips-go-here</TT
>bastion-ips-go-here</VAR
>;
};
allow-transfer { none; }; // sample allow-transfer (no one)
@ -719,25 +713,25 @@ NAME="tsig"
></H1
><P
>This is a short guide to setting up Transaction SIGnatures
(TSIG) based transaction security in <SPAN
(TSIG) based transaction security in <ACRONYM
CLASS="acronym"
>BIND</SPAN
>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 <SPAN
keys and using transaction signatures with <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
>.</P
><P
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>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 <SPAN
Resolvers based on newer versions of <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 8 have limited support
for TSIG.</P
><P
@ -749,13 +743,13 @@ for TSIG.</P
CLASS="command"
>nsupdate</B
>
program supports TSIG via the <TT
program supports TSIG via the <VAR
CLASS="option"
>-k</TT
>-k</VAR
> and
<TT
<VAR
CLASS="option"
>-y</TT
>-y</VAR
> command line options.</P
><DIV
CLASS="sect2"
@ -796,11 +790,9 @@ are easier to read. Note that the maximum key length is 512 bits;
keys longer than that will be digested with MD5 to produce a 128
bit key.</P
><P
><TT
><KBD
CLASS="userinput"
><B
>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</B
></TT
>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</KBD
></P
><P
>The key is in the file <TT
@ -808,18 +800,18 @@ CLASS="filename"
>Khost1-host2.+157+00000.private</TT
>.
Nothing directly uses this file, but the base-64 encoded string
following "<TT
following "<VAR
CLASS="literal"
>Key:</TT
>Key:</VAR
>"
can be extracted from the file and used as a shared secret:</P
><PRE
CLASS="programlisting"
>Key: La/E5CjG9O+os1jq0a2jdA==</PRE
><P
>The string "<TT
>The string "<VAR
CLASS="literal"
>La/E5CjG9O+os1jq0a2jdA==</TT
>La/E5CjG9O+os1jq0a2jdA==</VAR
>" can
be used as the shared secret.</P
></DIV
@ -890,9 +882,9 @@ CLASS="programlisting"
};
</PRE
><P
>The algorithm, hmac-md5, is the only one supported by <SPAN
>The algorithm, hmac-md5, is the only one supported by <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
>.
The secret is the one generated above. Since this is a secret, it
is recommended that either <TT
@ -1003,9 +995,9 @@ NAME="AEN900"
>4.5.5. TSIG Key Based Access Control</A
></H2
><P
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> allows IP addresses and ranges to be specified in ACL
definitions and
<B
@ -1087,9 +1079,9 @@ CLASS="command"
CLASS="command"
>TKEY</B
> that specify how the key is
generated or assigned. <SPAN
generated or assigned. <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9
implements only one of these modes,
the Diffie-Hellman key exchange. Both hosts are required to have
@ -1145,9 +1137,9 @@ NAME="AEN932"
>4.7. SIG(0)</A
></H1
><P
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 partially supports DNSSEC SIG(0)
transaction signatures as specified in RFC 2535 and RFC2931. SIG(0)
uses public/private keys to authenticate messages. Access control
@ -1161,9 +1153,9 @@ CLASS="acronym"
>SIG(0) signing of multiple-message TCP streams is not
supported.</P
><P
>The only tool shipped with <SPAN
>The only tool shipped with <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 that
generates SIG(0) signed messages is <B
CLASS="command"
@ -1191,21 +1183,21 @@ CLASS="emphasis"
of DNSSEC signed zones.</P
><P
>In order to set up a DNSSEC secure zone, there are a series
of steps which must be followed. <SPAN
of steps which must be followed. <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 ships
with several tools
that are used in this process, which are explained in more detail
below. In all cases, the <TT
below. In all cases, the <VAR
CLASS="option"
>-h</TT
>-h</VAR
> option prints a
full list of parameters. Note that the DNSSEC tools require the
keyset files to be in the working directory or the
directory specified by the <TT
directory specified by the <VAR
CLASS="option"
>-h</TT
>-h</VAR
> option, and
that the tools shipped with BIND 9.2.x and earlier are not compatible
with the current ones.</P
@ -1214,9 +1206,9 @@ CLASS="option"
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
resolver to trust its data. This is done through the presense
or absence of a <TT
or absence of a <VAR
CLASS="literal"
>DS</TT
>DS</VAR
> record at the delegation
point.</P
><P
@ -1256,11 +1248,9 @@ CLASS="filename"
>child.example</TT
> zone:</P
><P
><TT
><KBD
CLASS="userinput"
><B
>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</B
></TT
>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</KBD
></P
><P
>Two output files will be produced:
@ -1323,24 +1313,24 @@ CLASS="filename"
>keyset</TT
> files corresponding
to secure subzones should be present. The zone signer will
generate <TT
generate <VAR
CLASS="literal"
>NSEC</TT
> and <TT
>NSEC</VAR
> and <VAR
CLASS="literal"
>RRSIG</TT
>RRSIG</VAR
>
records for the zone, as well as <TT
records for the zone, as well as <VAR
CLASS="literal"
>DS</TT
>DS</VAR
> for
the child zones if <TT
the child zones if <VAR
CLASS="literal"
>'-d'</TT
>'-d'</VAR
> is specified.
If <TT
If <VAR
CLASS="literal"
>'-d'</TT
>'-d'</VAR
> is not specified then DS RRsets for
the secure child zones need to be added manually.</P
><P
@ -1352,11 +1342,9 @@ CLASS="filename"
default, all zone keys which have an available private key are
used to generate signatures.</P
><P
><TT
><KBD
CLASS="userinput"
><B
>dnssec-signzone -o child.example zone.child.example</B
></TT
>dnssec-signzone -o child.example zone.child.example</KBD
></P
><P
>One output file is produced:
@ -1376,12 +1364,12 @@ CLASS="command"
> will also produce a
keyset and dsset files and optionally a dlvset file. These
are used to provide the parent zone administators with the
<TT
<VAR
CLASS="literal"
>DNSKEYs</TT
> (or their corresponding <TT
>DNSKEYs</VAR
> (or their corresponding <VAR
CLASS="literal"
>DS</TT
>DS</VAR
>
records) that are the secure entry point to the zone.</P
></DIV
@ -1394,13 +1382,13 @@ NAME="AEN994"
>4.8.3. Configuring Servers</A
></H2
><P
>Unlike <SPAN
>Unlike <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 8,
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>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
@ -1419,41 +1407,41 @@ CLASS="sect1"
CLASS="sect1"
><A
NAME="AEN1001"
>4.9. IPv6 Support in <SPAN
>4.9. IPv6 Support in <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9</A
></H1
><P
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>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
>For forward lookups, <SPAN
>For forward lookups, <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 supports only AAAA
records. The use of A6 records is deprecated by RFC 3363, and the
support for forward lookups in <SPAN
support for forward lookups in <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 is
removed accordingly.
However, authoritative <SPAN
However, authoritative <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 name servers still
load zone files containing A6 records correctly, answer queries
for A6 records, and accept zone transfer for a zone containing A6
records.</P
><P
>For IPv6 reverse lookups, <SPAN
>For IPv6 reverse lookups, <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 supports
the traditional "nibble" format used in the
<SPAN
@ -1470,21 +1458,21 @@ CLASS="emphasis"
>ip6.int</I
></SPAN
> domain.
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 formerly
supported the "binary label" (also known as "bitstring") format.
The support of binary labels, however, is now completely removed
according to the changes in RFC 3363.
Any applications in <SPAN
Any applications in <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 do not understand
the format any more, and will return an error if given.
In particular, an authoritative <SPAN
In particular, an authoritative <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 name
server rejects to load a zone file containing binary labels.</P
><P
@ -1513,9 +1501,9 @@ host 3600 IN AAAA 2001:db8::1
><P
>It is recommended that IPv4-in-IPv6 mapped addresses not
be used. If a host has an IPv4 address, use an A record, not
a AAAA, with <TT
a AAAA, with <VAR
CLASS="literal"
>::ffff:192.168.42.1</TT
>::ffff:192.168.42.1</VAR
> as the
address.</P
></DIV
@ -1530,15 +1518,15 @@ NAME="AEN1025"
><P
>When looking up an address in nibble format, the address
components are simply reversed, just as in IPv4, and
<TT
<VAR
CLASS="literal"
>ip6.arpa.</TT
>ip6.arpa.</VAR
> is appended to the resulting name.
For example, the following would provide reverse name lookup for
a host with address
<TT
<VAR
CLASS="literal"
>2001:db8::1</TT
>2001:db8::1</VAR
>.</P
><PRE
CLASS="programlisting"
@ -1602,9 +1590,9 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The <SPAN
>The <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 Lightweight Resolver</TD
></TR
></TABLE

20
doc/arm/Bv9ARM.ch05.html
View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>The BIND 9 Lightweight Resolver</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="BIND 9 Administrator Reference Manual"
HREF="Bv9ARM.html"><LINK
@ -70,11 +70,11 @@ CLASS="chapter"
><H1
><A
NAME="ch05"
>Chapter 5. The <SPAN
></A
>Chapter 5. The <ACRONYM
CLASS="acronym"
>BIND</SPAN
> 9 Lightweight Resolver</A
></H1
>BIND</ACRONYM
> 9 Lightweight Resolver</H1
><DIV
CLASS="TOC"
><DL
@ -113,9 +113,9 @@ 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
>Instead, <SPAN
>Instead, <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 provides resolution services to local clients
using a combination of a lightweight resolver library and a resolver
daemon process running on the local host. These communicate using
@ -253,9 +253,9 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 Configuration Reference</TD
></TR
></TABLE

4369
doc/arm/Bv9ARM.ch06.html
View file

File diff suppressed because it is too large Load diff

68
doc/arm/Bv9ARM.ch07.html
View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>BIND 9 Security Considerations</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="BIND 9 Administrator Reference Manual"
HREF="Bv9ARM.html"><LINK
@ -70,11 +70,11 @@ CLASS="chapter"
><H1
><A
NAME="ch07"
>Chapter 7. <SPAN
></A
>Chapter 7. <ACRONYM
CLASS="acronym"
>BIND</SPAN
> 9 Security Considerations</A
></H1
>BIND</ACRONYM
> 9 Security Considerations</H1
><DIV
CLASS="TOC"
><DL
@ -208,9 +208,9 @@ CLASS="command"
UNIX servers)</A
></H1
><P
>On UNIX servers, it is possible to run <SPAN
>On UNIX servers, it is possible to run <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> in a <SPAN
CLASS="emphasis"
><I
@ -221,37 +221,35 @@ CLASS="emphasis"
(<B
CLASS="command"
>chroot()</B
>) by specifying the "<TT
>) by specifying the "<VAR
CLASS="option"
>-t</TT
>-t</VAR
>"
option. This can help improve system security by placing <SPAN
option. This can help improve system security by placing <ACRONYM
CLASS="acronym"
>BIND</SPAN
>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 <SPAN
>Another useful feature in the UNIX version of <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> is the
ability to run the daemon as an unprivileged user ( <TT
ability to run the daemon as an unprivileged user ( <VAR
CLASS="option"
>-u</TT
> <TT
>-u</VAR
> <VAR
CLASS="replaceable"
><I
>user</I
></TT
>user</VAR
> ).
We suggest running as an unprivileged user when using the <B
CLASS="command"
>chroot</B
> feature.</P
><P
>Here is an example command line to load <SPAN
>Here is an example command line to load <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> in a <B
CLASS="command"
>chroot()</B
@ -268,11 +266,9 @@ CLASS="command"
> to
user 202:</P
><P
><TT
><KBD
CLASS="userinput"
><B
>/usr/local/bin/named -u 202 -t /var/named</B
></TT
>/usr/local/bin/named -u 202 -t /var/named</KBD
></P
><DIV
CLASS="sect2"
@ -296,13 +292,13 @@ CLASS="filename"
>/var/named</TT
>),
you will need to set up an environment that includes everything
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> needs to run.
From <SPAN
From <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
>'s point of view, <TT
CLASS="filename"
>/var/named</TT
@ -375,9 +371,9 @@ CLASS="command"
>chown</B
> utility (to
set the user id and/or group id) on files
to which you want <SPAN
to which you want <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
>
to write. Note that if the <B
CLASS="command"
@ -398,9 +394,9 @@ NAME="dynamic_update_security"
><P
>Access to the dynamic
update facility should be strictly limited. In earlier versions of
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
>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 <B
@ -482,9 +478,9 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 Configuration Reference</TD
><TD
WIDTH="34%"

44
doc/arm/Bv9ARM.ch08.html
View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="BIND 9 Administrator Reference Manual"
HREF="Bv9ARM.html"><LINK
@ -70,8 +70,8 @@ CLASS="chapter"
><H1
><A
NAME="ch08"
>Chapter 8. Troubleshooting</A
></H1
></A
>Chapter 8. Troubleshooting</H1
><DIV
CLASS="TOC"
><DL
@ -158,35 +158,35 @@ NAME="AEN4743"
>8.3. Where Can I Get Help?</A
></H1
><P
>The Internet Software Consortium (<SPAN
>The Internet Software Consortium (<ACRONYM
CLASS="acronym"
>ISC</SPAN
>ISC</ACRONYM
>) offers a wide range
of support and service agreements for <SPAN
of support and service agreements for <ACRONYM
CLASS="acronym"
>BIND</SPAN
> and <SPAN
>BIND</ACRONYM
> and <ACRONYM
CLASS="acronym"
>DHCP</SPAN
>DHCP</ACRONYM
> servers. Four
levels of premium support are available and each level includes
support for all <SPAN
support for all <ACRONYM
CLASS="acronym"
>ISC</SPAN
>ISC</ACRONYM
> programs, significant discounts on products
and training, and a recognized priority on bug fixes and
non-funded feature requests. In addition, <SPAN
non-funded feature requests. In addition, <ACRONYM
CLASS="acronym"
>ISC</SPAN
>ISC</ACRONYM
> offers a standard
support agreement package which includes services ranging from bug
fix announcements to remote support. It also includes training in
<SPAN
<ACRONYM
CLASS="acronym"
>BIND</SPAN
> and <SPAN
>BIND</ACRONYM
> and <ACRONYM
CLASS="acronym"
>DHCP</SPAN
>DHCP</ACRONYM
>.</P
><P
>To discuss arrangements for support, contact
@ -195,9 +195,9 @@ HREF="mailto:info@isc.org"
TARGET="_top"
>info@isc.org</A
> or visit the
<SPAN
<ACRONYM
CLASS="acronym"
>ISC</SPAN
>ISC</ACRONYM
> web page at <A
HREF="http://www.isc.org/services/support/"
TARGET="_top"
@ -250,9 +250,9 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 Security Considerations</TD
><TD
WIDTH="34%"

426
doc/arm/Bv9ARM.ch09.html
View file

File diff suppressed because it is too large Load diff

52
doc/arm/Bv9ARM.html
View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>BIND 9 Administrator Reference Manual</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="NEXT"
TITLE="Introduction "
HREF="Bv9ARM.ch01.html"></HEAD
@ -31,10 +31,10 @@ NAME="AEN1"
></H1
><P
CLASS="copyright"
>Copyright &copy; 2004 by Internet Systems Consortium, Inc. ("ISC")</P
>Copyright &copy; 2004 Internet Systems Consortium, Inc. ("ISC")</P
><P
CLASS="copyright"
>Copyright &copy; 2000-2003 by Internet Software Consortium</P
>Copyright &copy; 2000-2003 Internet Software Consortium</P
><HR></DIV
><DIV
CLASS="TOC"
@ -68,9 +68,9 @@ HREF="Bv9ARM.ch01.html#AEN42"
><DT
>1.4. <A
HREF="Bv9ARM.ch01.html#AEN107"
>The Domain Name System (<SPAN
>The Domain Name System (<ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
>)</A
></DT
><DD
@ -112,9 +112,9 @@ HREF="Bv9ARM.ch01.html#AEN218"
><DT
>2. <A
HREF="Bv9ARM.ch02.html"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> Resource Requirements</A
></DT
><DD
@ -310,9 +310,9 @@ HREF="Bv9ARM.ch04.html#AEN994"
><DT
>4.9. <A
HREF="Bv9ARM.ch04.html#AEN1001"
>IPv6 Support in <SPAN
>IPv6 Support in <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9</A
></DT
><DD
@ -334,9 +334,9 @@ HREF="Bv9ARM.ch04.html#AEN1025"
><DT
>5. <A
HREF="Bv9ARM.ch05.html"
>The <SPAN
>The <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 Lightweight Resolver</A
></DT
><DD
@ -356,9 +356,9 @@ HREF="Bv9ARM.ch05.html#lwresd"
><DT
>6. <A
HREF="Bv9ARM.ch06.html"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 Configuration Reference</A
></DT
><DD
@ -621,9 +621,9 @@ HREF="Bv9ARM.ch06.html#AEN4496"
><DT
>6.3.6. <A
HREF="Bv9ARM.ch06.html#AEN4554"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> Master File Extension: the <B
CLASS="command"
>$GENERATE</B
@ -636,9 +636,9 @@ CLASS="command"
><DT
>7. <A
HREF="Bv9ARM.ch07.html"
><SPAN
><ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
> 9 Security Considerations</A
></DT
><DD
@ -737,12 +737,12 @@ HREF="Bv9ARM.ch09.html#AEN4759"
><DT
>A.1.1. <A
HREF="Bv9ARM.ch09.html#AEN4761"
>A Brief History of the <SPAN
>A Brief History of the <ACRONYM
CLASS="acronym"
>DNS</SPAN
> and <SPAN
>DNS</ACRONYM
> and <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
></A
></DT
></DL
@ -750,9 +750,9 @@ CLASS="acronym"
><DT
>A.2. <A
HREF="Bv9ARM.ch09.html#historical_dns_information"
>General <SPAN
>General <ACRONYM
CLASS="acronym"
>DNS</SPAN
>DNS</ACRONYM
> Reference Information</A
></DT
><DD
@ -784,9 +784,9 @@ HREF="Bv9ARM.ch09.html#internet_drafts"
><DT
>A.3.3. <A
HREF="Bv9ARM.ch09.html#AEN5356"
>Other Documents About <SPAN
>Other Documents About <ACRONYM
CLASS="acronym"
>BIND</SPAN
>BIND</ACRONYM
></A
></DT
></DL

156
lib/lwres/man/lwres.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres.html,v 1.5.18.2 2004/04/07 00:58:14 marka Exp $ -->
<!-- $Id: lwres.html,v 1.5.18.3 2004/08/22 23:53:34 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres</A
></H1
></A
>lwres</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN11"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN12"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwres.h&gt;</PRE
@ -98,41 +98,41 @@ NAME="AEN18"
><P
>The lwresd library implements multiple name service APIs.
The standard
<TT
<CODE
CLASS="FUNCTION"
>gethostbyname()</TT
>gethostbyname()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>gethostbyaddr()</TT
>gethostbyaddr()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>gethostbyname_r()</TT
>gethostbyname_r()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>gethostbyaddr_r()</TT
>gethostbyaddr_r()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>getaddrinfo()</TT
>getaddrinfo()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>getipnodebyname()</TT
>getipnodebyname()</CODE
>,
and
<TT
<CODE
CLASS="FUNCTION"
>getipnodebyaddr()</TT
>getipnodebyaddr()</CODE
>
functions are all supported. To allow the lwres library to coexist
with system libraries that define functions of the same name,
the library defines these functions with names prefixed by
<TT
<VAR
CLASS="LITERAL"
>lwres_</TT
>lwres_</VAR
>.
To define the standard names, applications must include the
header file
@ -142,23 +142,23 @@ CLASS="FILENAME"
>
which contains macro definitions mapping the standard function names
into
<TT
<VAR
CLASS="LITERAL"
>lwres_</TT
>lwres_</VAR
>
prefixed ones. Operating system vendors who integrate the lwres
library into their base distributions should rename the functions
in the library proper so that the renaming macros are not needed.</P
><P
>The library also provides a native API consisting of the functions
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrsbyname()</TT
>lwres_getaddrsbyname()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_getnamebyaddr()</TT
>lwres_getnamebyaddr()</CODE
>.
These may be called by applications that require more detailed
control over the lookup process than the standard functions
@ -167,9 +167,9 @@ provide.</P
>In addition to these name service independent address lookup
functions, the library implements a new, experimental API
for looking up arbitrary DNS resource records, using the
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrsbyname()</TT
>lwres_getaddrsbyname()</CODE
>
function.</P
><P
@ -201,66 +201,58 @@ sequence of actions.</P
CLASS="TYPE"
>lwres_packet_t</SPAN
>,
called <TT
called <VAR
CLASS="VARNAME"
>pkt</TT
>pkt</VAR
> below.</P
><P
>(2) Set <TT
>(2) Set <CODE
CLASS="STRUCTFIELD"
><I
>pkt.recvlength</I
></TT
>pkt.recvlength</CODE
> 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
<TT
CLASS="FILENAME"
>lwres.h</TT
>: <TT
>: <CODE
CLASS="CONSTANT"
>LWRES_RECVLENGTH = 4096</TT
>LWRES_RECVLENGTH = 4096</CODE
>.</P
><P
>(3) Set <TT
>(3) Set <CODE
CLASS="STRUCTFIELD"
><I
>pkt.serial</I
></TT
>pkt.serial</CODE
>
to a unique serial number. This value is echoed
back to the application by the remote server.</P
><P
>(4) Set <TT
>(4) Set <CODE
CLASS="STRUCTFIELD"
><I
>pkt.pktflags</I
></TT
>pkt.pktflags</CODE
>. Usually this is set to 0.</P
><P
>(5) Set <TT
>(5) Set <CODE
CLASS="STRUCTFIELD"
><I
>pkt.result</I
></TT
>pkt.result</CODE
> to 0.</P
><P
>(6) Call <TT
>(6) Call <CODE
CLASS="FUNCTION"
>lwres_*request_render()</TT
>lwres_*request_render()</CODE
>,
or marshall in the data using the primitives
such as <TT
such as <CODE
CLASS="FUNCTION"
>lwres_packet_render()</TT
>lwres_packet_render()</CODE
>
and storing the packet data.</P
><P
>(7) Transmit the resulting buffer.</P
><P
>(8) Call <TT
>(8) Call <CODE
CLASS="FUNCTION"
>lwres_*response_parse()</TT
>lwres_*response_parse()</CODE
>
to parse any packets received.</P
><P
@ -283,27 +275,27 @@ following is typically involved in processing each request packet.</P
CLASS="TYPE"
>lwres_packet_t</SPAN
> is used
in both the <TT
in both the <CODE
CLASS="FUNCTION"
>_parse()</TT
> and <TT
>_parse()</CODE
> and <CODE
CLASS="FUNCTION"
>_render()</TT
>_render()</CODE
> calls,
with only a few modifications made
to the packet header's contents between uses. This method is recommended
as it keeps the serial, opcode, and other fields correct.</P
><P
>(1) When a packet is received, call <TT
>(1) When a packet is received, call <CODE
CLASS="FUNCTION"
>lwres_*request_parse()</TT
>lwres_*request_parse()</CODE
> to
unmarshall it. This returns a <SPAN
CLASS="TYPE"
>lwres_packet_t</SPAN
> (also called <TT
> (also called <VAR
CLASS="VARNAME"
>pkt</TT
>pkt</VAR
>, below)
as well as a data specific type, such as <SPAN
CLASS="TYPE"
@ -312,42 +304,36 @@ CLASS="TYPE"
><P
>(2) Process the request in the data specific type.</P
><P
>(3) Set the <TT
>(3) Set the <CODE
CLASS="STRUCTFIELD"
><I
>pkt.result</I
></TT
>pkt.result</CODE
>,
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>pkt.recvlength</I
></TT
>pkt.recvlength</CODE
> as above. All other fields can
be left untouched since they were filled in by the <TT
be left untouched since they were filled in by the <CODE
CLASS="FUNCTION"
>*_parse()</TT
>*_parse()</CODE
> call
above. If using <TT
above. If using <CODE
CLASS="FUNCTION"
>lwres_*response_render()</TT
>lwres_*response_render()</CODE
>,
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>pkt.pktflags</I
></TT
>pkt.pktflags</CODE
> will be set up
properly. Otherwise, the <TT
properly. Otherwise, the <CODE
CLASS="CONSTANT"
>LWRES_LWPACKETFLAG_RESPONSE</TT
>LWRES_LWPACKETFLAG_RESPONSE</CODE
> bit should be
set.</P
><P
>(4) Call the data specific rendering function, such as
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnresponse_render()</TT
>lwres_gabnresponse_render()</CODE
>.</P
><P
>(5) Send the resulting packet to the client.</P

270
lib/lwres/man/lwres_buffer.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_buffer.html,v 1.5.18.2 2004/04/07 00:58:14 marka Exp $ -->
<!-- $Id: lwres_buffer.html,v 1.5.18.3 2004/08/22 23:53:35 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_buffer</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_buffer</A
></H1
></A
>lwres_buffer</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN26"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN27"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwbuffer.h&gt;</PRE
@ -205,9 +205,9 @@ NAME="AEN106"
>These functions provide bounds checked access to a region of memory
where data is being read or written.
They are based on, and similar to, the
<TT
<VAR
CLASS="LITERAL"
>isc_buffer_</TT
>isc_buffer_</VAR
>
functions in the ISC library.</P
><P
@ -308,323 +308,267 @@ CLASS="PROGRAMLISTING"
b-c == optional active region.</PRE
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_buffer_init()</TT
>lwres_buffer_init()</CODE
>
initializes the
<SPAN
CLASS="TYPE"
>lwres_buffer_t</SPAN
>
<TT
<VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
>
and assocates it with the memory region of size
<TT
<VAR
CLASS="PARAMETER"
><I
>length</I
></TT
>length</VAR
>
bytes starting at location
<TT
<VAR
CLASS="PARAMETER"
><I
>base.</I
></TT
>base.</VAR
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_buffer_invalidate()</TT
>lwres_buffer_invalidate()</CODE
>
marks the buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
>
as invalid. Invalidating a buffer after use is not required,
but makes it possible to catch its possible accidental use.</P
><P
>The functions
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_add()</TT
>lwres_buffer_add()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_subtract()</TT
>lwres_buffer_subtract()</CODE
>
respectively increase and decrease the used space in
buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
>
by
<TT
<VAR
CLASS="PARAMETER"
><I
>n</I
></TT
>n</VAR
>
bytes.
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_add()</TT
>lwres_buffer_add()</CODE
>
checks for buffer overflow and
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_subtract()</TT
>lwres_buffer_subtract()</CODE
>
checks for underflow.
These functions do not allocate or deallocate memory.
They just change the value of
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>used</I
></TT
>used</CODE
>.</P
><P
>A buffer is re-initialised by
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_clear()</TT
>lwres_buffer_clear()</CODE
>.
The function sets
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>used</I
></TT
>used</CODE
> ,
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>current</I
></TT
>current</CODE
>
and
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>active</I
></TT
>active</CODE
>
to zero.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_buffer_first</TT
>lwres_buffer_first</CODE
>
makes the consumed region of buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>*p</I
></TT
>*p</VAR
>
empty by setting
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>current</I
></TT
>current</CODE
>
to zero (the start of the buffer).</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_buffer_forward()</TT
>lwres_buffer_forward()</CODE
>
increases the consumed region of buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
>
by
<TT
<VAR
CLASS="PARAMETER"
><I
>n</I
></TT
>n</VAR
>
bytes, checking for overflow.
Similarly,
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_back()</TT
>lwres_buffer_back()</CODE
>
decreases buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>'s
consumed region by
<TT
<VAR
CLASS="PARAMETER"
><I
>n</I
></TT
>n</VAR
>
bytes and checks for underflow.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_buffer_getuint8()</TT
>lwres_buffer_getuint8()</CODE
>
reads an unsigned 8-bit integer from
<TT
<VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
>
and returns it.
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_putuint8()</TT
>lwres_buffer_putuint8()</CODE
>
writes the unsigned 8-bit integer
<TT
<VAR
CLASS="PARAMETER"
><I
>val</I
></TT
>val</VAR
>
to buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
>.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_buffer_getuint16()</TT
>lwres_buffer_getuint16()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_getuint32()</TT
>lwres_buffer_getuint32()</CODE
>
are identical to
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_putuint8()</TT
>lwres_buffer_putuint8()</CODE
>
except that they respectively read an unsigned 16-bit or 32-bit integer
in network byte order from
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>.
Similarly,
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_putuint16()</TT
>lwres_buffer_putuint16()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_putuint32()</TT
>lwres_buffer_putuint32()</CODE
>
writes the unsigned 16-bit or 32-bit integer
<TT
<VAR
CLASS="PARAMETER"
><I
>val</I
></TT
>val</VAR
>
to buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>,
in network byte order.</P
><P
>Arbitrary amounts of data are read or written from a lightweight
resolver buffer with
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_getmem()</TT
>lwres_buffer_getmem()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_putmem()</TT
>lwres_buffer_putmem()</CODE
>
respectively.
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_putmem()</TT
>lwres_buffer_putmem()</CODE
>
copies
<TT
<VAR
CLASS="PARAMETER"
><I
>length</I
></TT
>length</VAR
>
bytes of memory at
<TT
<VAR
CLASS="PARAMETER"
><I
>base</I
></TT
>base</VAR
>
to
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>.
Conversely,
<TT
<CODE
CLASS="FUNCTION"
>lwres_buffer_getmem()</TT
>lwres_buffer_getmem()</CODE
>
copies
<TT
<VAR
CLASS="PARAMETER"
><I
>length</I
></TT
>length</VAR
>
bytes of memory from
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>
to
<TT
<VAR
CLASS="PARAMETER"
><I
>base</I
></TT
>base</VAR
>.</P
></DIV
></BODY

86
lib/lwres/man/lwres_config.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_config.html,v 1.5.18.2 2004/04/07 00:58:14 marka Exp $ -->
<!-- $Id: lwres_config.html,v 1.5.18.3 2004/08/22 23:53:35 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_config</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_config</A
></H1
></A
>lwres_config</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN15"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN16"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwres.h&gt;</PRE
@ -114,9 +114,9 @@ NAME="AEN40"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_conf_init()</TT
>lwres_conf_init()</CODE
>
creates an empty
<SPAN
@ -124,16 +124,14 @@ CLASS="TYPE"
>lwres_conf_t</SPAN
>
structure for lightweight resolver context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_conf_clear()</TT
>lwres_conf_clear()</CODE
>
frees up all the internal memory used by
that
@ -142,30 +140,24 @@ CLASS="TYPE"
>lwres_conf_t</SPAN
>
structure in resolver context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_conf_parse()</TT
>lwres_conf_parse()</CODE
>
opens the file
<TT
<VAR
CLASS="PARAMETER"
><I
>filename</I
></TT
>filename</VAR
>
and parses it to initialise the resolver context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>'s
<SPAN
CLASS="TYPE"
@ -173,9 +165,9 @@ CLASS="TYPE"
>
structure.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_conf_print()</TT
>lwres_conf_print()</CODE
>
prints the
<SPAN
@ -183,22 +175,18 @@ CLASS="TYPE"
>lwres_conf_t</SPAN
>
structure for resolver context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>
to the
<SPAN
CLASS="TYPE"
>FILE</SPAN
>
<TT
<VAR
CLASS="PARAMETER"
><I
>fp</I
></TT
>fp</VAR
>.</P
></DIV
><DIV
@ -209,9 +197,9 @@ NAME="AEN61"
><H2
>RETURN VALUES</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_conf_parse()</TT
>lwres_conf_parse()</CODE
>
returns
<SPAN
@ -219,11 +207,9 @@ CLASS="ERRORCODE"
>LWRES_R_SUCCESS</SPAN
>
if it successfully read and parsed
<TT
<VAR
CLASS="PARAMETER"
><I
>filename</I
></TT
>filename</VAR
>.
It returns
<SPAN
@ -231,18 +217,16 @@ CLASS="ERRORCODE"
>LWRES_R_FAILURE</SPAN
>
if
<TT
<VAR
CLASS="PARAMETER"
><I
>filename</I
></TT
>filename</VAR
>
could not be opened or contained incorrect
resolver statements.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_conf_print()</TT
>lwres_conf_print()</CODE
>
returns
<SPAN

210
lib/lwres/man/lwres_context.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_context.html,v 1.7.18.2 2004/04/07 00:58:14 marka Exp $ -->
<!-- $Id: lwres_context.html,v 1.7.18.3 2004/08/22 23:53:35 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_context</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_context</A
></H1
></A
>lwres_context</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN17"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN18"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwres.h&gt;</PRE
@ -130,9 +130,9 @@ NAME="AEN60"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_context_create()</TT
>lwres_context_create()</CODE
>
creates a
<SPAN
@ -148,11 +148,9 @@ CLASS="TYPE"
>lwres_context_t</SPAN
>
is returned through
<TT
<VAR
CLASS="PARAMETER"
><I
>contextp</I
></TT
>contextp</VAR
>,
a pointer to a
@ -174,33 +172,25 @@ CLASS="TYPE"
><P
>When the lightweight resolver needs to perform dynamic memory
allocation, it will call
<TT
<VAR
CLASS="PARAMETER"
><I
>malloc_function</I
></TT
>malloc_function</VAR
>
to allocate memory and
<TT
<VAR
CLASS="PARAMETER"
><I
>free_function</I
></TT
>free_function</VAR
>
to free it. If
<TT
<VAR
CLASS="PARAMETER"
><I
>malloc_function</I
></TT
>malloc_function</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>free_function</I
></TT
>free_function</VAR
>
are NULL, memory is allocated using
@ -215,48 +205,36 @@ CLASS="REFENTRYTITLE"
>.
It is not permitted to have a NULL
<TT
<VAR
CLASS="PARAMETER"
><I
>malloc_function</I
></TT
>malloc_function</VAR
>
and a non-NULL
<TT
<VAR
CLASS="PARAMETER"
><I
>free_function</I
></TT
>free_function</VAR
>
or vice versa.
<TT
<VAR
CLASS="PARAMETER"
><I
>arg</I
></TT
>arg</VAR
>
is passed as the first parameter to the memory
allocation functions.
If
<TT
<VAR
CLASS="PARAMETER"
><I
>malloc_function</I
></TT
>malloc_function</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>free_function</I
></TT
>free_function</VAR
>
are NULL,
<TT
<VAR
CLASS="PARAMETER"
><I
>arg</I
></TT
>arg</VAR
>
is unused and should be passed as NULL.</P
@ -272,16 +250,14 @@ CLASS="REFENTRYTITLE"
>
and returned via
<TT
<VAR
CLASS="PARAMETER"
><I
>*contextp</I
></TT
>*contextp</VAR
>.&#13;</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_context_destroy()</TT
>lwres_context_destroy()</CODE
>
destroys a
<SPAN
@ -290,11 +266,9 @@ CLASS="TYPE"
>,
closing its socket.
<TT
<VAR
CLASS="PARAMETER"
><I
>contextp</I
></TT
>contextp</VAR
>
is a pointer to a pointer to the context that is to be destroyed.
The pointer will be set to NULL when the context has been destroyed.</P
@ -302,124 +276,106 @@ The pointer will be set to NULL when the context has been destroyed.</P
>The context holds a serial number that is used to identify resolver
request packets and associate responses with the corresponding requests.
This serial number is controlled using
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_initserial()</TT
>lwres_context_initserial()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_nextserial()</TT
>lwres_context_nextserial()</CODE
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_initserial()</TT
>lwres_context_initserial()</CODE
>
sets the serial number for context
<TT
<VAR
CLASS="PARAMETER"
><I
>*ctx</I
></TT
>*ctx</VAR
>
to
<TT
<VAR
CLASS="PARAMETER"
><I
>serial</I
></TT
>serial</VAR
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_nextserial()</TT
>lwres_context_nextserial()</CODE
>
increments the serial number and returns the previous value.</P
><P
>Memory for a lightweight resolver context is allocated and freed using
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_allocmem()</TT
>lwres_context_allocmem()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_freemem()</TT
>lwres_context_freemem()</CODE
>.
These use whatever allocations were defined when the context was
created with
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_create()</TT
>lwres_context_create()</CODE
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_allocmem()</TT
>lwres_context_allocmem()</CODE
>
allocates
<TT
<VAR
CLASS="PARAMETER"
><I
>len</I
></TT
>len</VAR
>
bytes of memory and if successful returns a pointer to the allocated
storage.
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_freemem()</TT
>lwres_context_freemem()</CODE
>
frees
<TT
<VAR
CLASS="PARAMETER"
><I
>len</I
></TT
>len</VAR
>
bytes of space starting at location
<TT
<VAR
CLASS="PARAMETER"
><I
>mem</I
></TT
>mem</VAR
>.&#13;</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_context_sendrecv()</TT
>lwres_context_sendrecv()</CODE
>
performs I/O for the context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>.
Data are read and written from the context's socket.
It writes data from
<TT
<VAR
CLASS="PARAMETER"
><I
>sendbase</I
></TT
>sendbase</VAR
>
&mdash; typically a lightweight resolver query packet &mdash;
and waits for a reply which is copied to the receive buffer at
<TT
<VAR
CLASS="PARAMETER"
><I
>recvbase</I
></TT
>recvbase</VAR
>.
The number of bytes that were written to this receive buffer is
returned in
<TT
<VAR
CLASS="PARAMETER"
><I
>*recvd_len</I
></TT
>*recvd_len</VAR
>.&#13;</P
></DIV
><DIV
@ -430,9 +386,9 @@ NAME="AEN115"
><H2
>RETURN VALUES</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_context_create()</TT
>lwres_context_create()</CODE
>
returns
<SPAN
@ -452,9 +408,9 @@ CLASS="ERRORCODE"
otherwise.</P
><P
>Successful calls to the memory allocator
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_allocmem()</TT
>lwres_context_allocmem()</CODE
>
return a pointer to the start of the allocated space.
It returns NULL if memory could not be allocated.</P
@ -464,9 +420,9 @@ CLASS="ERRORCODE"
>LWRES_R_SUCCESS</SPAN
>
is returned when
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_sendrecv()</TT
>lwres_context_sendrecv()</CODE
>
completes successfully.
<SPAN
@ -479,9 +435,9 @@ CLASS="ERRORCODE"
>LWRES_R_TIMEOUT</SPAN
>
is returned if
<TT
<CODE
CLASS="FUNCTION"
>lwres_context_sendrecv()</TT
>lwres_context_sendrecv()</CODE
>
times out waiting for a response.</P
></DIV

144
lib/lwres/man/lwres_gabn.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_gabn.html,v 1.7.18.2 2004/04/07 00:58:14 marka Exp $ -->
<!-- $Id: lwres_gabn.html,v 1.7.18.3 2004/08/22 23:53:35 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_gabn</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_gabn</A
></H1
></A
>lwres_gabn</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN16"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN17"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwres.h&gt;</PRE
@ -178,52 +178,42 @@ typedef struct {
} lwres_gabnresponse_t;</PRE
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gabnrequest_render()</TT
>lwres_gabnrequest_render()</CODE
>
uses resolver context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>
to convert getaddrbyname request structure
<TT
<VAR
CLASS="PARAMETER"
><I
>req</I
></TT
>req</VAR
>
to canonical format.
The packet header structure
<TT
<VAR
CLASS="PARAMETER"
><I
>pkt</I
></TT
>pkt</VAR
>
is initialised and transferred to
buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>.
The contents of
<TT
<VAR
CLASS="PARAMETER"
><I
>*req</I
></TT
>*req</VAR
>
are then appended to the buffer in canonical format.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnresponse_render()</TT
>lwres_gabnresponse_render()</CODE
>
performs the same task, except it converts a getaddrbyname response structure
<SPAN
@ -232,23 +222,19 @@ CLASS="TYPE"
>
to the lightweight resolver's canonical format.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gabnrequest_parse()</TT
>lwres_gabnrequest_parse()</CODE
>
uses context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>
to convert the contents of packet
<TT
<VAR
CLASS="PARAMETER"
><I
>pkt</I
></TT
>pkt</VAR
>
to a
<SPAN
@ -257,11 +243,9 @@ CLASS="TYPE"
>
structure.
Buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>
provides space to be used for storing this structure.
When the function succeeds, the resulting
@ -270,21 +254,19 @@ CLASS="TYPE"
>lwres_gabnrequest_t</SPAN
>
is made available through
<TT
<VAR
CLASS="PARAMETER"
><I
>*structp</I
></TT
>*structp</VAR
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnresponse_parse()</TT
>lwres_gabnresponse_parse()</CODE
>
offers the same semantics as
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnrequest_parse()</TT
>lwres_gabnrequest_parse()</CODE
>
except it yields a
<SPAN
@ -293,21 +275,19 @@ CLASS="TYPE"
>
structure.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gabnresponse_free()</TT
>lwres_gabnresponse_free()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnrequest_free()</TT
>lwres_gabnrequest_free()</CODE
>
release the memory in resolver context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
>
that was allocated to the
<SPAN
@ -320,11 +300,9 @@ CLASS="TYPE"
>lwres_gabnrequest_t</SPAN
>
structures referenced via
<TT
<VAR
CLASS="PARAMETER"
><I
>structp</I
></TT
>structp</VAR
>.
Any memory associated with ancillary buffers and strings for those
@ -339,22 +317,22 @@ NAME="AEN93"
>RETURN VALUES</H2
><P
>The getaddrbyname opcode functions
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnrequest_render()</TT
>lwres_gabnrequest_render()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnresponse_render()</TT
>lwres_gabnresponse_render()</CODE
>
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnrequest_parse()</TT
>lwres_gabnrequest_parse()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnresponse_parse()</TT
>lwres_gabnresponse_parse()</CODE
>
all return
<SPAN
@ -373,11 +351,9 @@ CLASS="ERRORCODE"
>LWRES_R_UNEXPECTEDEND</SPAN
>
is returned if the available space in the buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>
is too small to accommodate the packet header or the
<SPAN
@ -390,14 +366,14 @@ CLASS="TYPE"
>lwres_gabnresponse_t</SPAN
>
structures.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnrequest_parse()</TT
>lwres_gabnrequest_parse()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gabnresponse_parse()</TT
>lwres_gabnresponse_parse()</CODE
>
will return
<SPAN
@ -411,11 +387,9 @@ CLASS="ERRORCODE"
>LWRES_R_FAILURE</SPAN
>
if
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>pktflags</I
></TT
>pktflags</CODE
>
in the packet header structure
<SPAN

60
lib/lwres/man/lwres_gai_strerror.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_gai_strerror.html,v 1.6.18.2 2004/04/07 00:58:15 marka Exp $ -->
<!-- $Id: lwres_gai_strerror.html,v 1.6.18.3 2004/08/22 23:53:36 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_gai_strerror</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_gai_strerror</A
></H1
></A
>lwres_gai_strerror</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN11"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN12"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/netdb.h&gt;</PRE
@ -82,14 +82,14 @@ NAME="AEN18"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gai_strerror()</TT
>lwres_gai_strerror()</CODE
>
returns an error message corresponding to an error code returned by
<TT
<CODE
CLASS="FUNCTION"
>getaddrinfo()</TT
>getaddrinfo()</CODE
>.
The following error codes and their meaning are defined in
<TT
@ -127,9 +127,9 @@ CLASS="ERRORCODE"
><DD
><P
>invalid value for
<TT
<CODE
CLASS="CONSTANT"
>ai_flags</TT
>ai_flags</CODE
></P
></DD
><DT
@ -148,9 +148,9 @@ CLASS="ERRORCODE"
></DT
><DD
><P
><TT
><CODE
CLASS="CONSTANT"
>ai_family</TT
>ai_family</CODE
> not supported</P
></DD
><DT
@ -187,9 +187,9 @@ CLASS="ERRORCODE"
></DT
><DD
><P
>servname not supported for <TT
>servname not supported for <CODE
CLASS="CONSTANT"
>ai_socktype</TT
>ai_socktype</CODE
></P
></DD
><DT
@ -199,9 +199,9 @@ CLASS="ERRORCODE"
></DT
><DD
><P
><TT
><CODE
CLASS="CONSTANT"
>ai_socktype</TT
>ai_socktype</CODE
> not supported</P
></DD
><DT
@ -220,26 +220,24 @@ The message <SPAN
CLASS="ERRORNAME"
>invalid error code</SPAN
> is returned if
<TT
<VAR
CLASS="PARAMETER"
><I
>ecode</I
></TT
>ecode</VAR
>
is out of range.</P
><P
><TT
><CODE
CLASS="CONSTANT"
>ai_flags</TT
>ai_flags</CODE
>,
<TT
<CODE
CLASS="CONSTANT"
>ai_family</TT
>ai_family</CODE
>
and
<TT
<CODE
CLASS="CONSTANT"
>ai_socktype</TT
>ai_socktype</CODE
>
are elements of the
<SPAN
@ -247,9 +245,9 @@ CLASS="TYPE"
>struct addrinfo</SPAN
>
used by
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>.</P
></DIV
><DIV

230
lib/lwres/man/lwres_getaddrinfo.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_getaddrinfo.html,v 1.10.18.2 2004/04/07 00:58:15 marka Exp $ -->
<!-- $Id: lwres_getaddrinfo.html,v 1.10.18.3 2004/08/22 23:53:36 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_getaddrinfo</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_getaddrinfo</A
></H1
></A
>lwres_getaddrinfo</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN12"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN13"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/netdb.h&gt;</PRE
@ -111,43 +111,35 @@ NAME="AEN29"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>
is used to get a list of IP addresses and port numbers for host
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>
and service
<TT
<VAR
CLASS="PARAMETER"
><I
>servname</I
></TT
>servname</VAR
>.
The function is the lightweight resolver's implementation of
<TT
<CODE
CLASS="FUNCTION"
>getaddrinfo()</TT
>getaddrinfo()</CODE
>
as defined in RFC2133.
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>servname</I
></TT
>servname</VAR
>
are pointers to null-terminated
strings or
@ -156,19 +148,15 @@ CLASS="TYPE"
>NULL</SPAN
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>
is either a host name or a numeric host address string: a dotted decimal
IPv4 address or an IPv6 address.
<TT
<VAR
CLASS="PARAMETER"
><I
>servname</I
></TT
>servname</VAR
>
is either a decimal port number or a service name as listed in
<TT
@ -176,11 +164,9 @@ CLASS="FILENAME"
>/etc/services</TT
>.</P
><P
><TT
><VAR
CLASS="PARAMETER"
><I
>hints</I
></TT
>hints</VAR
>
is an optional pointer to a
<SPAN
@ -190,11 +176,9 @@ CLASS="TYPE"
This structure can be used to provide hints concerning the type of socket
that the caller supports or wishes to use.
The caller can supply the following structure elements in
<TT
<VAR
CLASS="PARAMETER"
><I
>*hints</I
></TT
>*hints</VAR
>:
<P
@ -203,17 +187,17 @@ CLASS="PARAMETER"
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>ai_family</TT
>ai_family</CODE
></DT
><DD
><P
>The protocol family that should be used.
When
<TT
<CODE
CLASS="CONSTANT"
>ai_family</TT
>ai_family</CODE
>
is set to
<SPAN
@ -224,9 +208,9 @@ it means the caller will accept any protocol family supported by the
operating system.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ai_socktype</TT
>ai_socktype</CODE
></DT
><DD
><P
@ -246,32 +230,32 @@ CLASS="TYPE"
>
&mdash; that is wanted.
When
<TT
<CODE
CLASS="CONSTANT"
>ai_socktype</TT
>ai_socktype</CODE
>
is zero the caller will accept any socket type.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ai_protocol</TT
>ai_protocol</CODE
></DT
><DD
><P
>indicates which transport protocol is wanted: IPPROTO_UDP or
IPPROTO_TCP.
If
<TT
<CODE
CLASS="CONSTANT"
>ai_protocol</TT
>ai_protocol</CODE
>
is zero the caller will accept any protocol.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ai_flags</TT
>ai_flags</CODE
></DT
><DD
><P
@ -282,15 +266,15 @@ CLASS="TYPE"
>AI_CANONNAME</SPAN
>
bit is set, a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>
will return a null-terminated string containing the canonical name
of the specified hostname in
<TT
<CODE
CLASS="CONSTANT"
>ai_canonname</TT
>ai_canonname</CODE
>
of the first
<SPAN
@ -332,9 +316,9 @@ CLASS="TYPE"
for an IPv6 address.</P
><P
>When
<TT
<CODE
CLASS="CONSTANT"
>ai_flags</TT
>ai_flags</CODE
>
does not set the
<SPAN
@ -378,11 +362,9 @@ CLASS="REFENTRYTITLE"
if a connectionless protocol was chosen.
The IP address portion of the socket address structure will be
set to the loopback address if
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>
is a
<SPAN
@ -395,15 +377,15 @@ CLASS="TYPE"
>AI_PASSIVE</SPAN
>
is not set in
<TT
<CODE
CLASS="CONSTANT"
>ai_flags</TT
>ai_flags</CODE
>.</P
><P
>If
<TT
<CODE
CLASS="CONSTANT"
>ai_flags</TT
>ai_flags</CODE
>
is set to
<SPAN
@ -411,11 +393,9 @@ CLASS="TYPE"
>AI_NUMERICHOST</SPAN
>
it indicates that
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>
should be treated as a numeric string defining an IPv4 or IPv6 address
and no name resolution should be attempted.</P
@ -428,18 +408,14 @@ and no name resolution should be attempted.</P
CLASS="TYPE"
>struct addrinfo</SPAN
> passed
via <TT
via <VAR
CLASS="PARAMETER"
><I
>hints</I
></TT
>hints</VAR
> must be zero.</P
><P
>A <TT
>A <VAR
CLASS="PARAMETER"
><I
>hints</I
></TT
>hints</VAR
> of <SPAN
CLASS="TYPE"
>NULL</SPAN
@ -448,25 +424,23 @@ the caller provided a <SPAN
CLASS="TYPE"
>struct addrinfo</SPAN
> initialized to zero
with <TT
with <CODE
CLASS="CONSTANT"
>ai_family</TT
>ai_family</CODE
>set to
<TT
<CODE
CLASS="CONSTANT"
>PF_UNSPEC</TT
>PF_UNSPEC</CODE
>.</P
><P
>After a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>*res</I
></TT
>*res</VAR
>
is a pointer to a linked list of one or more
<SPAN
@ -481,9 +455,9 @@ CLASS="TYPE"
>
in this list cn be processed by following
the
<TT
<CODE
CLASS="CONSTANT"
>ai_next</TT
>ai_next</CODE
>
pointer, until a
<SPAN
@ -492,18 +466,18 @@ CLASS="TYPE"
>
pointer is encountered.
The three members
<TT
<CODE
CLASS="CONSTANT"
>ai_family</TT
>ai_family</CODE
>,
<TT
<CODE
CLASS="CONSTANT"
>ai_socktype</TT
>ai_socktype</CODE
>,
and
<TT
<CODE
CLASS="CONSTANT"
>ai_protocol</TT
>ai_protocol</CODE
>
in each
returned
@ -525,43 +499,41 @@ CLASS="TYPE"
>addrinfo</SPAN
>
structure in the list, the
<TT
<CODE
CLASS="CONSTANT"
>ai_addr</TT
>ai_addr</CODE
>
member points to a filled-in socket address structure of length
<TT
<CODE
CLASS="CONSTANT"
>ai_addrlen</TT
>ai_addrlen</CODE
>.</P
><P
>All of the information returned by
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>
is dynamically allocated: the addrinfo structures, and the socket
address structures and canonical host name strings pointed to by the
<TT
<CODE
CLASS="CONSTANT"
>addrinfo</TT
>addrinfo</CODE
>structures.
Memory allocated for the dynamically allocated structures created by
a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>
is released by
<TT
<CODE
CLASS="FUNCTION"
>lwres_freeaddrinfo()</TT
>lwres_freeaddrinfo()</CODE
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>ai</I
></TT
>ai</VAR
>
is a pointer to a
<SPAN
@ -569,9 +541,9 @@ CLASS="TYPE"
>struct addrinfo</SPAN
>
created by a call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>.</P
></DIV
><DIV
@ -582,9 +554,9 @@ NAME="AEN142"
><H2
>RETURN VALUES</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>
returns zero on success or one of the error codes listed in
<SPAN
@ -596,27 +568,23 @@ CLASS="REFENTRYTITLE"
>
if an error occurs.
If both
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>
and
<TT
<VAR
CLASS="PARAMETER"
><I
>servname</I
></TT
>servname</VAR
>
are
<SPAN
CLASS="TYPE"
>NULL</SPAN
>
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrinfo()</TT
>lwres_getaddrinfo()</CODE
>
returns
<SPAN

380
lib/lwres/man/lwres_gethostent.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_gethostent.html,v 1.9.18.2 2004/04/07 00:58:15 marka Exp $ -->
<!-- $Id: lwres_gethostent.html,v 1.9.18.3 2004/08/22 23:53:36 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_gethostent</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_gethostent</A
></H1
></A
>lwres_gethostent</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN21"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN22"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/netdb.h&gt;</PRE
@ -203,27 +203,27 @@ CLASS="PROGRAMLISTING"
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_name</TT
>h_name</CODE
></DT
><DD
><P
>The official (canonical) name of the host.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_aliases</TT
>h_aliases</CODE
></DT
><DD
><P
>A NULL-terminated array of alternate names (nicknames) for the host.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_addrtype</TT
>h_addrtype</CODE
></DT
><DD
><P
@ -239,18 +239,18 @@ CLASS="TYPE"
>.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_length</TT
>h_length</CODE
></DT
><DD
><P
>The length of the address in bytes.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_addr_list</TT
>h_addr_list</CODE
></DT
><DD
><P
@ -266,40 +266,40 @@ Host addresses are returned in network byte order.</P
></P
><P
>For backward compatibility with very old software,
<TT
<CODE
CLASS="CONSTANT"
>h_addr</TT
>h_addr</CODE
>
is the first address in
<TT
<CODE
CLASS="CONSTANT"
>h_addr_list.</TT
>h_addr_list.</CODE
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gethostent()</TT
>lwres_gethostent()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_sethostent()</TT
>lwres_sethostent()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_endhostent()</TT
>lwres_endhostent()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostent_r()</TT
>lwres_gethostent_r()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_sethostent_r()</TT
>lwres_sethostent_r()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_endhostent_r()</TT
>lwres_endhostent_r()</CODE
>
provide iteration over the known host entries on systems that
provide such functionality through facilities like
@ -311,33 +311,29 @@ or NIS. The lightweight resolver does not currently implement
these functions; it only provides them as stub functions that always
return failure.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gethostbyname()</TT
>lwres_gethostbyname()</CODE
> and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname2()</TT
>lwres_gethostbyname2()</CODE
> look up the hostname
<TT
<VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname()</TT
>lwres_gethostbyname()</CODE
> always looks for an IPv4
address while <TT
address while <CODE
CLASS="FUNCTION"
>lwres_gethostbyname2()</TT
>lwres_gethostbyname2()</CODE
> looks for an
address of protocol family <TT
address of protocol family <VAR
CLASS="PARAMETER"
><I
>af</I
></TT
>af</VAR
>: either
<SPAN
CLASS="TYPE"
@ -355,37 +351,31 @@ CLASS="TYPE"
CLASS="TYPE"
>NULL</SPAN
> is returned if the lookups by
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname()</TT
>lwres_gethostbyname()</CODE
> or
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname2()</TT
>lwres_gethostbyname2()</CODE
> fail.</P
><P
>Reverse lookups of addresses are performed by
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr()</TT
>lwres_gethostbyaddr()</CODE
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>addr</I
></TT
>addr</VAR
> is an address of length
<TT
<VAR
CLASS="PARAMETER"
><I
>len</I
></TT
>len</VAR
> bytes and protocol family
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
> &mdash; <SPAN
CLASS="TYPE"
>PF_INET</SPAN
@ -394,99 +384,81 @@ CLASS="TYPE"
CLASS="TYPE"
>PF_INET6</SPAN
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname_r()</TT
>lwres_gethostbyname_r()</CODE
> is a thread-safe function
for forward lookups. If an error occurs, an error code is returned in
<TT
<VAR
CLASS="PARAMETER"
><I
>*error</I
></TT
>*error</VAR
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>resbuf</I
></TT
>resbuf</VAR
> is a pointer to a <SPAN
CLASS="TYPE"
>struct
hostent</SPAN
> which is initialised by a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname_r()</TT
>lwres_gethostbyname_r()</CODE
> .
<TT
<VAR
CLASS="PARAMETER"
><I
>buf</I
></TT
>buf</VAR
> is a buffer of length
<TT
<VAR
CLASS="PARAMETER"
><I
>len</I
></TT
>len</VAR
> bytes which is used to store the
<TT
<CODE
CLASS="CONSTANT"
>h_name</TT
>, <TT
>h_name</CODE
>, <CODE
CLASS="CONSTANT"
>h_aliases</TT
>h_aliases</CODE
>, and
<TT
<CODE
CLASS="CONSTANT"
>h_addr_list</TT
>h_addr_list</CODE
> elements of the <SPAN
CLASS="TYPE"
>struct
hostent</SPAN
> returned in <TT
> returned in <VAR
CLASS="PARAMETER"
><I
>resbuf</I
></TT
>resbuf</VAR
>.
Successful calls to <TT
Successful calls to <CODE
CLASS="FUNCTION"
>lwres_gethostbyname_r()</TT
>lwres_gethostbyname_r()</CODE
>
return <TT
return <VAR
CLASS="PARAMETER"
><I
>resbuf</I
></TT
>resbuf</VAR
>,
which is a pointer to the <SPAN
CLASS="TYPE"
>struct hostent</SPAN
> it created.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr_r()</TT
>lwres_gethostbyaddr_r()</CODE
> is a thread-safe function
that performs a reverse lookup of address <TT
that performs a reverse lookup of address <VAR
CLASS="PARAMETER"
><I
>addr</I
></TT
>addr</VAR
>
which is <TT
which is <VAR
CLASS="PARAMETER"
><I
>len</I
></TT
>len</VAR
> bytes long and is of protocol
family <TT
family <VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
> &mdash; <SPAN
CLASS="TYPE"
>PF_INET</SPAN
@ -495,75 +467,63 @@ CLASS="TYPE"
CLASS="TYPE"
>PF_INET6</SPAN
>. If an error occurs, the error code is returned
in <TT
in <VAR
CLASS="PARAMETER"
><I
>*error</I
></TT
>*error</VAR
>. The other function parameters are
identical to those in <TT
identical to those in <CODE
CLASS="FUNCTION"
>lwres_gethostbyname_r()</TT
>lwres_gethostbyname_r()</CODE
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>resbuf</I
></TT
>resbuf</VAR
> is a pointer to a <SPAN
CLASS="TYPE"
>struct
hostent</SPAN
> which is initialised by a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr_r()</TT
>lwres_gethostbyaddr_r()</CODE
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>buf</I
></TT
>buf</VAR
> is a buffer of length
<TT
<VAR
CLASS="PARAMETER"
><I
>len</I
></TT
>len</VAR
> bytes which is used to store the
<TT
<CODE
CLASS="CONSTANT"
>h_name</TT
>, <TT
>h_name</CODE
>, <CODE
CLASS="CONSTANT"
>h_aliases</TT
>h_aliases</CODE
>, and
<TT
<CODE
CLASS="CONSTANT"
>h_addr_list</TT
>h_addr_list</CODE
> elements of the <SPAN
CLASS="TYPE"
>struct
hostent</SPAN
> returned in <TT
> returned in <VAR
CLASS="PARAMETER"
><I
>resbuf</I
></TT
>resbuf</VAR
>. Successful
calls to <TT
calls to <CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr_r()</TT
>lwres_gethostbyaddr_r()</CODE
> return
<TT
<VAR
CLASS="PARAMETER"
><I
>resbuf</I
></TT
>resbuf</VAR
>, which is a pointer to the
<TT
<CODE
CLASS="FUNCTION"
>struct hostent()</TT
>struct hostent()</CODE
> it created.</P
></DIV
><DIV
@ -575,22 +535,22 @@ NAME="AEN191"
>RETURN VALUES</H2
><P
>The functions
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname()</TT
>lwres_gethostbyname()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname2()</TT
>lwres_gethostbyname2()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr()</TT
>lwres_gethostbyaddr()</CODE
>,
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostent()</TT
>lwres_gethostent()</CODE
>
return NULL to indicate an error. In this case the global variable
<SPAN
@ -609,18 +569,18 @@ CLASS="FILENAME"
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>HOST_NOT_FOUND</TT
>HOST_NOT_FOUND</CODE
></DT
><DD
><P
>The host or address was not found.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>TRY_AGAIN</TT
>TRY_AGAIN</CODE
></DT
><DD
><P
@ -628,18 +588,18 @@ CLASS="CONSTANT"
Retrying the lookup may succeed.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NO_RECOVERY</TT
>NO_RECOVERY</CODE
></DT
><DD
><P
>A non-recoverable error occurred.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NO_DATA</TT
>NO_DATA</CODE
></DT
><DD
><P
@ -662,14 +622,14 @@ CLASS="REFENTRYTITLE"
>
translates these error codes to suitable error messages.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gethostent()</TT
>lwres_gethostent()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostent_r()</TT
>lwres_gethostent_r()</CODE
>
always return
<SPAN
@ -677,19 +637,17 @@ CLASS="TYPE"
>NULL</SPAN
>.</P
><P
>Successful calls to <TT
>Successful calls to <CODE
CLASS="FUNCTION"
>lwres_gethostbyname_r()</TT
>lwres_gethostbyname_r()</CODE
> and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr_r()</TT
>lwres_gethostbyaddr_r()</CODE
> return
<TT
<VAR
CLASS="PARAMETER"
><I
>resbuf</I
></TT
>resbuf</VAR
>, a pointer to the <SPAN
CLASS="TYPE"
>struct
@ -698,40 +656,36 @@ hostent</SPAN
<SPAN
CLASS="TYPE"
>NULL</SPAN
> if the lookups fail or if <TT
> if the lookups fail or if <VAR
CLASS="PARAMETER"
><I
>buf</I
></TT
>buf</VAR
>
was too small to hold the list of addresses and names referenced by
the <TT
the <CODE
CLASS="CONSTANT"
>h_name</TT
>, <TT
>h_name</CODE
>, <CODE
CLASS="CONSTANT"
>h_aliases</TT
>h_aliases</CODE
>, and
<TT
<CODE
CLASS="CONSTANT"
>h_addr_list</TT
>h_addr_list</CODE
> elements of the <SPAN
CLASS="TYPE"
>struct
hostent</SPAN
>. If <TT
>. If <VAR
CLASS="PARAMETER"
><I
>buf</I
></TT
>buf</VAR
> was too small, both
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname_r()</TT
>lwres_gethostbyname_r()</CODE
> and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr_r()</TT
>lwres_gethostbyaddr_r()</CODE
> set the global variable
<SPAN
CLASS="TYPE"
@ -781,34 +735,34 @@ NAME="AEN257"
><H2
>BUGS</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gethostbyname()</TT
>lwres_gethostbyname()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname2()</TT
>lwres_gethostbyname2()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr()</TT
>lwres_gethostbyaddr()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_endhostent()</TT
>lwres_endhostent()</CODE
>
are not thread safe; they return pointers to static data and
provide error codes through a global variable.
Thread-safe versions for name and address lookup are provided by
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyname_r()</TT
>lwres_gethostbyname_r()</CODE
>,
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gethostbyaddr_r()</TT
>lwres_gethostbyaddr_r()</CODE
>
respectively.</P
><P

166
lib/lwres/man/lwres_getipnode.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_getipnode.html,v 1.9.18.2 2004/04/07 00:58:16 marka Exp $ -->
<!-- $Id: lwres_getipnode.html,v 1.9.18.3 2004/08/22 23:53:36 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_getipnode</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_getipnode</A
></H1
></A
>lwres_getipnode</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN13"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN14"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/netdb.h&gt;</PRE
@ -131,27 +131,27 @@ CLASS="PROGRAMLISTING"
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_name</TT
>h_name</CODE
></DT
><DD
><P
>The official (canonical) name of the host.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_aliases</TT
>h_aliases</CODE
></DT
><DD
><P
>A NULL-terminated array of alternate names (nicknames) for the host.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_addrtype</TT
>h_addrtype</CODE
></DT
><DD
><P
@ -167,18 +167,18 @@ CLASS="TYPE"
>.&#13;</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_length</TT
>h_length</CODE
></DT
><DD
><P
>The length of the address in bytes.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>h_addr_list</TT
>h_addr_list</CODE
></DT
><DD
><P
@ -194,32 +194,26 @@ Host addresses are returned in network byte order.</P
></DIV
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getipnodebyname()</TT
>lwres_getipnodebyname()</CODE
>
looks up addresses of protocol family
<TT
<VAR
CLASS="PARAMETER"
><I
>af</I
></TT
>af</VAR
>
for the hostname
<TT
<VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
>.
The
<TT
<VAR
CLASS="PARAMETER"
><I
>flags</I
></TT
>flags</VAR
>
parameter contains ORed flag bits to
specify the types of addresses that are searched
@ -231,44 +225,40 @@ The flag bits are:
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>AI_V4MAPPED</TT
>AI_V4MAPPED</CODE
></DT
><DD
><P
>This is used with an
<TT
<VAR
CLASS="PARAMETER"
><I
>af</I
></TT
>af</VAR
>
of AF_INET6, and causes IPv4 addresses to be returned as IPv4-mapped
IPv6 addresses.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>AI_ALL</TT
>AI_ALL</CODE
></DT
><DD
><P
>This is used with an
<TT
<VAR
CLASS="PARAMETER"
><I
>af</I
></TT
>af</VAR
>
of AF_INET6, and causes all known addresses (IPv6 and IPv4) to be returned.
If AI_V4MAPPED is also set, the IPv4 addresses are return as mapped
IPv6 addresses.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>AI_ADDRCONFIG</TT
>AI_ADDRCONFIG</CODE
></DT
><DD
><P
@ -277,21 +267,21 @@ interface of that type. This is not currently implemented
in the BIND 9 lightweight resolver, and the flag is ignored.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>AI_DEFAULT</TT
>AI_DEFAULT</CODE
></DT
><DD
><P
>This default sets the
<TT
<CODE
CLASS="CONSTANT"
>AI_V4MAPPED</TT
>AI_V4MAPPED</CODE
>
and
<TT
<CODE
CLASS="CONSTANT"
>AI_ADDRCONFIG</TT
>AI_ADDRCONFIG</CODE
>
flag bits.</P
></DD
@ -299,31 +289,25 @@ flag bits.</P
></DIV
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getipnodebyaddr()</TT
>lwres_getipnodebyaddr()</CODE
>
performs a reverse lookup
of address
<TT
<VAR
CLASS="PARAMETER"
><I
>src</I
></TT
>src</VAR
>
which is
<TT
<VAR
CLASS="PARAMETER"
><I
>len</I
></TT
>len</VAR
>
bytes long.
<TT
<VAR
CLASS="PARAMETER"
><I
>af</I
></TT
>af</VAR
>
denotes the protocol family, typically
<SPAN
@ -336,9 +320,9 @@ CLASS="TYPE"
>PF_INET6</SPAN
>.&#13;</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_freehostent()</TT
>lwres_freehostent()</CODE
>
releases all the memory associated with
the
@ -347,27 +331,25 @@ CLASS="TYPE"
>struct hostent</SPAN
>
pointer
<TT
<VAR
CLASS="PARAMETER"
><I
>he</I
></TT
>he</VAR
>.
Any memory allocated for the
<TT
<CODE
CLASS="CONSTANT"
>h_name</TT
>h_name</CODE
>,
<TT
<CODE
CLASS="CONSTANT"
>h_addr_list</TT
>h_addr_list</CODE
>
and
<TT
<CODE
CLASS="CONSTANT"
>h_aliases</TT
>h_aliases</CODE
>
is freed, as is the memory for the
<SPAN
@ -385,21 +367,19 @@ NAME="AEN116"
>RETURN VALUES</H2
><P
>If an error occurs,
<TT
<CODE
CLASS="FUNCTION"
>lwres_getipnodebyname()</TT
>lwres_getipnodebyname()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_getipnodebyaddr()</TT
>lwres_getipnodebyaddr()</CODE
>
set
<TT
<VAR
CLASS="PARAMETER"
><I
>*error_num</I
></TT
>*error_num</VAR
>
to an appropriate error code and the function returns a
<SPAN
@ -418,18 +398,18 @@ CLASS="FILENAME"
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>HOST_NOT_FOUND</TT
>HOST_NOT_FOUND</CODE
></DT
><DD
><P
>No such host is known.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NO_ADDRESS</TT
>NO_ADDRESS</CODE
></DT
><DD
><P
@ -438,9 +418,9 @@ available. Another type of request to the name server for the
domain might return an answer.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>TRY_AGAIN</TT
>TRY_AGAIN</CODE
></DT
><DD
><P
@ -449,9 +429,9 @@ failure of a server to respond. The request may succeed if
retried.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NO_RECOVERY</TT
>NO_RECOVERY</CODE
></DT
><DD
><P

98
lib/lwres/man/lwres_getnameinfo.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_getnameinfo.html,v 1.6.18.2 2004/04/07 00:58:16 marka Exp $ -->
<!-- $Id: lwres_getnameinfo.html,v 1.6.18.3 2004/08/22 23:53:37 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_getnameinfo</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_getnameinfo</A
></H1
></A
>lwres_getnameinfo</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN11"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN12"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/netdb.h&gt;</PRE
@ -89,70 +89,54 @@ CLASS="REFENTRYTITLE"
>getnameinfo</SPAN
>(3)</SPAN
> function defined in RFC2133.
<TT
<CODE
CLASS="FUNCTION"
>lwres_getnameinfo()</TT
>lwres_getnameinfo()</CODE
> returns the hostname for the
<SPAN
CLASS="TYPE"
>struct sockaddr</SPAN
> <TT
> <VAR
CLASS="PARAMETER"
><I
>sa</I
></TT
>sa</VAR
> which is
<TT
<VAR
CLASS="PARAMETER"
><I
>salen</I
></TT
>salen</VAR
> bytes long. The hostname is of length
<TT
<VAR
CLASS="PARAMETER"
><I
>hostlen</I
></TT
>hostlen</VAR
> and is returned via
<TT
<VAR
CLASS="PARAMETER"
><I
>*host.</I
></TT
>*host.</VAR
> The maximum length of the hostname is
1025 bytes: <TT
1025 bytes: <CODE
CLASS="CONSTANT"
>NI_MAXHOST</TT
>NI_MAXHOST</CODE
>.</P
><P
> The name of the service associated with the port number in
<TT
<VAR
CLASS="PARAMETER"
><I
>sa</I
></TT
> is returned in <TT
>sa</VAR
> is returned in <VAR
CLASS="PARAMETER"
><I
>*serv.</I
></TT
>*serv.</VAR
>
It is <TT
It is <VAR
CLASS="PARAMETER"
><I
>servlen</I
></TT
>servlen</VAR
> bytes long. The maximum length
of the service name is <TT
of the service name is <CODE
CLASS="CONSTANT"
>NI_MAXSERV</TT
>NI_MAXSERV</CODE
> - 32 bytes.</P
><P
> The <TT
> The <VAR
CLASS="PARAMETER"
><I
>flags</I
></TT
>flags</VAR
> argument sets the following
bits:
<P
@ -161,9 +145,9 @@ bits:
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>NI_NOFQDN</TT
>NI_NOFQDN</CODE
></DT
><DD
><P
@ -171,9 +155,9 @@ CLASS="CONSTANT"
The local part of the fully qualified domain name is returned instead.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NI_NUMERICHOST</TT
>NI_NUMERICHOST</CODE
></DT
><DD
><P
@ -181,9 +165,9 @@ CLASS="CONSTANT"
instead of a host name.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NI_NAMEREQD</TT
>NI_NAMEREQD</CODE
></DT
><DD
><P
@ -193,18 +177,18 @@ If the hostname is not found and the flag is not set, the
address is returned in numeric form.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NI_NUMERICSERV</TT
>NI_NUMERICSERV</CODE
></DT
><DD
><P
>The service name is returned as a digit string representing the port number.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>NI_DGRAM</TT
>NI_DGRAM</CODE
></DT
><DD
><P
@ -226,9 +210,9 @@ NAME="AEN70"
><H2
>RETURN VALUES</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getnameinfo()</TT
>lwres_getnameinfo()</CODE
>
returns 0 on success or a non-zero error code if an error occurs.</P
></DIV

148
lib/lwres/man/lwres_getrrsetbyname.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_getrrsetbyname.html,v 1.6.18.2 2004/04/07 00:58:16 marka Exp $ -->
<!-- $Id: lwres_getrrsetbyname.html,v 1.6.18.3 2004/08/22 23:53:37 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_getrrsetbyname</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_getrrsetbyname</A
></H1
></A
>lwres_getrrsetbyname</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN12"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN13"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/netdb.h&gt;</PRE
@ -111,60 +111,48 @@ NAME="AEN29"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getrrsetbyname()</TT
>lwres_getrrsetbyname()</CODE
>
gets a set of resource records associated with a
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>class</I
></TT
>class</VAR
>,
and
<TT
<VAR
CLASS="PARAMETER"
><I
>type</I
></TT
>type</VAR
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>hostname</I
></TT
>hostname</VAR
>
is
a pointer a to null-terminated string. The
<TT
<VAR
CLASS="PARAMETER"
><I
>flags</I
></TT
>flags</VAR
>
field is currently unused and must be zero.</P
><P
>After a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getrrsetbyname()</TT
>lwres_getrrsetbyname()</CODE
>,
<TT
<VAR
CLASS="PARAMETER"
><I
>*res</I
></TT
>*res</VAR
>
is a pointer to an
<SPAN
@ -184,84 +172,82 @@ CLASS="TYPE"
structures containing SIG resource records
associated with those records.
The members
<TT
<CODE
CLASS="CONSTANT"
>rri_rdclass</TT
>rri_rdclass</CODE
>
and
<TT
<CODE
CLASS="CONSTANT"
>rri_rdtype</TT
>rri_rdtype</CODE
>
are copied from the parameters.
<TT
<CODE
CLASS="CONSTANT"
>rri_ttl</TT
>rri_ttl</CODE
>
and
<TT
<CODE
CLASS="CONSTANT"
>rri_name</TT
>rri_name</CODE
>
are properties of the obtained rrset.
The resource records contained in
<TT
<CODE
CLASS="CONSTANT"
>rri_rdatas</TT
>rri_rdatas</CODE
>
and
<TT
<CODE
CLASS="CONSTANT"
>rri_sigs</TT
>rri_sigs</CODE
>
are in uncompressed DNS wire format.
Properties of the rdataset are represented in the
<TT
<CODE
CLASS="CONSTANT"
>rri_flags</TT
>rri_flags</CODE
>
bitfield. If the RRSET_VALIDATED bit is set, the data has been DNSSEC
validated and the signatures verified. </P
><P
>All of the information returned by
<TT
<CODE
CLASS="FUNCTION"
>lwres_getrrsetbyname()</TT
>lwres_getrrsetbyname()</CODE
>
is dynamically allocated: the
<TT
<CODE
CLASS="CONSTANT"
>rrsetinfo</TT
>rrsetinfo</CODE
>
and
<TT
<CODE
CLASS="CONSTANT"
>rdatainfo</TT
>rdatainfo</CODE
>
structures,
and the canonical host name strings pointed to by the
<TT
<CODE
CLASS="CONSTANT"
>rrsetinfo</TT
>rrsetinfo</CODE
>structure.
Memory allocated for the dynamically allocated structures created by
a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getrrsetbyname()</TT
>lwres_getrrsetbyname()</CODE
>
is released by
<TT
<CODE
CLASS="FUNCTION"
>lwres_freerrset()</TT
>lwres_freerrset()</CODE
>.
<TT
<VAR
CLASS="PARAMETER"
><I
>rrset</I
></TT
>rrset</VAR
>
is a pointer to a
<SPAN
@ -269,9 +255,9 @@ CLASS="TYPE"
>struct rrset</SPAN
>
created by a call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getrrsetbyname()</TT
>lwres_getrrsetbyname()</CODE
>.&#13;</P
><P
></P
@ -284,9 +270,9 @@ NAME="AEN62"
><H2
>RETURN VALUES</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getrrsetbyname()</TT
>lwres_getrrsetbyname()</CODE
>
returns zero on success, and one of the following error
codes if an error occurred:
@ -296,54 +282,54 @@ codes if an error occurred:
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>ERRSET_NONAME</TT
>ERRSET_NONAME</CODE
></DT
><DD
><P
>the name does not exist</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ERRSET_NODATA</TT
>ERRSET_NODATA</CODE
></DT
><DD
><P
>the name exists, but does not have data of the desired type</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ERRSET_NOMEMORY</TT
>ERRSET_NOMEMORY</CODE
></DT
><DD
><P
>memory could not be allocated</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ERRSET_INVAL</TT
>ERRSET_INVAL</CODE
></DT
><DD
><P
>a parameter is invalid</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>ERRSET_FAIL</TT
>ERRSET_FAIL</CODE
></DT
><DD
><P
>other failure</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
></TT
></CODE
></DT
><DD
><P

120
lib/lwres/man/lwres_gnba.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_gnba.html,v 1.7.18.2 2004/04/07 00:58:17 marka Exp $ -->
<!-- $Id: lwres_gnba.html,v 1.7.18.3 2004/08/22 23:53:37 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_gnba</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_gnba</A
></H1
></A
>lwres_gnba</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN16"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN17"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwres.h&gt;</PRE
@ -171,41 +171,41 @@ typedef struct {
} lwres_gnbaresponse_t;</PRE
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gnbarequest_render()</TT
>lwres_gnbarequest_render()</CODE
>
uses resolver context
<TT
<VAR
CLASS="VARNAME"
>ctx</TT
>ctx</VAR
>
to convert getnamebyaddr request structure
<TT
<VAR
CLASS="VARNAME"
>req</TT
>req</VAR
>
to canonical format.
The packet header structure
<TT
<VAR
CLASS="VARNAME"
>pkt</TT
>pkt</VAR
>
is initialised and transferred to
buffer
<TT
<VAR
CLASS="VARNAME"
>b</TT
>b</VAR
>.
The contents of
<TT
<VAR
CLASS="VARNAME"
>*req</TT
>*req</VAR
>
are then appended to the buffer in canonical format.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbaresponse_render()</TT
>lwres_gnbaresponse_render()</CODE
>
performs the same task, except it converts a getnamebyaddr response structure
<SPAN
@ -214,19 +214,19 @@ CLASS="TYPE"
>
to the lightweight resolver's canonical format.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gnbarequest_parse()</TT
>lwres_gnbarequest_parse()</CODE
>
uses context
<TT
<VAR
CLASS="VARNAME"
>ctx</TT
>ctx</VAR
>
to convert the contents of packet
<TT
<VAR
CLASS="VARNAME"
>pkt</TT
>pkt</VAR
>
to a
<SPAN
@ -235,9 +235,9 @@ CLASS="TYPE"
>
structure.
Buffer
<TT
<VAR
CLASS="VARNAME"
>b</TT
>b</VAR
>
provides space to be used for storing this structure.
When the function succeeds, the resulting
@ -246,18 +246,18 @@ CLASS="TYPE"
>lwres_gnbarequest_t</SPAN
>
is made available through
<TT
<VAR
CLASS="VARNAME"
>*structp</TT
>*structp</VAR
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbaresponse_parse()</TT
>lwres_gnbaresponse_parse()</CODE
>
offers the same semantics as
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbarequest_parse()</TT
>lwres_gnbarequest_parse()</CODE
>
except it yields a
<SPAN
@ -266,19 +266,19 @@ CLASS="TYPE"
>
structure.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_gnbaresponse_free()</TT
>lwres_gnbaresponse_free()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbarequest_free()</TT
>lwres_gnbarequest_free()</CODE
>
release the memory in resolver context
<TT
<VAR
CLASS="VARNAME"
>ctx</TT
>ctx</VAR
>
that was allocated to the
<SPAN
@ -291,9 +291,9 @@ CLASS="TYPE"
>lwres_gnbarequest_t</SPAN
>
structures referenced via
<TT
<VAR
CLASS="VARNAME"
>structp</TT
>structp</VAR
>.
Any memory associated with ancillary buffers and strings for those
structures is also discarded.</P
@ -307,22 +307,22 @@ NAME="AEN97"
>RETURN VALUES</H2
><P
>The getnamebyaddr opcode functions
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbarequest_render()</TT
>lwres_gnbarequest_render()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbaresponse_render()</TT
>lwres_gnbaresponse_render()</CODE
>
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbarequest_parse()</TT
>lwres_gnbarequest_parse()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbaresponse_parse()</TT
>lwres_gnbaresponse_parse()</CODE
>
all return
<SPAN
@ -341,9 +341,9 @@ CLASS="ERRORCODE"
>LWRES_R_UNEXPECTEDEND</SPAN
>
is returned if the available space in the buffer
<TT
<VAR
CLASS="VARNAME"
>b</TT
>b</VAR
>
is too small to accommodate the packet header or the
<SPAN
@ -356,14 +356,14 @@ CLASS="TYPE"
>lwres_gnbaresponse_t</SPAN
>
structures.
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbarequest_parse()</TT
>lwres_gnbarequest_parse()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_gnbaresponse_parse()</TT
>lwres_gnbaresponse_parse()</CODE
>
will return
<SPAN
@ -377,11 +377,9 @@ CLASS="ERRORCODE"
>LWRES_R_FAILURE</SPAN
>
if
<TT
<CODE
CLASS="STRUCTFIELD"
><I
>pktflags</I
></TT
>pktflags</CODE
>
in the packet header structure
<SPAN

50
lib/lwres/man/lwres_hstrerror.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_hstrerror.html,v 1.6.18.2 2004/04/07 00:58:17 marka Exp $ -->
<!-- $Id: lwres_hstrerror.html,v 1.6.18.3 2004/08/22 23:53:38 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_hstrerror</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_hstrerror</A
></H1
></A
>lwres_hstrerror</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN12"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN13"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/netdb.h&gt;</PRE
@ -90,37 +90,33 @@ NAME="AEN23"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_herror()</TT
>lwres_herror()</CODE
> prints the string
<TT
<VAR
CLASS="PARAMETER"
><I
>s</I
></TT
>s</VAR
> on <SPAN
CLASS="TYPE"
>stderr</SPAN
> followed by the string
generated by <TT
generated by <CODE
CLASS="FUNCTION"
>lwres_hstrerror()</TT
>lwres_hstrerror()</CODE
> for the error code
stored in the global variable <TT
stored in the global variable <CODE
CLASS="CONSTANT"
>lwres_h_errno</TT
>lwres_h_errno</CODE
>.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_hstrerror()</TT
>lwres_hstrerror()</CODE
> returns an appropriate string
for the error code gievn by <TT
for the error code gievn by <VAR
CLASS="PARAMETER"
><I
>err</I
></TT
>err</VAR
>. The values of
the error codes and messages are as follows:
@ -205,14 +201,14 @@ NAME="AEN65"
CLASS="ERRORNAME"
>Unknown resolver error</SPAN
> is returned by
<TT
<CODE
CLASS="FUNCTION"
>lwres_hstrerror()</TT
>lwres_hstrerror()</CODE
>
when the value of
<TT
<CODE
CLASS="CONSTANT"
>lwres_h_errno</TT
>lwres_h_errno</CODE
>
is not a valid error code.</P
></DIV

62
lib/lwres/man/lwres_inetntop.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_inetntop.html,v 1.6.18.2 2004/04/07 00:58:17 marka Exp $ -->
<!-- $Id: lwres_inetntop.html,v 1.6.18.3 2004/08/22 23:53:38 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_inetntop</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_inetntop</A
></H1
></A
>lwres_inetntop</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN11"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN12"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/net.h&gt;</PRE
@ -82,37 +82,29 @@ NAME="AEN21"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_net_ntop()</TT
>lwres_net_ntop()</CODE
> converts an IP address of
protocol family <TT
protocol family <VAR
CLASS="PARAMETER"
><I
>af</I
></TT
>af</VAR
> &mdash; IPv4 or IPv6 &mdash;
at location <TT
at location <VAR
CLASS="PARAMETER"
><I
>src</I
></TT
>src</VAR
> from network format to its
conventional representation as a string. For IPv4 addresses, that
string would be a dotted-decimal. An IPv6 address would be
represented in colon notation as described in RFC1884.</P
><P
>The generated string is copied to <TT
>The generated string is copied to <VAR
CLASS="PARAMETER"
><I
>dst</I
></TT
>dst</VAR
> provided
<TT
<VAR
CLASS="PARAMETER"
><I
>size</I
></TT
>size</VAR
> indicates it is long enough to store the
ASCII representation of the address.</P
></DIV
@ -124,33 +116,29 @@ NAME="AEN30"
><H2
>RETURN VALUES</H2
><P
>If successful, the function returns <TT
>If successful, the function returns <VAR
CLASS="PARAMETER"
><I
>dst</I
></TT
>dst</VAR
>:
a pointer to a string containing the presentation format of the
address. <TT
address. <CODE
CLASS="FUNCTION"
>lwres_net_ntop()</TT
>lwres_net_ntop()</CODE
> returns
<SPAN
CLASS="TYPE"
>NULL</SPAN
> and sets the global variable
<TT
<CODE
CLASS="CONSTANT"
>errno</TT
>errno</CODE
> to <SPAN
CLASS="ERRORCODE"
>EAFNOSUPPORT</SPAN
> if
the protocol family given in <TT
the protocol family given in <VAR
CLASS="PARAMETER"
><I
>af</I
></TT
>af</VAR
> is not
supported.</P
></DIV

142
lib/lwres/man/lwres_noop.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_noop.html,v 1.8.18.2 2004/04/07 00:58:17 marka Exp $ -->
<!-- $Id: lwres_noop.html,v 1.8.18.3 2004/08/22 23:53:38 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_noop</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_noop</A
></H1
></A
>lwres_noop</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN16"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN17"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwres.h&gt;</PRE
@ -176,43 +176,33 @@ Although the structures have different types, they are identical.
This is because the no-op opcode simply echos whatever data was sent:
the response is therefore identical to the request.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_nooprequest_render()</TT
>lwres_nooprequest_render()</CODE
> uses resolver
context <TT
context <VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
> to convert no-op request structure
<TT
<VAR
CLASS="PARAMETER"
><I
>req</I
></TT
>req</VAR
> to canonical format. The packet header
structure <TT
structure <VAR
CLASS="PARAMETER"
><I
>pkt</I
></TT
>pkt</VAR
> is initialised and transferred to
buffer <TT
buffer <VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>. The contents of
<TT
<VAR
CLASS="PARAMETER"
><I
>*req</I
></TT
>*req</VAR
> are then appended to the buffer in
canonical format. <TT
canonical format. <CODE
CLASS="FUNCTION"
>lwres_noopresponse_render()</TT
>lwres_noopresponse_render()</CODE
>
performs the same task, except it converts a no-op response structure
<SPAN
@ -221,68 +211,58 @@ CLASS="TYPE"
> to the lightweight resolver's
canonical format.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_nooprequest_parse()</TT
>lwres_nooprequest_parse()</CODE
> uses context
<TT
<VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
> to convert the contents of packet
<TT
<VAR
CLASS="PARAMETER"
><I
>pkt</I
></TT
>pkt</VAR
> to a <SPAN
CLASS="TYPE"
>lwres_nooprequest_t</SPAN
>
structure. Buffer <TT
structure. Buffer <VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
> provides space to be used
for storing this structure. When the function succeeds, the resulting
<SPAN
CLASS="TYPE"
>lwres_nooprequest_t</SPAN
> is made available through
<TT
<VAR
CLASS="PARAMETER"
><I
>*structp</I
></TT
>*structp</VAR
>.
<TT
<CODE
CLASS="FUNCTION"
>lwres_noopresponse_parse()</TT
>lwres_noopresponse_parse()</CODE
> offers the same
semantics as <TT
semantics as <CODE
CLASS="FUNCTION"
>lwres_nooprequest_parse()</TT
>lwres_nooprequest_parse()</CODE
> except it
yields a <SPAN
CLASS="TYPE"
>lwres_noopresponse_t</SPAN
> structure.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_noopresponse_free()</TT
>lwres_noopresponse_free()</CODE
> and
<TT
<CODE
CLASS="FUNCTION"
>lwres_nooprequest_free()</TT
>lwres_nooprequest_free()</CODE
> release the memory in
resolver context <TT
resolver context <VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
> that was allocated to the
<SPAN
CLASS="TYPE"
@ -291,11 +271,9 @@ CLASS="TYPE"
CLASS="TYPE"
>lwres_nooprequest_t</SPAN
>
structures referenced via <TT
structures referenced via <VAR
CLASS="PARAMETER"
><I
>structp</I
></TT
>structp</VAR
>.</P
></DIV
><DIV
@ -307,23 +285,23 @@ NAME="AEN95"
>RETURN VALUES</H2
><P
>The no-op opcode functions
<TT
<CODE
CLASS="FUNCTION"
>lwres_nooprequest_render()</TT
>lwres_nooprequest_render()</CODE
>,
<TT
<CODE
CLASS="FUNCTION"
>lwres_noopresponse_render()</TT
>lwres_noopresponse_render()</CODE
>
<TT
<CODE
CLASS="FUNCTION"
>lwres_nooprequest_parse()</TT
>lwres_nooprequest_parse()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_noopresponse_parse()</TT
>lwres_noopresponse_parse()</CODE
>
all return
<SPAN
@ -342,11 +320,9 @@ CLASS="ERRORCODE"
>LWRES_R_UNEXPECTEDEND</SPAN
>
is returned if the available space in the buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>
is too small to accommodate the packet header or the
<SPAN
@ -359,14 +335,14 @@ CLASS="TYPE"
>lwres_noopresponse_t</SPAN
>
structures.
<TT
<CODE
CLASS="FUNCTION"
>lwres_nooprequest_parse()</TT
>lwres_nooprequest_parse()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_noopresponse_parse()</TT
>lwres_noopresponse_parse()</CODE
>
will return
<SPAN
@ -380,9 +356,9 @@ CLASS="ERRORCODE"
>LWRES_R_FAILURE</SPAN
>
if
<TT
<CODE
CLASS="CONSTANT"
>pktflags</TT
>pktflags</CODE
>
in the packet header structure
<SPAN

120
lib/lwres/man/lwres_packet.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_packet.html,v 1.9.18.2 2004/04/07 00:58:17 marka Exp $ -->
<!-- $Id: lwres_packet.html,v 1.9.18.3 2004/08/22 23:53:38 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_packet</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_packet</A
></H1
></A
>lwres_packet</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN12"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN13"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwpacket.h&gt;</PRE
@ -125,9 +125,9 @@ struct lwres_lwpacket {
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>length</TT
>length</CODE
></DT
><DD
><P
@ -136,9 +136,9 @@ This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
calls.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>version</TT
>version</CODE
></DT
><DD
><P
@ -152,9 +152,9 @@ This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
calls.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>pktflags</TT
>pktflags</CODE
></DT
><DD
><P
@ -166,9 +166,9 @@ LWRES_LWPACKETFLAG_RESPONSE bit, which is set by the library in the
lwres_gabn_*() and lwres_gnba_*() calls.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>serial</TT
>serial</CODE
></DT
><DD
><P
@ -179,9 +179,9 @@ may be dropped.
This field must be set by the application.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>opcode</TT
>opcode</CODE
></DT
><DD
><P
@ -193,9 +193,9 @@ This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
calls.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>result</TT
>result</CODE
></DT
><DD
><P
@ -206,9 +206,9 @@ This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
calls.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>recvlength</TT
>recvlength</CODE
></DT
><DD
><P
@ -218,9 +218,9 @@ is too large for replies.
This field is supplied by the application.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>authtype</TT
>authtype</CODE
></DT
><DD
><P
@ -230,9 +230,9 @@ and types between 0x0000 and 0x0fff are reserved for library use.
Currently these are not used and must be zero.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>authlen</TT
>authlen</CODE
></DT
><DD
><P
@ -250,9 +250,9 @@ Since packet authentication is currently not used, this must be zero.</P
CLASS="VARIABLELIST"
><DL
><DT
><TT
><CODE
CLASS="CONSTANT"
>NOOP</TT
>NOOP</CODE
></DT
><DD
><P
@ -260,9 +260,9 @@ CLASS="CONSTANT"
The lwres_noop_*() functions should be used for this type.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>GETADDRSBYNAME</TT
>GETADDRSBYNAME</CODE
></DT
><DD
><P
@ -270,9 +270,9 @@ CLASS="CONSTANT"
The lwres_gabn_*() functions should be used for this type.</P
></DD
><DT
><TT
><CODE
CLASS="CONSTANT"
>GETNAMEBYADDR</TT
>GETNAMEBYADDR</CODE
></DT
><DD
><P
@ -283,50 +283,40 @@ The lwres_gnba_*() functions should be used for this type.</P
></DIV
></P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_lwpacket_renderheader()</TT
>lwres_lwpacket_renderheader()</CODE
> transfers the
contents of lightweight resolver packet structure
<SPAN
CLASS="TYPE"
>lwres_lwpacket_t</SPAN
> <TT
> <VAR
CLASS="PARAMETER"
><I
>*pkt</I
></TT
>*pkt</VAR
> in network
byte order to the lightweight resolver buffer,
<TT
<VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
>.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_lwpacket_parseheader()</TT
>lwres_lwpacket_parseheader()</CODE
> performs the
converse operation. It transfers data in network byte order from
buffer <TT
buffer <VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
> to resolver packet
<TT
<VAR
CLASS="PARAMETER"
><I
>*pkt</I
></TT
>*pkt</VAR
>. The contents of the buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
> should correspond to a
<SPAN
CLASS="TYPE"
@ -342,29 +332,25 @@ NAME="AEN107"
>RETURN VALUES</H2
><P
> Successful calls to
<TT
<CODE
CLASS="FUNCTION"
>lwres_lwpacket_renderheader()</TT
>lwres_lwpacket_renderheader()</CODE
> and
<TT
<CODE
CLASS="FUNCTION"
>lwres_lwpacket_parseheader()</TT
>lwres_lwpacket_parseheader()</CODE
> return
<SPAN
CLASS="ERRORCODE"
>LWRES_R_SUCCESS</SPAN
>. If there is insufficient
space to copy data between the buffer <TT
space to copy data between the buffer <VAR
CLASS="PARAMETER"
><I
>*b</I
></TT
>*b</VAR
> and
lightweight resolver packet <TT
lightweight resolver packet <VAR
CLASS="PARAMETER"
><I
>*pkt</I
></TT
>*pkt</VAR
> both functions
return <SPAN
CLASS="ERRORCODE"

166
lib/lwres/man/lwres_resutil.html
View file

@ -15,16 +15,16 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
<!-- $Id: lwres_resutil.html,v 1.9.18.2 2004/04/07 00:58:17 marka Exp $ -->
<!-- $Id: lwres_resutil.html,v 1.9.18.3 2004/08/22 23:53:39 marka Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>lwres_resutil</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -35,8 +35,8 @@ ALINK="#0000FF"
><H1
><A
NAME="AEN1"
>lwres_resutil</A
></H1
></A
>lwres_resutil</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -54,11 +54,11 @@ NAME="AEN14"
>Synopsis</H2
><DIV
CLASS="FUNCSYNOPSIS"
><P
></P
><A
NAME="AEN15"
></A
><P
></P
><PRE
CLASS="FUNCSYNOPSISINFO"
>#include &lt;lwres/lwres.h&gt;</PRE
@ -106,32 +106,26 @@ NAME="AEN43"
><H2
>DESCRIPTION</H2
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_string_parse()</TT
>lwres_string_parse()</CODE
> retrieves a DNS-encoded
string starting the current pointer of lightweight resolver buffer
<TT
<VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>: i.e. <TT
>b</VAR
>: i.e. <CODE
CLASS="CONSTANT"
>b-&gt;current</TT
>b-&gt;current</CODE
>.
When the function returns, the address of the first byte of the
encoded string is returned via <TT
encoded string is returned via <VAR
CLASS="PARAMETER"
><I
>*c</I
></TT
>*c</VAR
> and the
length of that string is given by <TT
length of that string is given by <VAR
CLASS="PARAMETER"
><I
>*len</I
></TT
>*len</VAR
>. The
buffer's current pointer is advanced to point at the character
following the string length, the encoded string, and the trailing
@ -140,45 +134,43 @@ CLASS="TYPE"
>NULL</SPAN
> character.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_addr_parse()</TT
>lwres_addr_parse()</CODE
> extracts an address from the
buffer <TT
buffer <VAR
CLASS="PARAMETER"
><I
>b</I
></TT
>b</VAR
>. The buffer's current pointer
<TT
<CODE
CLASS="CONSTANT"
>b-&gt;current</TT
>b-&gt;current</CODE
> is presumed to point at an encoded
address: the address preceded by a 32-bit protocol family identifier
and a 16-bit length field. The encoded address is copied to
<TT
<CODE
CLASS="CONSTANT"
>addr-&gt;address</TT
>addr-&gt;address</CODE
> and
<TT
<CODE
CLASS="CONSTANT"
>addr-&gt;length</TT
>addr-&gt;length</CODE
> indicates the size in bytes of
the address that was copied. <TT
the address that was copied. <CODE
CLASS="CONSTANT"
>b-&gt;current</TT
>b-&gt;current</CODE
> is
advanced to point at the next byte of available data in the buffer
following the encoded address.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getaddrsbyname()</TT
>lwres_getaddrsbyname()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_getnamebyaddr()</TT
>lwres_getnamebyaddr()</CODE
>
use the
<SPAN
@ -213,27 +205,21 @@ CLASS="REFENTRYTITLE"
functions.</P
><P
>The lightweight resolver uses
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrsbyname()</TT
>lwres_getaddrsbyname()</CODE
> to perform foward lookups.
Hostname <TT
Hostname <VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
> is looked up using the resolver
context <TT
context <VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
> for memory allocation.
<TT
<VAR
CLASS="PARAMETER"
><I
>addrtypes</I
></TT
>addrtypes</VAR
> is a bitmask indicating which type of
addresses are to be looked up. Current values for this bitmask are
<SPAN
@ -244,29 +230,23 @@ CLASS="TYPE"
CLASS="TYPE"
>LWRES_ADDRTYPE_V6</SPAN
> for IPv6 addresses. Results of the
lookup are returned in <TT
lookup are returned in <VAR
CLASS="PARAMETER"
><I
>*structp</I
></TT
>*structp</VAR
>.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getnamebyaddr()</TT
>lwres_getnamebyaddr()</CODE
> performs reverse lookups.
Resolver context <TT
Resolver context <VAR
CLASS="PARAMETER"
><I
>ctx</I
></TT
>ctx</VAR
> is used for memory
allocation. The address type is indicated by
<TT
<VAR
CLASS="PARAMETER"
><I
>addrtype</I
></TT
>addrtype</VAR
>: <SPAN
CLASS="TYPE"
>LWRES_ADDRTYPE_V4</SPAN
@ -275,23 +255,17 @@ CLASS="TYPE"
CLASS="TYPE"
>LWRES_ADDRTYPE_V6</SPAN
>. The address to be looked up is given
by <TT
by <VAR
CLASS="PARAMETER"
><I
>addr</I
></TT
>addr</VAR
> and its length is
<TT
<VAR
CLASS="PARAMETER"
><I
>addrlen</I
></TT
>addrlen</VAR
> bytes. The result of the function call
is made available through <TT
is made available through <VAR
CLASS="PARAMETER"
><I
>*structp</I
></TT
>*structp</VAR
>.</P
></DIV
><DIV
@ -303,14 +277,14 @@ NAME="AEN84"
>RETURN VALUES</H2
><P
>Successful calls to
<TT
<CODE
CLASS="FUNCTION"
>lwres_string_parse()</TT
>lwres_string_parse()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_addr_parse()</TT
>lwres_addr_parse()</CODE
>
return
<SPAN
@ -330,9 +304,9 @@ CLASS="ERRORCODE"
if the buffer has less space than expected for the components of the
encoded string or address.</P
><P
><TT
><CODE
CLASS="FUNCTION"
>lwres_getaddrsbyname()</TT
>lwres_getaddrsbyname()</CODE
>
returns
<SPAN
@ -345,11 +319,9 @@ CLASS="ERRORCODE"
>LWRES_R_NOTFOUND</SPAN
>
if the hostname
<TT
<VAR
CLASS="PARAMETER"
><I
>name</I
></TT
>name</VAR
>
could not be found.</P
><P
@ -358,20 +330,20 @@ CLASS="ERRORCODE"
>LWRES_R_SUCCESS</SPAN
>
is returned by a successful call to
<TT
<CODE
CLASS="FUNCTION"
>lwres_getnamebyaddr()</TT
>lwres_getnamebyaddr()</CODE
>.</P
><P
>Both
<TT
<CODE
CLASS="FUNCTION"
>lwres_getaddrsbyname()</TT
>lwres_getaddrsbyname()</CODE
>
and
<TT
<CODE
CLASS="FUNCTION"
>lwres_getnamebyaddr()</TT
>lwres_getnamebyaddr()</CODE
>
return
<SPAN