
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