From owner-freebsd-questions Wed Dec 15 17:35:26 1999 Delivered-To: freebsd-questions@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-010.npt-sdsl.stargate.net [208.223.229.10]) by hub.freebsd.org (Postfix) with ESMTP id B218014BC9 for ; Wed, 15 Dec 1999 17:35:19 -0800 (PST) (envelope-from durham@w2xo.pgh.pa.us) Received: from w2xo.pgh.pa.us (shazam.internal [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id BAA08713; Thu, 16 Dec 1999 01:34:59 GMT Message-ID: <385841C3.89F356AC@w2xo.pgh.pa.us> Date: Wed, 15 Dec 1999 20:34:59 -0500 From: Jim Durham Organization: dis- X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Joakim Ryden Cc: Jim Durham , FreeBSD Questions Subject: Re: A Nameserver/Resolv.conf question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joakim Ryden wrote: > > Are you running DHCP on the FreeBSD box? The DHCP-client overwrites > resolv.conf each time it renews its lease. No, DHCP is handled by an NT server on the LAN. The rewrite was dated at 159am, the time of the "daily" scripts being run by "periodic". > > => Every day, upon firing up my workstation, I would find problems > => with TELNETing into the local server. I guessed that this was a > => nameserver > => problem. Upon looking at resolv.conf, I found that the IP of the > => local nameserver, the whole line, had been removed. The time of > => modification of the file was at the time the "periodic/daily" script > => ran. > => I could find no mention in the "daily" scripts of resolv.conf. The > => "daily" > => scripts daily e-mail message to "root" showed no errors. > => > => I fixed the problem by just eliminating resolv.conf and defaulting to > => the local nameserver, but what was modifying the resolv.conf file? -- Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message