From e91b6c79f5e72c13ea9d7f6f45f15f116e7e0cd2 Mon Sep 17 00:00:00 2001 From: Mike Karels Date: Thu, 14 Dec 1989 16:54:12 -0800 Subject: [PATCH] add search keyword SCCS-vsn: share/man/man5/resolver.5 5.8 --- usr/src/share/man/man5/resolver.5 | 58 +++++++++++++++++++++++-------- 1 file changed, 44 insertions(+), 14 deletions(-) diff --git a/usr/src/share/man/man5/resolver.5 b/usr/src/share/man/man5/resolver.5 index d9eda347de..4d25a1ea98 100644 --- a/usr/src/share/man/man5/resolver.5 +++ b/usr/src/share/man/man5/resolver.5 @@ -13,7 +13,7 @@ .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. .\" -.\" @(#)resolver.5 5.7 (Berkeley) %G% +.\" @(#)resolver.5 5.8 (Berkeley) %G% .\" .TH RESOLVER 5 "" .UC 4 @@ -23,22 +23,30 @@ resolver \- resolver configuration file /etc/resolv.conf .SH DESCRIPTION .LP +The +.I resolver +is a set of routines in the C library (\c +.IR resolv (3)) +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 -name-value pairs that provide various types of resolver information. +keywords with values that provide various types of resolver information. .LP On a normally configured system this file should not be necessary. -The only name server to be queried will be on the local machine and -the domain name is retrieved from the system. +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. .LP The different configuration options are: .TP \fBnameserver\fP -followed by the Internet address (in dot notation) of a name server -that the resolver should query. At least one name server should be -listed. Up to MAXNS (currently 3) name servers may be listed, in that -case the resolver library queries tries them in the order listed. +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 \fBnameserver\fP 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, @@ -47,19 +55,41 @@ then repeat trying all the name servers until a maximum number of retries are made). .TP \fBdomain\fP -followed by a domain name, that is -the default domain to append to names that do not have a dot in them. -If no \fBdomain\fP entries are present, the domain returned by -\fIgethostname\fP\|(2) is used (everything after the first `.'). +Local domain name. +Most queries for names within this domain can use short names +relative to the local domain. +If no \fBdomain\fP entry is present, the domain is determined +from the local host name returned by +\fIgethostname\fP\|(2); +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. +.TP +\fBsearch\fP +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 \fIsearch\fP 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. +.LP +The \fIdomain\fP and \fIsearch\fP keywords are mutually exclusive. +If more than one instance of these keywords is present, +the last instance will override. .LP -The name value pair must appear on a single line, and the keyword +The keyword and value must appear on a single line, and the keyword (e.g. \fBnameserver\fP) must start the line. The value follows the keyword, separated by white space. .SH FILES .I /etc/resolv.conf .SH SEE ALSO -gethostbyname(3N), resolver(3), named(8) +gethostbyname(3N), resolver(3), hostname(7), named(8) .br Name Server Operations Guide for BIND -- 2.20.1