lostecho/oldlinux-files
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add directory Minix

Browse Source
This commit is contained in:
gohigh
2024-02-19 00:21:39 -05:00
parent 56596ada90
commit 5a46ddb732
2923 changed files with 1764412 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

121
Minix/2.0.0/wwwman/man5/resolver.5.html Normal file
View File

@@ -0,0 +1,121 @@
<HTML>
<HEAD>
<TITLE>resolver(5)</TITLE>
</HEAD>
<BODY>
<H1>resolver(5)</H1>
<HR>
<PRE>
</PRE>
<H2>NAME</H2><PRE>
resolver - resolver configuration file
</PRE>
<H2>SYNOPSIS</H2><PRE>
/etc/resolv.conf
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <EM>resolver</EM> is a set of routines in the C library (<STRONG><A HREF="../man3/resolv.3.html">resolv(3)</A></STRONG>) that
provide access to the Internet Domain Name System. The resolver
configuration file contains information that is read by the resolver
routines the first time they are invoked by a process. The file is
designed to be human readable and contains a list of keywords with values
that provide various types of resolver information.
On a normally configured system this file should not be necessary. The
only name server to be queried will be on the local machine, the domain
name is determined from the host name, and the domain search path is
constructed from the domain name.
The different configuration options are:
<STRONG>nameserver</STRONG>
Internet address (in dot notation) of a name server that the
resolver should query. Up to MAXNS (currently 3) name servers may
be listed, one per keyword. If there are multiple servers, the
resolver library queries them in the order listed. If no <STRONG>nameserver</STRONG>
entries are present, the default is to use the name server on the
local machine. (The algorithm used is to try a name server, and if
the query times out, try the next, until out of name servers, then
repeat trying all the name servers until a maximum number of retries
are made).
<STRONG>domain</STRONG>
Local domain name. Most queries for names within this domain can
use short names relative to the local domain. If no <STRONG>domain</STRONG> entry is
present, the domain is determined from the local host name returned
by <STRONG><A HREF="../man2/gethostname.2.html">gethostname(2)</A></STRONG>; the domain part is taken to be everything after
the first `.'. Finally, if the host name does not contain a domain
part, the root domain is assumed.
<STRONG>search</STRONG>
Search list for host-name lookup. The search list is normally
determined from the local domain name; by default, it begins with
the local domain name, then successive parent domains that have at
least two components in their names. This may be changed by listing
the desired domain search path following the <EM>search</EM> keyword with
spaces or tabs separating the names. Most resolver queries will be
attempted using each component of the search path in turn until a
match is found. Note that this process may be slow and will
generate a lot of network traffic if the servers for the listed
domains are not local, and that queries will time out if no server
is available for one of the domains.
The search list is currently limited to six domains with a total of
256 characters.
The <EM>domain</EM> and <EM>search</EM> keywords are mutually exclusive. If more than one
instance of these keywords is present, the last instance will override.
The keyword and value must appear on a single line, and the keyword (e.g.
<STRONG>nameserver</STRONG>) must start the line. The value follows the keyword,
separated by white space.
</PRE>
<H2>FILES</H2><PRE>
/<EM>etc</EM>/<EM>resolv</EM>.<EM>conf</EM>
</PRE>
<H2>SEE ALSO</H2><PRE>
<STRONG><A HREF="../man3/gethostbyname.3N.html">gethostbyname(3N)</A></STRONG>, <STRONG><A HREF="../man3/resolver.3.html">resolver(3)</A></STRONG>, <STRONG><A HREF="../man7/hostname.7.html">hostname(7)</A></STRONG>, <STRONG><A HREF="../man8/named.8.html">named(8)</A></STRONG>
Name Server Operations Guide for BIND
</PRE>
</BODY>
</HTML>