Sign up ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

I was given two domains: & (they are on GoDaddy).

And I was also given two servers, - Rails app and - Wordpress platform, on Digital Ocean.

At first, I was instructed to associate with the (Rails app). Then I was instructed to de-associate this IP with and associated the with the domain name

Then I was instructed to associated with the (Rails app).

Right now, when I go to the WordPress platform ( loads fine and that is what is expected. But when I go to for the Rails app ( I get redirected to This is not expected and this is really weird for me.

When I ping I get this:

PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=50 time=74.601 ms

Which is the expected result showing the correct IP but I don't understand why I get redirected to when I ping is:)

domain 64 bytes from icmp_seq=0 ttl=50 time=75.057 ms

The PTR Records on Digital Ocean are as follows:

IP Address  PTR Record

and the DNS configurations on Digital Ocean are:

A: @

CNAME: * @

A: @

CNAME: * @

I am not sure what the issue is, if you have any clue please let me know, I will be really grateful. If you need any other info let me know.

share|improve this question

closed as off-topic by Stephen Ostermiller Dec 20 '14 at 13:34

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions that are specific to one website are discouraged because they are unlikely to help future visitors. Examples include individual website reviews for SEO purposes and general website troubleshooting. See the How to Ask page for help improving this question." – Stephen Ostermiller
If this question can be reworded to fit the rules in the help center, please edit the question.

You're looking in the wrong place. Redirects are nothing to do with your DNS, but instead they're generated by your web server config, and that's what you should be asking about. – Mike Scott Mar 28 '14 at 19:35
@MikeScott you were right! Fixed it! I did not configure nginx correctly! You are awesome! Thanks! – Stefanos.Ioannou Mar 28 '14 at 19:48
Looks like this was a problem specific to your setup that is now solved, so closing. – Stephen Ostermiller Dec 20 '14 at 13:34