[rabbitmq-discuss] RabbitMQ on EC2

Kyle Salasko ksalasko at gmail.com
Fri Mar 14 05:49:44 GMT 2008

Scratch that, I found a solution. An easy workaround is to find the internal
(inside the NAT) IP address of any nodes with the domU-... hostnames, and
construct the ip-... hostnames from that. For example, Node A from below
might resolve to, and by manually running 'hostname
ip-10-252-56-111.ec2.internal', the problems below resolve themselves.

The problem seems to arise from the fact that the machines can resolve the
first three of the following names, but not the fourth.


This probably should be automated in AMI creation, but I thought I'd let
people know in case they run into the same problems.

View this message in context: http://www.nabble.com/RabbitMQ-on-EC2-tp16042914p16044743.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list