Date: Fri, 5 Jan 2001 17:07:44 +1100 From: Nick Slager <nicks@albury.net.au> To: Keith Walker <kew@icehouse.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Using BIND in a local, bogus network Message-ID: <20010105170744.A66041@albury.net.au> In-Reply-To: <01010418384900.00606@mars.walker.dom>; from kew@icehouse.net on Thu, Jan 04, 2001 at 06:38:49PM -0800 References: <01010418384900.00606@mars.walker.dom>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Keith Walker (kew@icehouse.net): > In my perfect world, the firewall would have a named running that would be a > domain master for the bogus network, would cache "real" addresses, and just > generally, DTRT. > > I've had *some* success with this, but I cannot get the nameserver to quit > forcing dial-outs, keeping the modem connected almost 24/7. > > Ok, so: > > 1) How come the named program keeps dialing out? > 2) How can I prevent this? > 3) Are nameservers designed to run only on full time systems? > 4) Is there a better way of doing this? You might want to look into userland PPP's filters to stop the auto dial on DNS lookups. Have a look at the examples in /usr/share/examples/ppp. Nick -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." 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?20010105170744.A66041>