1RESOLVER(5) File Formats Manual RESOLVER(5)
2
3
4
6 resolver - resolver configuration file
7
9 /etc/resolv.conf
10
12 The resolver configuration file contains information that is read by
13 the resolver routines the first time they are invoked by a process.
14 The file is designed to be human readable and contains a list of name-
15 value pairs that provide various types of resolver information.
16
17 On a normally configured system this file should not be necessary. The
18 only name server to be queried will be on the local machine and the
19 domain name is retrieved from the system.
20
21 The different configuration options are:
22
23 nameserver
24 followed by the Internet address (in dot notation) of a name
25 server that the resolver should query. At least one name server
26 should be listed. Up to MAXNS (currently 3) name servers may be
27 listed, in that case the resolver library queries tries them in
28 the order listed. If no nameserver entries are present, the
29 default is to use the name server on the local machine. (The
30 algorithm used is to try a name server, and if the query times
31 out, try the next, until out of name servers, then repeat trying
32 all the name servers until a maximum number of retries are
33 made).
34
35 domain followed by a domain name, that is the default domain to append
36 to names that do not have a dot in them. If no domain entries
37 are present, the domain returned by gethostname(2) is used
38 (everything after the first `.'). Finally, if the host name
39 does not contain a domain part, the root domain is assumed.
40
41 The name value pair must appear on a single line, and the keyword (e.g.
42 nameserver) must start the line. The value follows the keyword, sepa‐
43 rated by white space.
44
46 /etc/resolv.conf
47
49 gethostbyname(3N), resolver(3), named(8)
50 Name Server Operations Guide for BIND
51
52
53
544th Berkeley Distribution September 14, 1987 RESOLVER(5)