Date: Thu, 11 Jan 2007 08:56:19 +0200 From: "George Vanev" <george.vanev@gmail.com> To: questions@freebsd.org Subject: Re: Automatically get nameservers Message-ID: <6f4f57f60701102256o36adba6ap9617c787ed3242c6@mail.gmail.com> In-Reply-To: <44y7oay77l.fsf@be-well.ilk.org> References: <6f4f57f60701090556v35b55b2cn9bbcd363c588b002@mail.gmail.com> <45A3AD0A.1090600@vidican.com> <6f4f57f60701092249p65cc4a2bn40af47d6096f5918@mail.gmail.com> <44y7oay77l.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I set up my own caching nameserver. I used djbdns (dnscache). Some guys like it some not. Any opinion which is best (or at least very good) to use for caching dns On 1/10/07, Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote: > > "George Vanev" <george.vanev@gmail.com> writes: > > > I installed isc-dhcpd and it is working fine. > > But I don't want to hardcode the nameservers in the dhcpd.conf, > > because my ISP is changing them sometimes. > > It would be perfect if there is a way dhcpd to read the nameservers > > from /etc/resolv.conf > > Not exactly, but you can have the dhclient rewrite the dhcpd.conf when > it gets new nameservers. I used to do this; I ran it from > dhclient-exit-hooks, and it was a simple sed(1) command. For a long > time, I've been running my own local caching nameserver, and directing > the DHCP clients to that, but I could dig out my old script if you > have trouble with it. Although I would suggest you also consider > setting up your own local caching nameserver; the caching behaviour > can be a noticeable speed boost. > -- George Vanev Information Systems Specialist tel.: +359 898 44 25 37
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6f4f57f60701102256o36adba6ap9617c787ed3242c6>