• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk 12 with AWS route 53 not work

Eric Fung

New Pleskian
Hi All,

I am getting lost on migrating Plesk to my AWS EC2 from a 3rd-Party VPS... I am now doing the DNS setting but no matter how I tried it is still fail.

I have installed the extension for AWS route 53 and insert the credentials already, sure have enabled the service in Plesk, and in my domain nameservers I set it to ns.mydomain.com - which is auto-configured by Plesk, the IP of the ns.mydomain.com is exactly the same of EIP I made on AWS. I have also run the repair_ip.cmd by mentioned in this guideline http://kb.odin.com/en/122222

I checked all the DNS records in my Plesk now is with the EIP correctly, DNS record has already updated (I'd wait 48 hours too). But when I type the domain in my browser it is still not go thru.

Do I missing some step? Or I need to configure something on Amazon Route 53 as the extension will not get auto-update to this?

Many Thanks.
 
Hi
"When you type the domain in your browser" AS in on your personal computer ?
If that is correct, then Does it work from other computers that have never been to your domain before ?
Try cleaning the DNS cache on your computer :
If you are running windows : run a command prompt (Start>run>CMD (enter)
then type in "IPCONFIG /FLUSHDNS"
Also, try to get to your domain from a computer that has never been to it before.
Post your domain name (and at least a few line test page there) and we can try to trace it, see if it shows up for anyone else.
 
Back
Top