old-www/LDP/nag/node38.html

52 lines
2.2 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>Domain Name Servers</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="node39.html">The DNS Database</A>
<B>Up:</B> <A HREF="node34.html">The Domain Name System</A>
<B> Previous:</B> <A HREF="node37.html">Name Lookups with DNS</A>
<BR> <P>
<H2><A NAME="SECTION004640000">Domain Name Servers</A></H2>
Name servers that hold all information on hosts within a zone are
called <em>authoritative</em> for this zone, and are sometimes referred
to as <em>master name servers</em>. Any query for a host within this
zone will finally wind down at one of these master name servers.
<P>
<A NAME="1601"></A>
<A NAME="1602"></A>
<A NAME="1603"></A>
<A NAME="1604"></A>
To provide a coherent picture of a zone, its master servers must be
fairly well synchronized. This is achieved by making one of them the
<em>primary</em> server, which loads its zone information from data
files, and making the others <em>secondary</em> servers who transfer the
zone data from the primary server at regular intervals.
<P>
One reason to have several name servers is to distribute work load,
another is redundancy. When one name server machine fails in a benign
way, like crashing or losing its network connection, all queries will
fall back to the other servers. Of course, this scheme doesn't protect
you from server malfunctions that produce wrong replies to all DNS
requests, e.g. from software bugs in the server program itself.
<P>
<A NAME="1607"></A>
Of course, you can also think of running a name server that is not
authoritative for any domain.<A HREF="footnode.html#1748"><IMG ALIGN=BOTTOM ALT="gif" SRC="foot_motif.gif"></A> This type of server is useful nevertheless, as it is still able to
conduct DNS queries for the applications running on the local network,
and cache the information. It is therefore called a <em>caching-only</em>
server.
<P>
<A NAME="1611"></A>
<P>
<BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>