Differences between current version and predecessor to the previous major change of resolv.conf(5).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Thursday, October 16, 2003 3:21:56 pm | by CraigBox | |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:30:41 am | by perry | Revert |
@@ -1,22 +1,13 @@
-RESOLVER
-!!!RESOLVER
-NAME
-SYNOPSIS
-DESCRIPTION
-FILES
-SEE ALSO
-----
!!NAME
-
resolver - resolver configuration file
+
!!SYNOPSIS
-
/etc/resolv.conf
+
!!DESCRIPTION
-
The ''resolver'' is a set of routines in the C library
that provide access to the Internet Domain Name System. The
resolver configuration file contains information that is
@@ -34,125 +25,46 @@
The different configuration options are:
+; __nameserver__ : 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 __nameserver__ 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).
-__nameserver
__
+;
__domain
__ : Local domain name. Most queries for names within this domain can use short names relative to the local domain. If no __domain__ entry is present, the domain is determined from the local host name returned by ''gethostname''(); 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.
+; __search__ : Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the ''search'' 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.
-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 __nameserver__ 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)
.
+;:
The search list
is currently limited
to six domains with
a total
of 256 characters
.
+; __sortlist__ : Sortlist allows addresses returned by gethostbyname to be sorted. A sortlist is specified by IP address netmask pairs. The netmask is optional and defaults to the natural netmask of the net. The IP address and optional network pairs are separated by slashes. Up to 10 pairs may be specified.
-__domain__
+;: e.g. sortlist 130.155.160./255.255.240.0 130.155..
+; __options__ : Options allows certain internal resolver variables to be modified. The syntax is
-Local domain name. Most queries for names within this domain
-can use short names relative to the local domain. If no
-__domain__ entry is present, the domain is determined
-from the local host name returned by ''gethostname''();
-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.
-
-
-__search__
-
-
-Search list for host-name lookup. The search list is
-normally determined from the local domain name; by default,
-it contains only the local domain name. This may be changed
-by listing the desired domain search path following the
-''search'' 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.
-
-
-__sortlist__
-
-
-Sortlist allows addresses returned by gethostbyname to be
-sorted. A sortlist is specified by IP address netmask pairs.
-The netmask is optional and defaults to the natural netmask
-of the net. The IP address and optional network pairs are
-separated by slashes. Up to 10 pairs may be
-specified.
-
-
-e.g. sortlist 130.155.160./255.255.240.
-130.155..
-
-
-__options__
-
-
-Options allows certain internal resolver variables to be
-modified. The syntax is
-
-
-
-
+
__options__ ''option ...''
where ''option'' is one of the following:
+;;: __debug__ -- sets RES_DEBUG in _res.options.
-__debug__ -- sets RES_DEBUG in _res.options.
+;;:__ndots:__''n'' -- sets a threshold for the number of dots which must appear in a name given to __res_query__ (see resolver(3)) before an ''initial absolute query'' will be made. The default for ''n'' is ``1'', meaning that if there are any dots in a name, the name will be tried first as an absolute name before any ''search list'' elements are appended to it.
-__ndots:__''n'' -- sets a threshold for the number of
-dots which must appear in a name given to __res_query__
-(see resolver(3)) before an ''initial absolute
-query'' will be made. The default for ''n'' is ``1'',
-meaning that if there are any dots in a name, the name will
-be tried first as an absolute name before any ''search
-list'' elements are appended to it.
-
-
-
-
+The ''domain'' and ''search'' keywords are mutually exclusive. If more than one instance of these keywords is
present, the last instance wins.
+The ''search'' keyword of a system's ''resolv.conf'' file can be overridden on a per-process basis by setting the
+environment variable "LOCALDOMAIN" to a space-separated list of search domains.
-The ''search
'' keyword of a system's ''resolv.conf''
-overridden
on a per-process basis by setting the
-environment variable `` LOCALDOMAIN ''
to a
-search domains
.
+The ''options
'' keyword of a system's ''resolv.conf'' file can be amended
on a per-process basis by setting the
+environment variable "RES_OPTIONS"
to a space-separated list of resolver options as explained above under __options__
.
+The keyword and value must appear on a single line, and the keyword (e.g. __nameserver__) must start the line. The
+value follows the keyword, separated by whitespace.
-The ''options'' keyword of a system's ''resolv.conf''
-file can be amended on a per-process basis by setting the
-environment variable `` RES_OPTIONS '' to a
-space-separated list of resolver options as explained above
-under __options__.
-
-
-The keyword and value must appear on a single line, and the
-keyword (e.g. __nameserver__) must start the line. The
-value follows the keyword, separated by white
-space.
!!FILES
+''/etc/resolv.conf''
-''/etc/resolv.conf''
!!SEE ALSO
-
-
-
-
-----
+gethostbyname(3), hostname(7), named(8), Name Server Operations Guide for BIND
