Date: Mon, 31 Dec 2018 13:41:07 +1030 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: freebsd-questions@freebsd.org, byrnejb@harte-lyne.ca Subject: Re: /etc/resolv.conf overwritten by what? Message-ID: <6abf5488-84ac-186e-a244-5fca2ccf8533@ShaneWare.Biz> In-Reply-To: <1551791.MsCH1bHPGx@curlew> References: <961dc39c14de8d519801ca9fe3b2cdd9.squirrel@webmail.harte-lyne.ca> <1551791.MsCH1bHPGx@curlew>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31/12/18 3:45 am, Mike Clarke wrote: > On Friday, 28 December 2018 15:15:54 GMT James B. Byrne via freebsd-questions wrote: >> Something changed the contents of /etc/resolv.conf from this: >> >> search hamilton.harte-lyne.ca harte-lyne.ca >> # nameserver ::216:33 >> # nameserver ::216:34 >> # nameserver 127.0.0.1 >> nameserver 216.185.71.33 >> nameserver 216.185.71.34 >> options edns0 timeout:5 attempts:3 >> >> to this: >> >> # Generated by resolvconf >> search localdomain > > You need to add a line containing resolvconf=NO to /etc/resolvconf.conf. > > man 5 resolvconf.conf > Yeah this can get confusing, there are two config files - resolv.conf and resolvconf.conf and the command resolvconf. resolvconf reads resolvconf.conf to generate resolv.conf As suggested you can disable the generation of resolv.conf or you can adjust resolvconf.conf so that it generates resolv.conf the way you want. -- FreeBSD - the place to B...Software Developing Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6abf5488-84ac-186e-a244-5fca2ccf8533>