Cannot get multiple domains to work off one VM server with one IP address using EC2 and DNS

The problem I am having is that every time I have tried to create an additional virtual server (using VM: Create Virtual Server) it has messed up the main one (which is working fine)! Just to be clear (because there are many different uses of web server termingology): I want one externallyy addressable (Elastic) IP address to host many web sites on one VM EC2 instance (an Amazon virtual server).

I am struggling to find any clear instructions on how to set this up - specifically for EC2. The IP address, the virtual interface, External IP address, and DNS configuration are confusing me - especially as Amazon has its own internal DNS!

We are using VM Pro on EC2 (NOT AMI version: we used the GPL version and upgraded to Pro via VM interface). CentOS (standard repo). BTW I don't think the problem is anything to do with GPL/Pro, because I couldn't get it to work in the GPL version either. In fact this was one of the reasons we chose to upgrade to Pro - to see if the Pro version would work with multiple domains - but we're having exactly the same problem!

We have two IP addresses (Elastic) which we use for NS1 & NS2, but for now I am only trying to get virtual servers to run off one IP address on one instance - I'll worry about master/slave/s virtual servers later!

We have configured our own DN servers using 2 EC2 instances and their respective Elastic IP addresses. This is working fine. The slave gets automatically updated.

Am I right in assuming that all domains (web sites) can have the same external IP address?

Every time we terminate an instance and create a new one (happens quite often while we build up the full stack with master/slave/s, redundancy, EBS, S3, etc.) - the master server using Amazon's DHCP is allocated a new IP address (naturally enough). However, when I check the existing server it has the old DHCP IP address in. Confusing! Not sure if this is a problem...?

Using eth0:1 for virtual IP address.
The first virtual server works fine. intodns is all clear apart from serial number - "Looks like your nameservers do not agree on the SOA serial. Ths SOA records as reported by your nameservers:
174.129.192.147 -> 1243646782
79.125.11.180 -> 1243826765
This can cause some serious problems that is why you should fix this asap."
Not sure is this is connected with the multiple domain problem I'm having or what to do about this?

Any help would be much appreciated.

I think if you can get this to work automatically, or at least have some very idiot-proof instructions on how to set up multiple domains on EC2 instances - then I think your software sales will soar - because I don't think there are any competitors even offering AMIs (one reason why we chose VM in the first place). But it has to be as EASY as possible...

Status: 
Closed (fixed)

Comments

Hello, have you found a solutions?

Please, can you share?

Thanks in advance.

Hi Davide -- can you describe specifically what problem you're having, and what symptoms you're seeing?

In the above, it sounds like in the Apache config file, the "NameVirtualHost" line was commented out, whereas it needed to be in the config and active. But, it's rare that this would happen.