From owner-freebsd-questions  Tue Nov  5 10:27:08 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA14994
          for questions-outgoing; Tue, 5 Nov 1996 10:27:08 -0800 (PST)
Received: from brimstone.gage.com (brimstone.gage.com [205.217.2.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14988
          for <questions@freebsd.org>; Tue, 5 Nov 1996 10:27:05 -0800 (PST)
Received: (from mail@localhost) by brimstone.gage.com (8.8.2/8.7.3) id MAA00580; Tue, 5 Nov 1996 12:25:56 -0600 (CST)
Received: from octopus.gage.com(158.60.57.50) by brimstone.gage.com via smap (V2.0beta)
	id xma000578; Tue, 5 Nov 96 12:25:45 -0600
Received: from squid.gage.com (squid [158.60.57.101]) by octopus.gage.com (8.7.5/8.7.3) with SMTP id MAA08603; Tue, 5 Nov 1996 12:19:44 -0600 (CST)
Received: from schemer by squid.gage.com (NX5.67e/NX3.0S)
	id AA26781; Tue, 5 Nov 96 12:27:00 -0600
Message-Id: <9611051827.AA26781@squid.gage.com>
Received: by schemer.gage.com (NX5.67g/NX3.0X)
	id AA00741; Tue, 5 Nov 96 12:27:03 -0600
Mime-Version: 1.0 (NeXT Mail 4.0 v146.2)
Content-Type: multipart/alternative; boundary=NeXT-Mail-1438490562-3
Content-Transfer-Encoding: 7bit
In-Reply-To: <327F3B96.72EC@degnet.baynet.de>
X-Nextstep-Mailer: Mail 3.3 (Enhance 1.3)
Received: by NeXT.Mailer (1.146.2)
From: Ben Black <black@gage.com>
Date: Tue,  5 Nov 96 12:27:03 -0600
To: moos@degnet.baynet.de
Subject: Re: how to: ip aliases
Cc: dwhite@resnet.uoregon.edu, FreeBSD-questions <questions@freebsd.org>,
        aricio1@srv1-bsb.bsb.nutecnet.com.br
References: <Pine.BSI.3.94.961104231317.5689I-100000@gdi.uoregon.edu>
	<327F3B96.72EC@degnet.baynet.de>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

--NeXT-Mail-1438490562-3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

>You can do this without IP-aliasing. When it is acceptable, that the
>virtual domain is a CNAME to your own domain. This requires some
>configuration to the nameservices.
>

and browser support for it.  this is not currently the best solution.


b3n

--NeXT-Mail-1438490562-3
Content-Type: text/enriched; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<smaller>>You can do this without IP-aliasing. When it is acceptable, that
the
<nofill>
>virtual domain is a CNAME to your own domain. This requires some
>configuration to the nameservices.
</smaller>>

and browser support for it.  this is not currently the best solution.


b3n
</nofill>
--NeXT-Mail-1438490562-3--