Commit | Line | Data |
---|---|---|
591e95f8 | 1 | .\" @(#)resolver.5 5.2 (Berkeley) %G% |
ba305536 KD |
2 | .\" |
3 | .TH RESOLVER 5 "1 January 1986" | |
4 | .UC 4 | |
5 | .SH NAME | |
6 | resolver configuration file | |
7 | .SH DESCRIPTION | |
8 | .LP | |
9 | The resolver configuration file contains information that is read | |
10 | by the resolver routines the first time they are invoked in a process. | |
11 | The file is designed to be human readable and contains a list of | |
12 | name-value pairs which provide various types of resolver information. | |
13 | .LP | |
14 | The different configuration options are: | |
15 | .TP | |
16 | \fBnameserver\fP | |
17 | followed by the Internet address (in dot notation) of a nameserver | |
18 | that the resolver should query. At least one nameserver should be | |
19 | listed. Up to MAXNS (currently 3) nameservers may be listed, in which | |
20 | case the resolver library queries tries them in the order listed. | |
21 | (The algorithm used is to try a nameserver, and if the query times out, | |
22 | try the next, until out of nameservers, then repeat trying all the nameservers | |
23 | until a maximum number of retries has been made). | |
24 | .TP | |
25 | \fBdomain\fP | |
26 | followed by a domain name, which is | |
27 | the default domain to append to names which do not have a dot in them. | |
28 | This defaults to empty (the root domain). | |
29 | .LP | |
30 | The name value pair must appear on a single line, and the keyword | |
31 | (e.g. \fBnameserver\fP) must start the line. The value follows | |
32 | the keyword, separated by whitespace. | |
33 | .SH FILES | |
34 | .I /etc/resolv.conf | |
35 | .SH SEE ALSO | |
36 | gethostent(3n), resolver(3), named(8) |