multiple ips/apache vhost setup

[RDWest2005]

Hello guys,
I'm pulling my hair out here.
I've never had over 1 ip to use over the years. Now I have colo-ed and have 13 ip addresses. I'm not doing something right in apache. I'm getting the wrong site for a differentt ip etc.

Here is my order of includes...

Listen zzz.zzz.zz.zz:80
Listen yyy.yyy.yyy.yyy:80

NameVirtualHost zzz.zzz.zz.zz:80
NameVirtualHost yyy.yyy.yyy.yyy:80

<vhost1 zzz.zzz.zz.zz:80>
servername name.com

<vhost2 yyy.yyy.yyy.yyy:80>
servername name.com

<vhost3 yyy.yyy.yyy.yyy:80>
servername name.com

<vhost4 yyy.yyy.yyy.yyy:80>
servername name.com

My thinking is run as many one ip as shared
and assign certain ips to other domains that needs SSL

I need to run around 20 on a shared ip and 2 others on dedicated...
Can someone point me in the right direction for this setup?

any suggestions on what i'm doing wrong?
Thanks,
~RD

[edited by: RDWest2005 at 9:50 pm (utc) on Feb. 16, 2008]

[gergoe]

Your directives (after reformating):

# 
# Make Apache listen on the proper ip addresses and ports 
Listen zzz.zzz.zz.zz:80 
Listen yyy.yyy.yyy.yyy:80 
# 
# Define which ip address and port combinations will need name based virtual hosting enabled. When enabled and Apache receives a request, it tries to match the http Host header with the ServerName and ServerAlias directives from each VirtualHost, when failed, it will match it to the first VirtualHost in the "group". When it is disabled, the Apache will not do any matching, it will serve the request using the (hopefully) only one VirtualHost in the "group". With the "group" I mean one or more VirtualHosts which are bound to the same ip address and port combinations. 
NameVirtualHost zzz.zzz.zz.zz:80 
NameVirtualHost yyy.yyy.yyy.yyy:80 
# 
# Default name based virtual host (group 1): example1.com 
<VirtualHost zzz.zzz.zz.zz:80> 
ServerName example1.com 
</VirtualHost> 
# 
# Default name based virtual host (group 2): example2.com 
<VirtualHost yyy.yyy.yyy.yyy:80> 
ServerName example2.com 
</VirtualHost> 
# 
# Name based virtual host (group 2): example3.com 
<VirtualHost yyy.yyy.yyy.yyy:80> 
ServerName example3.com 
</VirtualHost> 
# 
# Name based virtual host (group 2): example4.com 
<VirtualHost yyy.yyy.yyy.yyy:80> 
ServerName example4.com 
</VirtualHost> 

This will do the following:

1. Serve any requests coming through the zzz.zzz.zz.zz ip address from the example1.com virtualhost (even if the name does not match);
   
2. Serve requests for example4.com if coming through yyy.yyy.yyy.yyy ip address from the example4.com virtualhost;
   
3. Serve requests for example3.com if coming through yyy.yyy.yyy.yyy ip address from the example3.com virtualhost;
   
4. Serve any requests coming through the yyy.yyy.yyy.yyy ip address from the example4.com virtualhost (even if the name does not match);
   

If you intended to "bind" only one virtualhost (website) to the zzz.zzz.zz.zz ip address, then the NameVirtualHost zzz.zzz.zz.zz:80 is not needed. If you want to use more than two ip addresses (while keeping some reserved for certain websites, or ssl enabled websites), then you can add more (shared) name based virtualhosts as in the case of example[2-4].com, while the dedicated ones could look like the first virtualhost. For more information see the Apache Virtual Host documentation [httpd.apache.org]