278N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
278N/A>The BIND 9 Lightweight Resolver</
TITLE 278N/ACONTENT="Modular DocBook HTML Stylesheet Version 1.7"><
LINK 278N/ATITLE="BIND 9 Administrator Reference Manual" 278N/ATITLE="Advanced DNS Features" 278N/ATITLE="BIND 9 Configuration Reference" 278N/ASUMMARY="Header navigation table" 278N/A>BIND 9 Administrator Reference Manual</
TH > 9 Lightweight Resolver</
H1>The Lightweight Resolver Library</
A>Running a Resolver Daemon</
A>5.1. The Lightweight Resolver Library</
A>Traditionally applications have been linked with a stub resolver
library that sends recursive DNS queries to a local caching name
>IPv6 once introduced new complexity into the resolution process,
such as following A6 chains and DNAME records, and simultaneous
lookup of IPv4 and IPv6 addresses. Though most of the complexity was
then removed, these are hard or impossible
to implement in a traditional stub resolver.</
P> 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
a simple UDP-based protocol, the "lightweight resolver protocol"
that is distinct from and simpler than the full DNS protocol.</
P>5.2. Running a Resolver Daemon</
A>To use the lightweight resolver interface, the system must
run the resolver daemon <
Bname server configured with a <
B>By default, applications using the lightweight resolver library will make
UDP requests to the IPv4 loopback address (127.0.0.1) on port 921. The
address can be overridden by <
B>The daemon currently only looks in the DNS, but in the future
it may use other sources such as <
TT> daemon is essentially a
caching-only name server that responds to requests using the lightweight
resolver protocol rather than the DNS protocol. Because it needs
to run on each host, it is designed to require no or minimal configuration.
Unless configured otherwise, it uses the name servers listed on
as forwarders, but is also capable of doing the resolution autonomously if
> daemon may also be configured with a
> style configuration file, in
> by default. A name server may also
be configured to act as a lightweight resolver daemon using the
SUMMARY="Footer navigation table" >Advanced DNS Features</
TD> 9 Configuration Reference</
TD