1 .TH RESOLVCONF 8 "9 Nov 2007" "openresolv"
3 resolvconf \- manage nameserver information
7 \fB\-a\fR \fIINTERFACE\fR
10 \fB\-d\fR \fIINTERFACE\fR
16 \fB\-l\fR \fIPATTERN\fR
19 \fB\-i\fR \fIPATTERN\fR
22 \fB\-v\fR \fIPATTERN\fr
24 Overwrite (\fB\-a\fR) or delete (\fB\-d\fR) the nameserver information
25 record for network interface \fIINTERFACE\fR
26 and run the update scripts in \fI%%PREFIX%%/etc/resolvconf/update.d/\fR.
28 With \fB\-u\fR, just run the update scripts.
30 With \fB\-l\fR, list the resolv files for each interface, optionally
31 with patterns to match interface names.
33 With \fB\-i\fR, list the interfaces we have resolv files for, optionally
34 with patterns to match interface names.
36 With \fB\-v\fR, we echo variables NEWDOMAIN, NEWSEARCH and NEWNS to the
37 console which can be used to make it easer writing scripts which configure
42 is run only by hook scripts attached to network interface configurers
46 to DHCP clients such as
49 .BR /etc/init.d/net.eth0
55 (for the loopback interface).
56 However, the administrator can also run
58 from the command line to add or delete auxiliary nameserver information.
60 Nameserver information provided to
62 is stored for use by subscribers to \fBresolvconf\fR's notification service.
63 Subscribers that need to know when nameserver information has changed
64 should install a script in \fI%%PREFIX%%/etc/resolvconf/update.d/\fR
65 (... or in \fI%%PREFIX%%/etc/resolvconf/update-libc.d/\fR: see below).
66 For example, DNS caches such as
70 subscribe to the notification service so that they know
71 whither to forward queries.
73 The most important piece of
74 software that subscribes to the notification service is the set of functions
75 that make up the GNU C Library
77 When nameserver information is updated the script
78 \fI%%PREFIX%%/etc/resolvconf/update.d/libc\fR writes a new resolver configuration
79 file to \fI%%PREFIX%%/etc/resolvconf/run/resolv.conf\fR and then runs the scripts in
80 %%PREFIX%%/etc/resolvconf/update-libc.d/.
81 To make the resolver use the dynamically generated resolver configuration
82 file the administrator should ensure that \fI/etc/resolv.conf\fR is a symbolic
83 link to \fI%%PREFIX%%/etc/resolvconf/run/resolv.conf\fR.
84 This link is never modified by \fB/sbin/resolvconf\fR.
85 If you find that \fI/etc/resolv.conf\fR is not being updated,
86 check to see that the link is intact.
88 The C Library resolver library isn't the only resolver library available.
89 However, any resolver library that reads /etc/resolv.conf
90 (and most of them do, in order to be compatible with the C Library resolver)
91 should work with \fBresolvconf\fR.
93 \fBopenresolv\fR ships with subscribers for
97 wwhich handle resolv.conf a bit differently. If they handle search AND domain
98 options then the nameservers listed with the domain are only used when
99 querying for that domain.
103 # resolv.conf from bge0
107 # resolv.conf from tap0
112 In this instance, nameserver 5.6.7.8 will only handle requests for bar.org
113 and nameserver 1.2.3.4 will handle everything else.
115 Subscribers that need to know only when the resolver configuration file
116 has changed should install a script in \fI/etc/resolvconf/update-libc.d/\fR
117 rather than in \fI%%PREFIX%%/etc/resolvconf/update.d/\fR.
118 (This is important for synchronization purposes:
119 scripts in \fIupdate-libc.d/\fR are run after resolv.conf has been updated;
120 the same is not necessarily true of scripts in update.d/.)
123 \fB\-a\fR \fIINTERFACE\fR
124 Add or overwrite the record for network interface \fIINTERFACE\fR.
125 When this option is used the information must be provided to
127 on its standard input in the format of the
130 Each line in the file must be terminated by a newline.
132 \fB\-d\fR \fIINTERFACE\fR
133 Delete the record for network interface \fIINTERFACE\fR.
135 The \fIINTERFACE\fR name may not contain spaces, slashes, asterisks or
136 initial dots, hyphens or tildes.
138 Following the addition or deletion of the record, resolvconf runs
139 the update scripts as described in the CLIENTS section.
142 Just run the update scripts.
144 \fB\-l\fR \fIPATTERN\fR
145 List the resolv.conf files for the interfaces that match the pattern,
146 otherwise all the interfaces.
148 \fB\-i\fR \fIPATTERN\fR
149 List the interfaces that match the pattern otherwise all the interfaces.
151 \fB\-v\fR \fIPATTERN\fR
152 Echo variables NEWDOMAIN, NEWSEARCH and NEWNS to the console.
155 .I %%PREFIX%%/etc/resolvconf/run
156 This is either a directory where nameserver information can be stored
157 or a symbolic link to such a directory.
158 Clients should not make any assumptions about the canonical location
159 of this directory or the hierarchy that is constructed under it.
161 .I %%PREFIX%%/etc/resolvconf/interface-order
162 Determines the order in which nameserver information records are processed
165 .I %%PREFIX%%/etc/resolvconf/resolv.conf.d/base
166 File containing basic resolver information.
167 The lines in this file are included in the resolver configuration file
168 even when no interfaces are configured.
170 .I %%PREFIX%%/etc/resolvconf/resolv.conf.d/head
171 File to be prepended to the dynamically generated resolver configuration file.
172 Normally this is just a comment line.
174 .I %%PREFIX%%/etc/resolvconf/reslov.conf.d/tail
175 File to be appended to the dynamically generated resolver configuration file.
176 To append nothing, make this an empty file.
180 does not check the sanity of the information provided to it.
182 Written by Roy Marples <roy@marples.name>.
184 Heavily based on Debians resolvconf by Thomas Hood <jdthood_AT_yahoo.co.uk>
186 Copyright \(co 2006 Gentoo Foundation
188 Copyright \(co 2007 Roy Marples