From owner-freebsd-hackers Mon Feb 19 10:58:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA15406 for hackers-outgoing; Mon, 19 Feb 1996 10:58:19 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA15399 for ; Mon, 19 Feb 1996 10:58:11 -0800 (PST) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id UAA03195; Mon, 19 Feb 1996 20:56:55 +0200 Date: Mon, 19 Feb 1996 20:56:55 +0200 (EET) From: Narvi To: me@gw.muc.ditec.de cc: hackers@freebsd.org Subject: Re: An ISP's Wishlist... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk On Mon, 19 Feb 1996, Michael Elbel wrote: > In lists.freebsd.hackers you write: > > >David Muir Sharnoff stands accused of saying: > >> > >> It would be very nice to be able to have a separate configuration for > >> each port that named might bind to. There are times when I want to > >> serve different information to different nets. This is particularly > >> handy when building firewalls. > > >That definitely falls into "you have the source" 8) > > I've done this, it wasn't too difficult. I'm now running three > nameds on our firewall bastion, one to serve the inside network > with everything on the outside hidden and a wildcard MX-record > pointing to the mail relay machine, one to serve the outside > with all internall stuff hidden and an MX-record also pointing > to the mail relay and a third listening on 127.0.0.1 for the > bastion itself that has info about both the in- and the outside. > > Works like a charm. If there's enough interest, I can make that > available. > > Michael > > -- > Michael Elbel, DITEC, Muenchen, Germany - me@muc.ditec.de > Fermentation fault (coors dumped) > It would be really useful. Perhaps times will come when people port things *from* FreeBSD? Cheers, Sander.