69 lines
3.3 KiB
HTML
69 lines
3.3 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>Name Service and Resolver Configuraton</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="node81.html">The Resolver Library</A>
|
|
<B>Up:</B> <A HREF="nag.html">The Network Administrators' Guide</A>
|
|
<B> Previous:</B> <A HREF="node79.html">The Future</A>
|
|
<BR> <P>
|
|
<H1><A NAME="SECTION008000000">Name Service and Resolver Configuraton</A></H1>
|
|
As discussed in chapter-<A HREF="node23.html#tcpip"><IMG ALIGN=BOTTOM ALT="gif" SRC="cross_ref_motif.gif"></A>, TCP/IP networking may rely on
|
|
different schemes to convert names into addresses. The simplest way,
|
|
which takes no advantage of the way the name space has been split up
|
|
into zones is a host table stored in /etc/hosts. This is
|
|
useful only for small LANs that are run by one single administrator,
|
|
and otherwise have no IP-traffic with the outside world. The format
|
|
of the hosts file has already been described in
|
|
chapter-<A HREF="node58.html#iface"><IMG ALIGN=BOTTOM ALT="gif" SRC="cross_ref_motif.gif"></A>.
|
|
<P>
|
|
<A NAME="3265"></A>
|
|
<A NAME="3266"></A>
|
|
<A NAME="3681"></A>
|
|
Alternatively, you may use BIND-- the Berkeley Internet Name Domain
|
|
Service-- for resolving host names to IP-addresses. Configuring BIND
|
|
may be a real chore, but once you've done it, changes in the network
|
|
topology are easily made. On, as on many other ish
|
|
systems, name service is provided through a program called named.
|
|
At startup, it loads a set of master files into its cache, and waits
|
|
for queries from remote or local user processes. There are different
|
|
ways to set up BIND, and not all require you to run a name server on
|
|
every host.
|
|
<P>
|
|
This chapter can do little more but give a rough sketch of how to
|
|
operate a name server. If you plan to use BIND in an environment with
|
|
more than just a small LAN and probably an Internet up-link, you should
|
|
get a good book on BIND, for instance Cricket Liu's ``DNS and BIND''
|
|
(see [<A HREF="#liudns"></A>]). For current information, you may also want to
|
|
check the release notes contained in the BIND sources. There's also a
|
|
newsgroup for DNS questions called comp.protocols.tcp-ip.domains.
|
|
<P>
|
|
<BR> <HR>
|
|
<UL>
|
|
<LI> <A HREF="node81.html#SECTION008100000">The Resolver Library</A>
|
|
<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>
|
|
<LI> <A HREF="node86.html#SECTION008200000">Running named</A>
|
|
<UL>
|
|
<LI> <A HREF="node87.html#SECTION008210000">The named.boot File</A>
|
|
<LI> <A HREF="node88.html#SECTION008220000">The DNS Database Files</A>
|
|
<LI> <A HREF="node89.html#SECTION008230000">Writing the Master Files</A>
|
|
<LI> <A HREF="node90.html#SECTION008240000">Verifying the Name Server Setup</A>
|
|
<LI> <A HREF="node91.html#SECTION008250000">Other Useful Tools</A>
|
|
</UL>
|
|
</UL>
|
|
<BR> <HR>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|