[49877] in North American Network Operators' Group
Re: Question regarding web hosting ip addressing
daemon@ATHENA.MIT.EDU (Scott Francis)
Thu Jul 11 16:33:09 2002
Date: Thu, 11 Jul 2002 13:29:20 -0700
From: Scott Francis <darkuncle@darkuncle.net>
To: Martin Hannigan <hannigan@fugawi.net>
Cc: nanog@merit.edu
Mail-Followup-To: Scott Francis <darkuncle@darkuncle.net>,
Martin Hannigan <hannigan@fugawi.net>, nanog@merit.edu
In-Reply-To: <5.0.2.1.0.20020711162023.01848ef0@ns1.outland.net>
Errors-To: owner-nanog-outgoing@merit.edu
--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jul 11, 2002 at 04:22:53PM -0400, hannigan@fugawi.net said:
>=20
>=20
>=20
> Folks, could use some pointers.
>=20
> I seem to remember from experience some years ago that if you were
> hosting multiple domains for web hosting in a shared environment that
> they needed to have individual IP numbers assigned specifically to the
> domain, all sharing the interface, so things like AOL browser, etc.
> would all work properly.
I haven't heard of any problems with virtual hosting and client-side
browsers. The only caveat I'm aware of is that SSL-enabled virtual hosts
(i.e. https://foo.bar.bz) must have a unique IP per host, due to the nature
of SSL and certificates.
> Am I out of date on this, or is it still common practice to assign a sing=
le
> ip number to a single web hosted domain i.e.
>=20
> hme0/1.2.3.1/www.test1.com
> hme0/1.2.3.2/www.test2.com
>=20
> ...and so on and so forth?
Only for SSL vhosts. Otherwise, there are no problems (well, very few anywa=
y)
that I am aware of in using a single IP to host as many vhosts as physical
resources will allow.
I'm quite certain somebody will correct me if I've missed something. :)
--=20
-=3D Scott Francis || darkuncle (at) darkuncle (dot) net =3D-
GPG key CB33CCA7 has been revoked; I am now 5537F527
illum oportet crescere me autem minui
--DocE+STaALJfprDB
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE9LeqgWaB7jFU39ScRAtCUAKCu/hsvvO88FqNhYNsh33UXJ6lNBQCgpYtw
nu9+q8T+FyNKNo86gJMvb7M=
=eKxA
-----END PGP SIGNATURE-----
--DocE+STaALJfprDB--
