|Main index||Section 8||Options|
solves this by letting the daemon send their
with the argument
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
Here are some options for the above commands:-
| ||Ignore non existent interfaces. Only really useful for deleting interfaces.|
|Set the metric of the interface when adding it, default of 0. Lower metrics take precedence. This affects the default order of interfaces when listed.|
| ||Marks the interface resolv.conf as private.|
| ||Mark the interface resolv.conf as exclusive when adding, otherwise only use the latest exclusive interface.|
resolvconf has some more commands for general usage:-
|List the interfaces and protocols, optionally matching pattern, we have resolv.conf files for.|
|List the resolv.conf files we have. If pattern is specified then we list the files for the interfaces and protocols that match it.|
| ||Force 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.|
|Echo the resolvconf version to stdout.|
resolvconf also has some commands designed to be used by it's subscribers and system startup:-
| ||Initialise the state directory /var/run/resolvconf. This only needs to be called if the initial system boot sequence does not automatically clean it out; for example the state directory is moved somewhere other than /var/run. If used, it should only be called once as early in the system boot sequence as possible and before resolvconf is used to add interfaces.|
| ||Echo the command used to restart a service.|
|If the service is running then restart it. If the service does not exist or is not running then zero is returned, otherwise the result of restarting the service.|
| ||Echo variables DOMAINS, SEARCH and NAMESERVERS so that the subscriber can configure the resolver easily.|
|dhcp||Dynamic Host Configuration Protocol. Initial versions of 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.|
|ra||IPv6 Router Advertisement.|
|dhcp6||Dynamic Host Configuration Protocol, version 6.|
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.
|IF_PRIVATE||Marks the interface resolv.conf as private.|
|IF_EXCLUSIVE||Marks the interface resolv.conf as exclusive.|
|/etc/resolv.conf.bak||Backup file of the original resolv.conf.|
|/etc/resolvconf.conf||Configuration file for resolvconf.|
|/libexec/resolvconf||Directory of subscribers which are run every time resolvconf adds, deletes or updates.|
|/libexec/resolvconf/libc.d||Directory of subscribers which are run after the libc subscriber is run.|
|/var/run/resolvconf||State directory for resolvconf.|
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.
|RESOLVCONF (8)||November 29, 2016|
|Main index||Section 8||Options|
|“||I have a natural revulsion to any operating system that shows so little planning as to have to named all of its commands after digestive noises (awk, grep, fsck, nroff).||”|