RESOLVCONF(8) | System Manager's Manual | RESOLVCONF(8) |
resolvconf
—
resolvconf |
-I |
resolvconf |
[-m metric]
[-p ] [-x ]
-a
interface[.protocol]
<file |
resolvconf |
[-f ] -d
interface[.protocol] |
resolvconf |
[-x ] -il
pattern |
resolvconf |
-u |
resolvconf |
- -version |
resolvconf
manages
resolv.conf(5) files from
multiple sources, such as DHCP and VPN clients. Traditionally, the host runs
just one client and that updates /etc/resolv.conf.
More modern systems frequently have wired and wireless interfaces and there is
no guarantee both are on the same network. With the advent of VPN and other
types of networking daemons, many things now contend for the contents of
/etc/resolv.conf.
resolvconf
solves this by letting the
daemon send their
resolv.conf(5) file to
resolvconf
via
stdin(4) with the argument
-a
interface[.protocol] instead of
the filesystem. resolvconf
then updates
/etc/resolv.conf as it thinks best. When a local
resolver other than libc is installed, such as
dnsmasq(8) or
named(8), then
resolvconf
will supply files that the resolver
should be configured to include.
resolvconf
assumes it has a job to do. In
some situations resolvconf
needs to act as a
deterrent to writing to /etc/resolv.conf. Where this
file cannot be made immutable or you just need to toggle this behaviour,
resolvconf
can be disabled by adding
resolvconf=NO to
resolvconf.conf(5).
resolvconf
can mark an interfaces
resolv.conf as private. This means that the name
servers listed in that resolv.conf are only used for
queries against the domain/search listed in the same file. This only works
when a local resolver other than libc is installed. See
resolvconf.conf(5)
for how to configure resolvconf
to use a local name
server and how to remove the private marking.
resolvconf
can mark an interfaces
resolv.conf as exclusive. Only the latest exclusive
interface is used for processing, otherwise all are.
When an interface goes down, it should then call
resolvconf
with -d
interface.* arguments to delete the
resolv.conf file(s) for all the
protocols on the interface.
Here are some options for the above commands:-
-f
-m
metric-p
-x
resolvconf
has some more commands for
general usage:-
-i
pattern-l
pattern-u
resolvconf
to update all its subscribers.
resolvconf
does not update the subscribers when
adding a resolv.conf that matches what it already has for that
interface.-
-version
resolvconf
also has some commands designed
to be used by it's subscribers and system startup:-
-I
resolvconf
is used to add interfaces.-R
-r
service-v
-V
-v
except that only the information
configured in
resolvconf.conf(5)
is set.resolvconf
to work effectively, it has to process
the resolv.confs for the interfaces in the correct order.
resolvconf
first processes interfaces from the
interface_order list, then interfaces without a metic and
that match the dynamic_order list, then interfaces with a
metric in order and finally the rest in the operating systems lexical order.
See resolvconf.conf(5)
for details on these lists.
resolvconf
did not recommend a
protocol tag be appended to the
interface name. When the protocol is absent, it is
assumed to be the DHCP protocol.Portable subscribers should not use anything outside of /bin and /sbin because /usr and others may not be available when booting. Also, it would be unwise to assume any shell specific features.
-m
option is not present then we use
IF_METRIC for the metric.resolvconf
.resolvconf
adds, deletes or updates.resolvconf
.resolvconf
is called openresolv
and is fully command line compatible with Debian's resolvconf, as written by
Thomas Hood.
resolvconf
does not validate any of the
files given to it.
When running a local resolver other than libc, you will need to
configure it to include files that resolvconf
will
generate. You should consult
resolvconf.conf(5)
for instructions on how to configure your resolver.
November 29, 2016 | NetBSD 9.4 |