From owner-freebsd-isp Wed Dec 16 10:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21416 for freebsd-isp-outgoing; Wed, 16 Dec 1998 10:26:48 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from hecate.webcom.com (hecate.webcom.com [209.1.28.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21411 for ; Wed, 16 Dec 1998 10:26:47 -0800 (PST) (envelope-from graeme@echidna.com) Received: from eresh.webcom.com (eresh.webcom.com [209.1.28.49]) by hecate.webcom.com (8.9.1/8.9.1) with SMTP id KAA06437; Wed, 16 Dec 1998 10:26:36 -0800 Received: from [209.122.117.150] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 15669082; Wed Dec 16 10:24 PST 1998 Message-Id: <3677FB7E.7C08@echidna.com> Date: Wed, 16 Dec 1998 13:27:10 -0500 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win95; I) Mime-Version: 1.0 To: Michiel Boland Cc: Troy Settle , "(ML) FreeBSD ISP" Subject: Re: Aliased IPs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michiel Boland wrote: > > Hi. > > > Hey all, > > > > As our web hosting business grows, I'm finding myself aliasing more and > > more IP addresses to accomodate. FreeBSD and apache are holding up like > > champs, but my local routing tables are getting a little big. > > I can't answer your specific problem but I feel I must react to what you > are doing here. :) > > Personally, I don't use apache, but it should not be a problem in the > latest apache versions to add virtual hosts that share an IP address with > other servers. This will save you from the problems you are experiencing > now + it will also save a lot of valuable IP address space. I use one host that has well over 10,000 domains served from one machine with all mapped to a single IP. It's a great idea in principle, but when you use it on any scale, you can run into problems. Here are some of the downsides: Some search engines won't list sites from this host - they treat the multitudinous submissions with multiple hostnames resolving to one IP as SPAMming. Others have taken similar action in the past, and had to be persuaded to reverse their restriction. Access control software is often set to ban on IP address. It only takes one bad apple to get you banned, and often banning is done on commonplace material (like corporations restricting access to sports sites). For sensitive categories (like access for children), fairly innocent material can lead to banning. In one case Switzerland mandated the banning of the the entire server mentioned above from its ISP's, because of one site with racist content. Reverse lookups don't resolve to the correct hostname. Some users, especially resellers, are concerned that this happens, as it "blows their cover". And there's the occasional browser that doesn't pass the host header required for this form of virtual hosting. -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message