-from the http side of view, it's ok to use name based vhosts -problem: accounting There is no software package to do an !reliable! accounting on a name-based basis, Accounting per IP works fine Possible solution is a sniffer. this requires an extra machine (and perhaps a second machine more for analyzing the collected data) and perhaps changes in the network layout. There is no software package to do this. -problem: bandwidth management Bandwidth management on an ip + service based environment is possible and not tooooo complicated. For the http part, there are some packages for apache, but they have not all features needed and you cannot manage badwith for other services than http. -problem: moving vhosts DNS is not fast enough, the possible solution with a redirect to a new www2-host doesnt work in all cases. So i think it is not possible to use only one ip per machine and doing only name based hosting. I think our way with one IP per customer (NOT per vhost) is an acceptable compromise. I won't be at the RIPE-Meeting. Could someone please point out a summary of our discussion? Greetings from Germany 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