Geek Answers Handbook

AWS loadbalancer requires an @cname entry, but that overrides my @MX entries

I need to add a CName entry for my AWS mywebsite.com load-loaded site. The entry should be:

@ CNAME mywebsite.us-east-1.elb.amazonaws.com

However, it appears (according to 123-reg) that this will replace the @MX entries that I have for email in this domain:

 @ MX 300 mail1.mywebsite.com. @ MX 400 mail2.mywebsite.com. @ MX 500 mail3.mywebsite.com.

I am stumped because they both look reasonable and I did not expect CName to take precedence over MX in this way.

Any ideas on how to proceed? I suppose there should be a different way to tune MX records, but don't know how to do this.

+4
source share
2 answers

I would recommend moving your DNS hosting to Amazon Route 53.

You will also not be able to use CNAME , as this is a general DNS limitation (see RFC 1034 section 3.6.2 - http://www.faqs.org/rfcs/rfc1034.html ). However, for A Records on Route 53, you can indicate that the record is an "Alias" (this is a special AWS function), and select your ELB as the target instead of a specific IP address. Since the host is configured through and record A, you can also enter MX records.

In addition, Route 53 is a very advanced DNS system and affordable, starting at a dollar per month ( http://aws.amazon.com/route53/pricing/ ), so you will also get many other benefits.

+5
source

yes, even I had the same problem after switching to Route 53, this was resolved. When it comes to pricing, Route 53 is not expensive at all, as it pays for peanuts if you have an AWS-based production system and spend a lot.

+1
source

More articles:


All Articles