The ability to create Virtual Domains in APACHE is a beautiful thing. There should be
something in the Linux Documention about this subject.
Barry Treahy wrote:
> You're saying that if I have:
>
> www.xxx.com
> www.yyy.com
> www.zzz.com
>
> all resolving to the same IP address 192.168.1.1
>
> that Apache knows which virtual server to use and therefore which real file system to
> service from when Joe Shmoe comes along and points his broswer to www.yyy.com?
>
> I'd like to know how that is configured, because obviously I've missed it some how
>become
> I'm not talking about www.yyy.com/~someuser stuff...
>
> Thanks!
>
> Barry
>
> Sean A. Walberg wrote:
>
> > That works because on the http layer the server name is specified. This
> > functionality is not provided on lower layers.
> >
> > Also, apache can do name based virtual servers even easier than that, as
> > there is no need to run sepearate ports or anything.
> >
> > Sean
> >
> > On Wed, 2 Jun 1999, Barry Treahy wrote:
> >
> > >
> > > One possible reason is to host multiple domains off one IP and still be able to
>offer
> > > unique web sites, which is what I've done for home... I have a simple perl
>script
> > > and html page that is used to detect the incoming URL and then dispatches to the
> > > domain (still the same domain & IP) and proper IP port (for that domain) which
>the
> > > port could be set to pass into the internally masqed LAN using tools like TIS
>plug-gw
> > > and others I'm sure...
> > >
> > > Barry
> > >
> > > David A. Ranch wrote:
> > >
> > > > >What I want to know is is there a way to give the internal clients a name in
> > > > >my DNS server, and the Masq Machine can somehow see what NAME not IP ADDRESS
> > > > >the request is for and forward it to one of the internal clients. I only
> > > > >have one IP address (from the cable modem), so I don't know if this is
> > > > >possible. Please let me know. Thanks!
> > > >
> > > > I don't see what this would gain you. If you can explain your idea
> > > > maybe there is an alternative way.
> > > >
> > > > Regardless, this way isn't possible. TCP/IP doesn't work that way.
> > > > Things go from NAME to TCP/IP address to MAC address. Always.
> > > >
> > > > --David
> > > > .----------------------------------------------------------------------------.
> > > > | David A. Ranch - Linux/Networking/PC hardware [EMAIL PROTECTED] |
> > > > !---- ----!
> > > > `----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
> > > >
> > > > _______________________________________________
> > > > Masq maillist - [EMAIL PROTECTED]
> > > > http://tiffany.indyramp.com/mailman/listinfo/masq
> > > > Admin requests can be handled by web (above) or
>[EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Masq maillist - [EMAIL PROTECTED]
> > > http://tiffany.indyramp.com/mailman/listinfo/masq
> > > Admin requests can be handled by web (above) or [EMAIL PROTECTED]
> > >
> >
> > -------------------------------------------------------------------
> > Sean Walberg <[EMAIL PROTECTED]> http://come.to/the_dark_side
>
> _______________________________________________
> Masq maillist - [EMAIL PROTECTED]
> http://tiffany.indyramp.com/mailman/listinfo/masq
> Admin requests can be handled by web (above) or [EMAIL PROTECTED]
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
