Amazon EC2 Help

[LaughingBuddhaIT]

Hi,

I'm a UK service provider, and I've been running a dedicated server (my own hardware) since 2008, and various VPS boxes from 2005 to 2009. I've recently looked into Amazon EC2 for some projects I'm developing which will need to scale rapidly, and set-up a micro instance using CentOS 6.3 64bit installing Plesk 11 (latest build) on it. I set-up the usual elastic IP to the instance, and pointed a sub-domain to it so it would resolve correctly.

Now here's my thing, it really is sluggish. It takes a good 40-60 seconds to resolve the sub-domain to the server using the browser. Has anyone else experienced this?

And before the Plesk admins jump in pointing me to the knowledge base file for Plesk 11 AMI I'll repeat, I'm in the UK, I'm only interested in European AMI files.

 

[abdi]

Try pinging the sub-domain name and the IP address, compare the response times..The problem could be with the resolution server / dns server and not necessarily Plesk response back.

 

[LaughingBuddhaIT]

Ok. I was considering running the instance without Plesk as I've had some issues getting it to work.

I'll fire the instance up later, and post the ping response times here.

 

[LaughingBuddhaIT]

Well I can't get a response on Ping, and tracert bottoms out when it reaches the first server in ec2, but not the server/instance that the Plesk instance is loaded on.

The elastic IP is assigned to the instance, and is configured as a shared IP in Plesk. But it now isn't resolving the domain name to the box (something.tdldomian.com) unless you use https in front of it. Same with the IP address.

Wow, not impressed by EC2 so far.

 

[IgorG]

Maybe this thread will be useful - http://forum.parallels.com/showthread.php?t=258898

 

[abdi]

LaughingBuddhaIT, are you able to SSH the server without pinging or reaching it?