Date: Wed, 11 Apr 2001 22:26:57 -0400 From: Leonard Zettel <zettel@acm.org> To: "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG> Subject: resolv.conf overwrite Message-ID: <3AD51271.25615AEB@acm.org>
next in thread | raw e-mail | index | archive | help
Following The Complete FreeBSD p 480 I created the following /etc/resolv.conf # Changed by Len Zettel 4/11/01 #----------removed------------- # search # nameserver 192.168.0.185 # ------------------------------ # ---------Added--------------- domain Oz. nameserver 204.254.120.6 # Bignet primary nameserver nameserver 204.254.120.7 # Bignet secondart nameserver #------------------------------------------------------ I was then happy as a clam at high tide at being able to ping domain names on the net. :-) This looked like PROGRESS! (One step at a time division). Then I rebooted :-( /etc/resolv.conf now contained search nameserver 192.168.0.185 Tentative conclusion: something in the boot sequence is fooling with (probably creating) /etc/resolv.conf So, what do I change to stop this? Or should I not be trying to stop it? And doing something else entirely? And where can I read about THAT? My access to the net is via DSL with a Windows machine as gateway running a package calle SyGate. (Yes, technically DUMB, DUMB, DUMB) except for one thing: it works. Even I got it working. When (not IF, optimist that I am) I get Free BSD running well under this setup we'll work on changing it. Hopefully a step at a time. Thanks for reading. -LenZ- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AD51271.25615AEB>