/etc/resolv.conf getting over written with dhcp
Teske, Devin
Devin.Teske at fisglobal.com
Fri Jun 15 13:51:39 UTC 2012
On Jun 15, 2012, at 5:47 AM, Volodymyr Kostyrko <c.kworr at gmail.com> wrote:
> Varuna wrote:
>> Hello Folks,
>>
>> Noticed a strange issue with the creation / update of /etc/resolv.conf.
>> The details of the system that I noticed the issue on is:
>> Version : FreeBSD 8.0
>> Patch level: not patched
>> Uname: FreeBSD shastry.eudaemonicsystems.net 8.0-RELEASE FreeBSD
>> 8.0-RELEASE #0: Thu Sep 29 22:37:51 IST 2011
>> root at shastry.bhuta.in:/usr/obj/usr/src/sys/SHASTRY i386
>>
>>
>> I generally have a static IP 192.168.98.6 (via rc.conf) for my Beastie.
>> The contents of my /etc/resolv.conf is as follows:
>> domain eudaemonicsystems.net
>> nameserver 208.67.222.222
>> nameserver 208.67.220.220
>> nameserver 4.2.2.2
>> No matter how many times I reboot the system, the resolv.conf does not
>> get overwritten when configured with a static IP.
>
> 1. Since 9.0 we already have resolveconf(8) for this.
> 2. Empty dhclient.conf means default configuration, you can make your own, refusing nameserver updates coming from DHCP.
> 3. You can always chflags noschg any precious file.
>
schg to disallow changes.
noschg is incorrect.
--
Devin
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
More information about the freebsd-hackers
mailing list