Date: Fri, 5 Jan 2001 10:22:41 -0800 From: Keith Walker <kew@icehouse.net> To: Cliff Sarginson <cliff@raggedclown.net>, Nick Slager <nicks@albury.net.au>, freebsd-questions@FreeBSD.ORG Subject: Re: Using BIND in a local, bogus network Message-ID: <01010510224103.01946@mars.walker.dom> In-Reply-To: <E14ERy2-0004Ea-00@post.mail.nl.demon.net> References: <E14ERy2-0004Ea-00@post.mail.nl.demon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 05 January 2001 12:11 am, Cliff Sarginson wrote: > > 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. > > > [ ... ] > > > 1) How come the named program keeps dialing out? > > My prime candidate for this is my MTA. Oh heck. I *think* I figured this whole thing out. Between a very good private response from a "Bill" guy, and my discovering a running daemon that was screwing things up, I've got the whole thing working. My errant daemon was ntpd. I didn't think of this because when I was using off-site nameservers, the anti-dial lines in the ppp.conf file would keep everything in check. But now with a local nameserver, while the ntp packets were blocked, the name lookup would wake up the nameserver, which would force the dial out. So, it's back to ntpdate periodically instead of the constantly running ntpd. > > This must be solvable ! > Yep, I think so! At least I hope I've got it. -- Keith Walker kew@icehouse.net PGP Key: http://www.icehouse.net/kew/public-key.pgp 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?01010510224103.01946>