Comment 6 for bug 1032855

MarianoAbsatz wrote:
> After reading these two paragraph I thought (though I can be wrong) that:
>
> 1) dhclient doesn't handle /etc/resolv.conf directly but, instead, invokes resolvconf

If resolvconf is installed then dhclient calls resolvconf, otherwise it writes to /etc/resolv.conf directly. For details please read the make_resolv_conf() function in /sbin/dhclient-script.

> 2) resolvconf NEVER modifies /etc/resolv.conf but, instead, modifies
> /run/resolvconf/resolv.conf

Correct. The program /bin/resolvconf never touches /etc/resolv.conf directly.

But please note that the resolvconf *package* does put a symbolic link at /etc/resolv.conf at installation time unless you have told it not to or it thinks that it has already been installed before.

My advice: Install resolvconf which causes dhclient and similar programs to refrain from stomping on /etc/resolv.conf. Make sure that /etc/resolv.conf is a symbolic link "../resolvconf/resolv.conf". Then configure resolvconf so that it behaves the way you want. E.g., put

    nameserver ::1

in /etc/resolvconf/resolv.conf.d/base

so that this nameserver address is included in resolv.conf.