[svlug] Re: Re: virtual domain names inside the LAN

[Tim]

On Tue, Aug 27, 2002 at 05:48:44PM -0700, Daevid Vincent wrote:
> > The very last idea that pops into mind is a wild speculation 
> > and I have never tried it - Apache has a proxy module. try to 
> > enable it and have lynx use it. maybe it's smart enough to 
> > reply to proxy requests for one of it's local alias hosts 
> > without going out and trying to get the packet translated by 
> > the router, since afterall it has access to the same config 
> > files. wild speculation, but has a good chance of working.
> 
> I think that would only work for web though right? 
> 
> I'd still have issues with mail @marq.org and @vrexhibits.com etc..
> Right?
> And also ssh/telnet/ftp and anything else.
> 
> I think after all you've explained that setting up BIND is the way to
> go, especially if it's not terribly difficult as you stated earlier.

Why not just make the Linux box running Apache the router/firewall?
That way when your internal machines try to connect to your external IP
address they'll connect directly to the Linux box.

Just add a second network card to the Linux box, connect eth0 to a
hub/switch for the local network, connect eth1 to the cable modem, set
up eth1 to retrieve an IP address via DHCP, setup dhcpd on eth0 such
that it gives eth0's IP address as the default gateway and your ISP's
DNS servers as the DNS servers, setup IP masquerading from the network
on eth0 to eth1, add firewall rules (iptables or ipchains) as necessary,
and you should be set.

  - Tim

P.S.  Sorry if you get this twice, Daevid.  I accidentally replied
      without CC'ing the list.