-2

I have registered a domain www.techsteroid.com with godaddy and hosted on aws ec2 instance with public dns ec2-52-8-152-90.us-west-1.compute.amazonaws.com . I have installed wordpress and associated elastic ip address and updated it in godaddy. Then, my website was redirecting to correct page like this

http://www.techsteroid.com/

but on clicking on any link, address bar will show public dns ie

http://ec2-52-8-152-90.us-west-1.compute.amazonaws.com/2016/06/11/hello-world/

instead of

http://techsteroid.com/2016/06/11/hello-world/

To fix it I created a hosted zone, imported zone file, and updated nameservers in godaddy. But since then website is not even opening. It says www...com can't ebe reached. Niether of company's support are able to resolve this problem.

The ss's are enter image description here enter image description here The problem now is how should I be able to connect to the site by its domain on my network. In permalinks setting, I am seeing this enter image description here

closed as unclear what you're asking by Iain, dawud, Jenny D, longneck, Jim B Jun 14 '16 at 18:08

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • I can't understand why people are downvoting. There are plenty of questions with similar problems with tens of upvotes. – It's a trap Jun 11 '16 at 20:25
  • 2
    You are getting downvoted because you have not dedicated ample time to truly understanding the technologies you are using, and because of this, are flailing around and causing further confusion for yourself. – EEAA Jun 11 '16 at 20:44
1

OK, first, the DNS changes you made are working. I can pull up the site without issue.

Your NS servers point to Route53 as expected:

$ whois techsteroid.com | grep "Name Server"
   Name Server: NS-1129.AWSDNS-13.ORG
   Name Server: NS-159.AWSDNS-19.COM
   Name Server: NS-1846.AWSDNS-38.CO.UK
   Name Server: NS-635.AWSDNS-15.NET

Furthermore, the DNS records themselves look good:

$ dig +short www.techsteroid.com
techsteroid.com.
52.8.152.90

Here's the site screenshot: website screenshot

So, any issue you're seeing locally are likely due to cache issues. Either your browser is caching old data, or something between your browser and the server is caching old data. Try a different browser, or connecting from a network different than the one you're currently using.

  • Comments are not for extended discussion; this conversation has been moved to chat. – EEAA Jun 12 '16 at 18:55

Not the answer you're looking for? Browse other questions tagged or ask your own question.