From owner-freebsd-net  Mon Jun 12 21: 7:40 2000
Delivered-To: freebsd-net@freebsd.org
Received: from rapidnet.com (rapidnet.com [205.164.216.1])
	by hub.freebsd.org (Postfix) with ESMTP id F026A37B923
	for <freebsd-net@FreeBSD.ORG>; Mon, 12 Jun 2000 21:07:36 -0700 (PDT)
	(envelope-from nick@rapidnet.com)
Received: from localhost (nick@localhost)
	by rapidnet.com (8.9.3/8.9.3) with ESMTP id WAA94990;
	Mon, 12 Jun 2000 22:07:35 -0600 (MDT)
Date: Mon, 12 Jun 2000 22:07:34 -0600 (MDT)
From: Nick Rogness <nick@rapidnet.com>
To: "Chutima S." <chutima_s@zdnetonebox.com>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: How to: Web service for other website.
In-Reply-To: <20000613031556.GKL29121.mta02@onebox.com>
Message-ID: <Pine.BSF.4.05.10006122154560.90094-100000@rapidnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Mon, 12 Jun 2000, Chutima S. wrote:

> My company will release web service on internet to other websites.
> Where can I find technology issue about it?  

	What do you mean by this?  Are customers dialing up to your
	service or what?  Are you host web server space?  Clarify.

> Such as:
> 1. I know that we can apply DNS to load balancing (round robin).
> But I like to know can I apply DNS to fault tolorence(if one of 
> our server die all request from customer websites will connect
> to the rest of our servers)? 

	What type of remote-access gear are you using?  In most types
	you can setup a primary name server and a secondary (backup)
	server within your gear.  Cisco's allow multiple 'ip name-server'

	Setup multiple nameservers that are authoritative for your
	domains.

	Setup a 'cluster' of machines.

> 2. Our webserver will service several customer websites.  How 
> can I use difference URL for each customer website?

	Apache virtual hosts.  Set this up in your web server.


> 3. How can I protect my webserver from other website or browser
> that is not my customer website? (Someone talk about relay URL.)
> 

	This is also setup in your web server.  You can setup allowable
	hosts:

	<location /path_to_your _website>
	Deny from all
	Allow from .your_domain.com
	</location>

	Or you can setup firewall rules:

	ipfw add 2000 allow tcp from your_ip_range to your_web_server 80
	ipfw add 2001 deny tcp from any to your_web_server 80
	
	I don't know exactly what you are asking so I can't be more
	specific...sorry.


Nick Rogness
- Speak softly and carry a Gigabit switch.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message