[CentOS] resolv.conf rewritten every reboot. How to figure out who and why?

Dave tdbtdb+centos at gmail.com
Sat Oct 10 00:18:13 UTC 2009

On Thu, Oct 8, 2009 at 2:54 PM, Joseph L. Casale
<JCasale at activenetwerx.com> wrote:
>>Just one of those things you kind of pick up as you go along and
>>remember.  Tribal knowledge if you will.
> There's two pdf's and one command I use "often" :)
> The redhat 5.3 deployment and installation pdf's (or the online versions)

That looks useful to know.

> and:
> # find /usr/share/doc/ -exec grep "PEERDNS" '{}' \; -print
>    PEERDNS=yes|no
>      file if PEERDNS is not set to "no".
> /usr/share/doc/initscripts-8.45.25/sysconfig.txt
>    honor PEERDNS=no for pump and dhcpcd too (#18619)
>    DEFROUTE defaults on; PEERDNS documented and defaults on
> /usr/share/doc/initscripts-8.45.25/ChangeLog
> Now you know what doc to read...

Yeah, but by the time I knew PEERDNS was involved, all the hard work
was done. Try that find command with 'resolv.conf' instead of PEERDNS
and you get way too many hits.


More information about the CentOS mailing list