Re: IP assignment for virtual webhosting

Hi Javier, why do you use an own POP3 and FTP for each customer/domain???? We are using the same POP3/FTP/SMTP for all customers. Of course you need individual Logins, you can solve this by naming them CUSTOMERNR-1, -2 and so on or by using DOMAINNAME-1, DOMAINNAME--2 and so on. For ftp, we do a CHROOT in the customers Webroot (=his home-dir). So where is the problem?? Henning Brauer Hostmaster BSWS ------------------------------------------------ BS Web Services Roedingsmarkt 14 20459 Hamburg Germany info@bsmail.de www.bsws.de fon: +49 40 3750357-0 fax: +49 40 3750357-5 PLEASE USE EMAIL WHERE POSSIBLE "Javier Llopis" To: "lir-wg@ripe.net" <lir-wg@ripe.net> <javier@bitma cc: iler.com> Subject: Re: IP assignment for virtual webhosting Sent by: owner-lir-wg@ ripe.net 11.05.00 13:41 Please respond to "Javier Llopis" On Mon, 08 May 2000 18:26:19 +0200, Nurani Nimpuno wrote:
We do however wish to raise our concern regarding what we see as an inefficient usage of addresses in our limited address pool. We would therefore like to request the community to consider making it mandatory for NEW installations to use domain based web-hosting, with the exception of a set of agreed applications needing IP based web-hosting (eg. SSL).
There is one issue I'd like to bring up that we constantly run into and was never brought up in this debate, which somehow amazes me. Our typical situation is that when a customer orders a domain named web site it comes along with an FTP server and a POP-3 server so they can have their own email addresses. While we could host all customer pages on the same host with the same IP using HTTP 1.1, in order to do the same with the POP servers we need to distinguish the POP server by its single IP address, since there is no HTTP 1.1 equivalent for POP. So we end up with 99% of our domains having a different IP address each, in which case who _cares_ if we also use that IP address for the web server? Are we really wasting IP address space? Hasn't anybody run into this situation? If so, how are you dealing with it? We would ask that, unless a viable solution to this problem is found, name based hosting should be encouraged but not required. BTW we are adopting HTTP 1.1 name based virtual hosts anyway in case the FTP and POP issues could be solved. Regards Javier Llopis BitMailer, S.L. javier@bitmailer.com Juan Bravo 51, Dup. 1-Izq Tel: +34 91 402 1551 28006 Madrid Fax: +34 91 402 4115 SPAIN

why do you use an own POP3 and FTP for each customer/domain???? We are using the same POP3/FTP/SMTP for all customers. Of course you need individual Logins, you can solve this by naming them CUSTOMERNR-1, -2 and so on or by using DOMAINNAME-1, DOMAINNAME--2 and so on. For ftp, we do a CHROOT in the customers Webroot (=his home-dir). So where is the problem??
We are also using one singel pop3 and smtp server for all customers, and also use the CHROOT solution for FTP accounts on un*x servers, however other FTP servers on other platforms (don't want to start an OS war here, but some of us do use IIS on NT for FTP :)) do not always support this mechanism. Has anyone solved this on NT? Perhaps by using different FTP server software? And I agree with Daniel that accounting is a very important issue here. Security is another one, firewalls being configured based on source and destination IP addresses. kind regards, Herbert -- Herbert Baerten HB5351 HostIT Network Manager NCC9166-RIPE

On Thu, May 11, 2000 at 04:09:45PM +0200, Herbert Baerten wrote:
And I agree with Daniel that accounting is a very important issue here. Security is another one, firewalls being configured based on source and destination IP addresses.
And another (although minor) point: you loose flexibilty. Situation: you want to move a bunch of domains hosted on server A to another server B because of system load or whatever. With name-based vhosting you have to do the usual DNS changes and wait for DNS convergency (DNS cache timeouts) to start the move. With IP-based vhosting you can act in minutes. Move config over to server B, take down IP on server A, activate IP on server B and you're set. This means in the name-based vhosting case i have about a week (usual RR TTL) before being able to react on the slashdot effect in contrary to IP-based vhosting where I'm able to react in minutes. I already saw several well known sites suffering from exactly THIS problem. Especially for companies like us with very limited upstream bandwidth. Best regards, Daniel Roesen Entire Systems NOC -- Entire Systems Network Operations Center noc@entire-systems.com Entire Systems GmbH - Ferbachstrasse 12 - 56203 Hoehr-Grenzhausen, Germany InterNIC-Handle: ES1238-ORG RIPE-Handle: ESN10-RIPE Tel: +49 2624 9550-55 GnuPG/PGP Key-ID: 0xBF3C40C9 http://www.entire-systems.com/noc/noc-key.asc GnuPG/PGP Fingerprint: 1F3F B675 1A38 D87C EB3C 6090 C6B9 DF48 BF3C 40C9

On Thu, May 11, 2000 at 04:27:27PM +0200, Daniel Roesen wrote:
This means in the name-based vhosting case i have about a week (usual RR TTL) before being able to react on the slashdot effect in contrary
Sorry, i meant "1 to several days". Daniel Roesen Entire Systems NOC -- Entire Systems Network Operations Center noc@entire-systems.com Entire Systems GmbH - Ferbachstrasse 12 - 56203 Hoehr-Grenzhausen, Germany InterNIC-Handle: ES1238-ORG RIPE-Handle: ESN10-RIPE Tel: +49 2624 9550-55 GnuPG/PGP Key-ID: 0xBF3C40C9 http://www.entire-systems.com/noc/noc-key.asc GnuPG/PGP Fingerprint: 1F3F B675 1A38 D87C EB3C 6090 C6B9 DF48 BF3C 40C9
participants (3)
-
Daniel Roesen
-
henning.brauer@bsmail.de
-
Herbert Baerten