Date: 31 Mar 2006 14:18:41 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: fbsd_user@a1poweruser.com, freebsd-questions@FreeBSD.ORG Subject: Re: DHCPD config Message-ID: <44y7yqfmni.fsf@be-well.ilk.org> In-Reply-To: <20060331183758.66265.qmail@web52703.mail.yahoo.com> References: <20060331183758.66265.qmail@web52703.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Anderson <ciscoaix@yahoo.com> writes: > I think the answer you are looking for lies in > dhclient-script. I noticed it futzes with resolv.conf. > If you happen to notice resolv.conf changing (You can > test this about by making a backup of resolv.conf, > erasing its contents and then rebooting the machine, > just for the sake of everything running properly and > seeing if the contents of resolv.conf get repopulated > with your ISPs DNS settings) then you can create a > script to grab the elements needed from the ISP and > drop them in to a file for dhcpd to read and then > SIGTERM dhcpd and restart it. Basically, "have dhclient-script rewrite the dhcpd.conf". Running your own nameserver and pointing the internal DHCP clients to it is another option, but slightly less resistant to failures. Doing both will get you the best of both worlds.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44y7yqfmni.fsf>