Overwrite (-a) or delete (-d) the nameserver information
record for network interface INTERFACE
and run the update scripts in /etc/resolvconf/update.d/
if the nameserver information has changed.
With -u, just run the update scripts.
is run only by hook scripts attached to network interface configurers
(for ppp interfaces),
to DHCP clients such as
to DNS caches such as
(for the loopback interface).
These hook scripts furnish
with information about nameservers.
receives one or more nameserver addresses
during its negotiation with the DHCP server;
its hook script
publishes this information to
program can be used to configure network interfaces
according to settings in
publish nameserver information to
when it configures an interface, add
lines to the relevant
stanza in /etc/network/interfaces.
To add nameserver addresses add a line beginning with
dns-nameservers 126.96.36.199 188.8.131.52
Note that one or more addresses can be given,
and note the `s' at the end of the option name.
(Contrast with the
For each other valid
you can include, in the stanza,
one line beginning with that option name with a
The resulting stanza might look like the following example.
See the resolvconf package's README file for more detailed information.
For more information about the dns-* options, e.g.,
The administrator can run
from the command line to add or delete nameserver information,
but this is not normally necessary.
Nameserver information provided to
is stored for use by subscribers to resolvconf's notification service.
Subscribers that need to know when nameserver information has changed
should install a script in /etc/resolvconf/update.d/
(... or in /etc/resolvconf/update-libc.d/: see below).
For example, DNS caches such as
subscribe to the notification service so that they know
whither to forward queries.
The most important piece of
software that subscribes to the notification service is the set of functions
that make up the GNU C Library
When nameserver information is updated the script
/etc/resolvconf/update.d/libc writes a new resolver configuration
file to /etc/resolvconf/run/resolv.conf and then runs the scripts in
To make the resolver use the dynamically generated resolver configuration
file the administrator should ensure that /etc/resolv.conf is a symbolic
link to /etc/resolvconf/run/resolv.conf.
This link is never modified by /sbin/resolvconf.
If you find that /etc/resolv.conf is not being updated,
check to see that the link is intact.
The GNU C Library resolver library isn't the only resolver library available.
However, any resolver library that reads /etc/resolv.conf
(and most of them do, in order to be compatible with the GNU C Library resolver)
should work with
Subscribers that need to know only when the resolver configuration file
has changed should install a script in /etc/resolvconf/update-libc.d/
rather than in /etc/resolvconf/update.d/.
This is important for synchronization purposes:
scripts in update-libc.d/ are run after resolv.conf has been updated;
the same is not necessarily true of scripts in update.d/.
Examples of packages that do this are
Client hook scripts will find the files containing nameserver
information in the current directory.
Add or overwrite the record for network interface INTERFACE.
When this option is used the information must be provided to
on its standard input in the format of the
Each line in the file must be terminated by a newline.
Delete the record for network interface INTERFACE.
The INTERFACE name may not contain spaces, slashes or
initial dots, hyphens or tildes.
Following the addition or deletion of the record, resolvconf runs
the update scripts as described in the CLIENTS section.
Just run the update scripts.
The following variables can be set in /etc/default/resolvconf.
If set to "yes" then
will print a message when /etc/resolv.conf is not a symbolic link
Set to "no" to prevent the printing of this message.
The default is "yes".
If set to "yes" then the update.d/libc script will include
no more nameserver addresses after the first address
that starts with "127."
This is usually the preferable behavior
if the nameserver at 127.* is a local caching nameserver
since it inhibits unnecessary changes to resolv.conf.
When an interface is brought up the local caching nameserver
is informed by
of any new nameserver addresses
and the additional name service is made available to applications
that make use of the resolver and the local caching nameserver;
the applications themselves do not need to be notified of the change.
A disadvantage of this mode of operation is that applications have
no secondary or tertiary nameserver address to fall back on should
the local caching nameserver crash.
Insofar as a local nameserver crash can be regarded
as an unlikely event,
this is a relatively minor disadvantage.
Set to "no" to disable this truncation feature.
The default is "yes".
This is the directory where the dynamically generated
file will be placed. See the README file for more information.
The default location is
See the ENVIRONMENT VARIABLES section.
This is either a directory where nameserver information can be stored
or a symbolic link to such a directory.
Clients should not make any assumptions about the canonical location
of this directory or the hierarchy that is constructed under it.
Determines the order in which nameserver information records are processed.
File containing basic resolver information.
The lines in this file are included in the resolver configuration file
even when no interfaces are configured.
File to be prepended to the dynamically generated resolver configuration file.
Normally this is just a comment line.
File to be appended to the dynamically generated resolver configuration file.
To append nothing, make this an empty file.
This file is a good place to put a resolver
line if one is needed, e.g.,
does not check the sanity of the information provided to it.