Re: Why does resolv.conf keep changing?
- Date: Wed, 25 Oct 2017 09:23:01 -0400
- From: Michael Stone <mstone@xxxxxxxxxx>
- Subject: Re: Why does resolv.conf keep changing?
On Wed, Oct 25, 2017 at 09:03:07AM -0400, Greg Wooledge wrote:
If Debian developers who are responsible for resolvconf are reading this,
and if they actually CARE about making things work correctly and sensibly,
then here is yet another proposal: give us a way to QUICKLY and EASILY
and RELIABLY tell resolvconf "never do anything". I don't care where it
is, or what it looks like. Just make SOME way to configure the system so
that /etc/resolv.conf is never touched in any way by ANYTHING. Resolvconf
already intercepts all the incoming attempts to modify /etc/resolv.conf
by dhclient et al., right? That's its entire purpose, right? So just
give us a way to tell it to intercept those requests and do nothing.
You understand that in most of the cases discussed recently it isn't
resolvconf changing resolv.conf, it's the dhcp client? One of the
drivers for resolvconf was to have a central place to configure
preferences so that people *wouldn't* have to deal with a number of
other daemons modifying the resolv.conf file and overwriting each other.