This is more of a feature request than anything. We have an external bandwidth manager box (doesn't everybody? ) that works great. Just one problem. For simplicity's sake, we'd like to be able to bandwidth limit a reseller and all of his domains with one bandwidth limit rule on our bandwidth manager box. We believe that instituting bandwidth management on an external box is the most flexible and scalable method (vs some of the bw limiting modules you can get for Apache and etc.) To do this, all domains for that reseller (the "client") would have to point to a single IP and each reseller would have to have their own unique IP. Its not hard to do by hand (just time consuming when dealing with hundreds of domains), but that would defeat the whole reason we bought plesk - automation! At present (v2.5), Plesk will only do name based hosting on the main IP of the server. I've checked all the documentation at the Apache site regarding name based hosting and I know it is possible to configure Apache to do name based hosting on any active IP in the system. It's all pretty straightforward. A relatively simple interface change of the domain creation pages (or the domain's "hosting" settings page) would allow us to do this. Instead of forcing all name based hosts to point to the main server IP, simply put a text box IP entry field right next to the name based hosting radio button so that we can define what IP is sending and receiving traffic for that domain. To encourage our resellers to properly point their domains to something other than the main server IP, we'd institute a restrictive bandwidth rule for the main IP of the server. Of course, we'd love it if there was a way to default that field to be the first dedicated IP assigned to a particular client, but that would not be 100% necessary to get our bandwidth management scheme working. Anyone else think this is a good idea? If so, forward the URL to this thread to the Plesk support department so that they know that I'm not the only one that wants this functionality. Andrew PS Another alternative is to just use a wildcard in the NameVirtualHost directive of /usr/local/psa/apache/conf/httpd.conf and let DNS determine which IP gets the traffic for that domain. This still requires that plesk write out the virtualhost directive for name based sites with a wildcard instead of the IPort format they're currently using. I've tried just using NameVirtualHost * in the httpd.conf, but since PSA insists on writing specific IP and port information in every name based virtualhost directive, it doesn't match properly and the site won't come up on any other IP but the one configured in the VirtualHost directive. If the virtualhost directive format for name based sites (and only name based sites) was changed from: <VirtualHost IPort> to <VirtualHost *> then using the NameVirtualHost wildcard would allow you to use DNS to point name based sites to any valid IP on the server and the site should function, thereby allowing resellers to be bandwidth limited by the dedicated IP assigned to their main site and solving a common problem that PSA users face - bandwidth management.