Date: Fri, 29 Oct 2004 18:02:55 +0200 From: cpghost@cordula.ws To: Peter Ulrich Kruppa <root@pukruppa.de> Cc: freebsd-stable@freebsd.org Subject: Re: ppp -nat broken [solved] Message-ID: <20041029160255.GA783@bsdbox.farid-hajji.net> In-Reply-To: <20041029090017.I827@pukruppa.net> References: <20041026141721.X816@pukruppa.net> <20041029090017.I827@pukruppa.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 29, 2004 at 09:52:51AM +0200, Peter Ulrich Kruppa wrote:
> On Tue, 26 Oct 2004, Peter Ulrich Kruppa wrote:
> learn that named and BIND have changed. I did the respective
> changes and edited two entries in /var/named/etc/named/named.conf
> 1) I commented
> listen-on {127.0.0.1;};
Instead of opening a 53/tcp, 53/udp port to the world (ANYADDR),
you may prefer to restrict the address range to your internal LAN only,
with something like (replace 192.168.10.0/24 accordingly):
listen-on { 127.0.0.1; 192.168.10.0/24; };
Check with 'sockstat -46' to be sure.
> 2) I put my two nameserver IPs (from /etc/resolv.conf) into
> forwarders {
> 195.62.99.42;
> 195.62.97.177;
> };
They are not absolutely necessary: named is perfectly able to
query root and other servers itself. You could experiment with
or without forwarders, and pick the configuration that is faster
for you. As a general rule of thumb: Forwarders are good for
recursive queries, because only one query will travel through
your ADSL link, other queries being done by your ISPs nameservers.
They are also good, because you can profit from your ISPs nameservers'
cache. But they can hinder performance, should one or both of those
nameservers be down for whatever reason.
Cheers,
cpghost.
--
Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041029160255.GA783>