[Resolvconf-devel] Bug#366309: Motivation? Patch?

Thomas Hood jdthood at yahoo.co.uk
Fri Jul 28 16:28:04 UTC 2006

martin f krafft wrote:
> If I always want to override the DNS, it should not matter where
> I got the entries from, DHCP, PPP, anything. Moreover, it would be
> nice to be able to control nameservers from a single location, not
> in various places.

/etc/network/interfaces is not the right place to configure this
sort of thing since /e/n/i is just ifupdown's configuration file.
One can start a DHCP client independently of ifupdown, and I presume
that you want the nameserver address to be overridden in that case

Here are a number of things to consider.

First of all, resolvconf already puts addresses for lo.* first and
truncates the nameserver list in resolv.conf after the first 127.*

Second, overriding is already possible in more than one way.  One
can add a

    nameserver w.x.y.z

line to /etc/resolvconf/resolv.conf.d/head so that this line always
appears before a "nameserver" line generated by resolvconf.  Thus
w.x.y.z will override any other addresses in the sense that it will
be tried first.

A more selective override can be implemented by editing the shell
script /etc/resolvconf/update.d/libc which is what generates the
dynamic resolv.conf file.

Now the question is: should we implement "selective overrides" in
some way that makes it easier for the administrator to configure?
Should we just implement overrides, or should we implement a more
general feature?

More information about the Resolvconf-devel mailing list