Thank you all so much for the quick response. Jeff Higgins presented to
me a copy of a previous summary (before I signed-up). I suppose there
are, like me, those who read and archive the summaries (just in case, I
ever need it--I'm a pack-rat). Here it is...
How to Set-up a virtual host and configure httpd to read it.
Sam Washburn
Toccoa Falls Internet Services
Systems Administrator
<samw_at_toccoafalls.edu>
On Wed, 31 Jul 1996, Jeff Higgins wrote:
>
> Here's the summary I sent after I asked a similar question. The first part
> deals with setting up the second IP address in ifconfig; the second is more
> about virtual hosting. There are a couple Web pages referenced, too, which I
> found helpful. Virtual hosting is quite common, and I know you'll find out
> plenty about it! Also a number of retail books are now available on setting up
> servers; they include virtual hosting information.
>
> Good luck!
>
>
> Date: Fri, 07 Jun 1996 13:52:37 -0500 (EST)
> From: Jeff Higgins <HIGGINS_at_aces.k12.ct.us>
> Subject: SUMMARY: Specify interface for ifconfig
> Sender: alpha-osf-managers-relay_at_sws1.ctd.ornl.gov
> To: alpha-osf-managers_at_ornl.gov
> Precedence: bulk
> Followup-to: poster
>
> I see why people consistently marvel at the lightning-fast responses from this
> group! Many thanks to all who replied. I've acknowledged you below.
>
> My question was how to determine the name of my network interface so that I
> could specify it in ifconfig. I also wondered if anyone else had set up two
> independent web sites with different http servers on the same Alpha.
>
> The basic solution was to use netstat -i. This displays the interfaces. Common
> interface names are ln# (DEC Lance interface) and tu# (DEC Tulip interface).
> SLIP (sl#) and loopback (lo#) interfaces will also be displayed. There are two
> other ways to get the answer:
>
> - Display /etc/rc.config, where NETDEV_# is defined as ln# or tu#.
> - Display /var/adm/messages, which contains many of the messages, including
> configuration, that appear during boot.
>
> My command turned out to be #ifconfig tu0 my.new.ip.address alias
>
> As for setting up the additional Web site under a new http server, two of the
> suggestions I recieved are below. The suggestions by some to run the second
> server on a different port is contested in
>
> http://www.thesphere.com/~dlp/TwoServers
>
> which explains that the only way to make that work is to include the port
> number in the URL, as DNS will not return port numbers with host lookup.
>
> MULTIPLE SITE/ONE MACHINE SUGGESTIONS:
>
> From: Steve McLaughlin (mclaughl_at_nssdc.gsfc.nasa.gov)
>
> I've setup a few of these. Here' the basics:
>
> 1) Have your DNS people add another ip and name to your harware address.
>
> 2) Setup the following /etc/rc.config entries:
>
>
> NUM_NETCONFIG="2" /* default is one */
>
> NETDEV_0="ln0" /* default */
> NETDEV_1="ln0" /* add this one */
>
> IFCONFIG_0="128.183.101.62 netmask 255.255.0.0" /* first ip */
> IFCONFIG_1="128.183.101.63 netmask 255.255.0.0" /* virtual ip */
>
> /* reboot and changes will configure */
>
>
> 3) Add the following to the ~httpd/httpd.conf:
>
> <VirtualHost 127.0.0.1 Optional> /* default */
> DocumentRoot /ncf/bolero/pub/www
> ServerName localhost.ncsa.uiuc.edu
> ResourceConfig conf/localhost_srm.conf
> </VirtualHost>
>
>
> <VirtualHost 128.183.101.63 > /* virtual server */
> DocumentRoot /ncf/bolero/pub/www
> ServerName ssdoo.gsfc.nasa.gov
> ResourceConfig conf/nasa_srm.conf /* note the different srm.conf */
> </VirtualHost>
>
>
> 4) Setting DirectoryIndex
>
> 4a) in srm.conf: DirectoryIndex index.html
>
> 4a) in nasa_srm.conf: DirectoryIndex virtual.html
>
>
> Steve Mclaughlin
> mclaughl_at_nssdc.gsfc.nasa.gov
>
>
>
> From: Peter Bivesand <PetBi_at_UNIT.LiU.SE>
>
> I'm running that kind of setup without any problems, I even use different
> http-servers on the same machine. Make sure you have configured your
> ethernet-card with ifconfig and that the ip-number you use is registered
> with a A-record in your DNS. It should look something like this:
>
>
> bive.unit.liu.se. IN NS styra.lidac.liu.se.
> www IN A 130.236.10.70
> IN MX 5 mailgw.liu.se
> IN HINFO ALHPA OSF1
>
> This setup makes my machine (styra.lidac.liu.se) answer to requests to
> www.bive.unit.liu.se.
> Then you have to configure your www-server. I use Apache (www.apache.org),
> Spinner (www.infovav.se) and Netscape Commerce Server (www.netscape.com).
> The configuration differs a little from server to server, but it very well
> documented in the packages. I recomend Apache, very fast, reliable and
> easy to add different virtual servers.
> This is basics of it. Read the documentation to the servers and you should
> be up and running within the hour.
> Good luck!
>
> Thanks again to everyone who responded!!:
>
> Anonymous <root_at_vepdl.vafb.af.mil>
>
> Gernot M. Fuchs <gfuchs_at_golay.med.unc.edu>
>
> R. Kevin Oberman (oberman_at_es.net)
>
> Walt Melton (wmelton_at_iii.com)
>
> Knut Helleboe (Knut.Hellebo_at_nho.hydro.com)
>
> Yvon Lauriault <Yvon_at_InfoServ.nlc-bnc.ca>
>
> Mark E. Glidden <glidden_at_harvard.edu>
>
> Steve Weber <sweber_at_mr.picker.com>
>
> Norbert Kasperczyk-Borgmann <nkb_at_informatik.fh-hamburg.de> |
>
> Steve Mclaughlin <mclaughl_at_nssdc.gsfc.nasa.gov>
>
> Peter Bivesand <PetBi_at_UNIT.LiU.SE>
Received on Thu Aug 01 1996 - 19:24:35 NZST