old-www/LDP/nag/node81.html

39 lines
1.6 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>The Resolver Library</TITLE>
</HEAD>
<BODY LANG="EN">
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
<B> Next:</B> <A HREF="node82.html">The host.conf File</A>
<B>Up:</B> <A HREF="node80.html">Name Service and Resolver </A>
<B> Previous:</B> <A HREF="node80.html">Name Service and Resolver </A>
<BR> <P>
<H1><A NAME="SECTION008100000">The Resolver Library</A></H1>
When talking of ``the resolver'', we do not mean any special
application, but rather refer to the <em>resolver library</em>, a
collection of functions that can be found in the standard C library. The
central routines are gethostbyname(2) and gethostbyaddr(2)
which look up all IP addresses belonging to a host, and vice versa.
They may be configured to simply look up the information in
hosts, query a number of name servers, or use the hosts
database of NIS (Network Information Service). Other applications, like
smail, may include different drivers for any of these, and need
special care.
<HR>
<UL>
<LI> <A HREF="node82.html#SECTION008110000">The host.conf File</A>
<LI> <A HREF="node83.html#SECTION008120000">Resolver Environment Variables</A>
<LI> <A HREF="node84.html#SECTION008130000">Configuring Name Server Lookups-- resolv.conf</A>
<LI> <A HREF="node85.html#SECTION008140000">Resolver Robustness</A>
</UL>
<BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>