353N/A - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC") 353N/A - Copyright (C) 2000-2003 Internet Software Consortium. 353N/A - Permission to use, copy, modify, and/or distribute this software for any 353N/A - purpose with or without fee is hereby granted, provided that the above 353N/A - copyright notice and this permission notice appear in all copies. 353N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 353N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 353N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 353N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 353N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 353N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 353N/A - PERFORMANCE OF THIS SOFTWARE. 353N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
353N/A<
title>Chapter�5.�The BIND 9 Lightweight Resolver</
title>
353N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
353N/A<
link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
353N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
2695N/A<
table width="100%" summary="Navigation header">
353N/A<
tr><
th colspan="3" align="center">Chapter�5.�The <
acronym class="acronym">BIND</
acronym> 9 Lightweight Resolver</
th></
tr>
2695N/A<
td width="20%" align="left">
353N/A<
th width="60%" align="center">�</
th>
353N/A<
div class="titlepage"><
div><
div><
h1 class="title">
353N/A<
a name="Bv9ARM.ch05"></
a>Chapter�5.�The <
acronym class="acronym">BIND</
acronym> 9 Lightweight Resolver</
h1></
div></
div></
div>
353N/A<
p><
b>Table of Contents</
b></
p>
2695N/A<
dt><
span class="section"><
a href="Bv9ARM.ch05.html#id-1.6.3">The Lightweight Resolver Library</
a></
span></
dt>
353N/A<
div class="titlepage"><
div><
div><
h2 class="title" style="clear: both">
353N/A<
a name="id-1.6.3"></
a>The Lightweight Resolver Library</
h2></
div></
div></
div>
2695N/A Traditionally applications have been linked with a stub resolver
353N/A library that sends recursive DNS queries to a local caching name
2695N/A IPv6 once introduced new complexity into the resolution process,
353N/A such as following A6 chains and DNAME records, and simultaneous
2695N/A lookup of IPv4 and IPv6 addresses. Though most of the complexity was
353N/A then removed, these are hard or impossible
2695N/A to implement in a traditional stub resolver.
353N/A <
acronym class="acronym">BIND</
acronym> 9 therefore can also provide resolution
353N/A services to local clients
353N/A using a combination of a lightweight resolver library and a resolver
353N/A daemon process running on the local host. These communicate using
a simple UDP-based protocol, the "lightweight resolver protocol"
that is distinct from and simpler than the full DNS protocol.
<
div class="titlepage"><
div><
div><
h2 class="title" style="clear: both">
<
a name="lwresd"></
a>Running a Resolver Daemon</
h2></
div></
div></
div>
To use the lightweight resolver interface, the system must
run the resolver daemon <
span class="command"><
strong>lwresd</
strong></
span> or a
name server configured with a <
span class="command"><
strong>lwres</
strong></
span>
By default, applications using the lightweight resolver library will
UDP requests to the IPv4 loopback address (127.0.0.1) on port 921.
address can be overridden by <
span class="command"><
strong>lwserver</
strong></
span>
The daemon currently only looks in the DNS, but in the future
it may use other sources such as <
code class="filename">/
etc/
hosts</
code>,
The <
span class="command"><
strong>lwresd</
strong></
span> daemon is essentially a
caching-only name server that responds to requests using the
resolver protocol rather than the DNS protocol. Because it needs
to run on each host, it is designed to require no or minimal
Unless configured otherwise, it uses the name servers listed on
<
span class="command"><
strong>nameserver</
strong></
span> lines in <
code class="filename">/
etc/
resolv.conf</
code>
as forwarders, but is also capable of doing the resolution
The <
span class="command"><
strong>lwresd</
strong></
span> daemon may also be
<
code class="filename">
named.conf</
code> style configuration file,
be configured to act as a lightweight resolver daemon using the
<
span class="command"><
strong>lwres</
strong></
span> statement in <
code class="filename">
named.conf</
code>.
The number of client queries that the <
span class="command"><
strong>lwresd</
strong></
span>
daemon is able to serve can be set using the
<
code class="option">lwres-tasks</
code> and <
code class="option">lwres-clients</
code>
statements in the configuration.
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center">�</
td>
<
td width="40%" align="right">�<
a accesskey="n" href="Bv9ARM.ch06.html">Next</
a>
<
td width="40%" align="left" valign="top">Chapter�4.�Advanced DNS Features�</
td>
<
td width="20%" align="center"><
a accesskey="h" href="Bv9ARM.html">Home</
a></
td>
<
td width="40%" align="right" valign="top">�Chapter�6.�<
acronym class="acronym">BIND</
acronym> 9 Configuration Reference</
td>