|
|
1.1 root 1: .\" Copyright (c) 1986 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)resolver.5 5.11 (Berkeley) 6/27/90
19: .\"
20: .TH RESOLVER 5 "June 27, 1990"
21: .UC 4
22: .SH NAME
23: resolver \- resolver configuration file
24: .SH SYNOPSIS
25: /etc/resolv.conf
26: .SH DESCRIPTION
27: .LP
28: The
29: .I resolver
30: is a set of routines in the C library (\c
31: .IR resolver (3))
32: that provide access to the Internet Domain Name System.
33: The resolver configuration file contains information that is read
34: by the resolver routines the first time they are invoked by a process.
35: The file is designed to be human readable and contains a list of
36: keywords with values that provide various types of resolver information.
37: .LP
38: On a normally configured system this file should not be necessary.
39: The only name server to be queried will be on the local machine,
40: the domain name is determined from the host name,
41: and the domain search path is constructed from the domain name.
42: .LP
43: The different configuration options are:
44: .TP
45: \fBnameserver\fP
46: Internet address (in dot notation) of a name server
47: that the resolver should query.
48: Up to MAXNS (currently 3) name servers may be listed,
49: one per keyword.
50: If there are multiple servers,
51: the resolver library queries them in the order listed.
52: If no \fBnameserver\fP entries are present,
53: the default is to use the name server on the local machine.
54: (The algorithm used is to try a name server, and if the query times out,
55: try the next, until out of name servers,
56: then repeat trying all the name servers
57: until a maximum number of retries are made).
58: .TP
59: \fBdomain\fP
60: Local domain name.
61: Most queries for names within this domain can use short names
62: relative to the local domain.
63: If no \fBdomain\fP entry is present, the domain is determined
64: from the local host name returned by
65: \fIgethostname\fP\|(2);
66: the domain part is taken to be everything after the first `.'.
67: Finally, if the host name does not contain a domain part, the root
68: domain is assumed.
69: .TP
70: \fBsearch\fP
71: Search list for host-name lookup.
72: The search list is normally determined from the local domain name;
73: by default, it begins with the local domain name, then successive
74: parent domains that have at least two components in their names.
75: This may be changed by listing the desired domain search path
76: following the \fIsearch\fP keyword with spaces or tabs separating
77: the names.
78: Most resolver queries will be attempted using each component
79: of the search path in turn until a match is found.
80: Note that this process may be slow and will generate a lot of network
81: traffic if the servers for the listed domains are not local,
82: and that queries will time out if no server is available
83: for one of the domains.
84: .IP
85: The search list is currently limited to six domains
86: with a total of 256 characters.
87: .LP
88: The \fIdomain\fP and \fIsearch\fP keywords are mutually exclusive.
89: If more than one instance of these keywords is present,
90: the last instance will override.
91: .LP
92: The keyword and value must appear on a single line, and the keyword
93: (e.g. \fBnameserver\fP) must start the line. The value follows
94: the keyword, separated by white space.
95: .SH FILES
96: .I /etc/resolv.conf
97: .SH SEE ALSO
98: gethostbyname(3N), resolver(3), hostname(7), named(8)
99: .br
100: Name Server Operations Guide for BIND
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.