Report this

What is the reason for this report?

Setup a "mail.xxx.com" in Digital Ocean (when xxx.com's hosting server is located in Amazon S3)

Posted on January 1, 2015

Hi guys. I’ll try to explain as detailed as possible.

  1. I own a Namecheap domain. And it’s web server is located in Amazon S3 and all directions xxx.com and www.xxx.com are routed with Amazon Route53.
  2. The point is: my customer wants a corporative mail ( @xxx.com) which server is now placed in DigitalOcean (ubuntu 14.xx).

The point is that my last step is to register the mail.xxx.com domain and point that domain to my IP DigitalOceans’s mail server.

But when I apply that action automatically it creates three “NS” records (which the digital oceans by-default-nameservers) and one “A” record (pointing to the IP). At this time I also created in Amazon Route53 a new “record set” of type MMX with the “mail.xxx.com” route and pointing to the three DigitalOcean “NS” directions.

Finally when I make a ping or trace mail.xxx.com it has no results in return.

I’m a little bit frustrated. In case you can help us, I would appreciate it.

Thanks in advance.

R.R.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This comment has been deleted

Point the MX record at your droplet’s IP address, not at the DigitalOcean nameservers.

This is because it is the nameservers which you create the records on which also do the pointing to the target for each record. In your case that’s Amazon Route53, so you do not need to use DigitalOcean’s. In fact, you cannot use both at once.

An alternative method would be to change the DNS settings in your Amazon Route53 to point at DigitalOcean’s nameservers and do not set up any records at all on Amazon Route53. Then you can create all of the records on DigitalOcean’s nameservers and point the MX to your droplet and the A (or all the As) to your Amazon S3 IP address(es).

Hope that helps. Ask away if that doesn’t make it clear.

Apologies raul, the answer I gave was incomplete. To get a mail server running on a droplet, you must first create an A record on the Amazon system, which effectively sets up a subdomain.

You can call it anything-you-like.xxx.com, so your original idea of mail.xxx.com is good, as would be post.xxx.com and many others. This new A record must have the subdomain name and point to your droplet’s IP address.

Then you make the MX record and follow on from there.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.