Thread: MX DNS Records
View Single Post
Old 9th April 2013, 03:45
Parsec Parsec is offline
Join Date: Jan 2013
Posts: 66
Thanks: 1
Thanked 9 Times in 8 Posts

Originally Posted by mrrow View Post - - This is the address and IP of the physical hardware. It runs the mail server, - This is the domain name of the client website.

I have a few choices as I see it.
1. Just set the MX record to for every client.
2. Set the MX record to and have an A record pointing ->
3. Set the MX record to and have an CNAME record pointing ->
Well, you can do it whichever way you like although option 3 is most probably better then 2. However Option 1 is actually the best, especially if your clients start using ssl methods of transport. Assuming has a valid ssl certificate, then the clients will connect without issue, however if you use their domain name and the server responds with it's ssl cert ( they will always get an error popping up in their client.

Originally Posted by mrrow View Post
I'm trying to figure out what the best thing to do is from:
1. A maintenance point of view (likely to move servers in the future)
2. Receiving servers point of view (are any of the options less likely to get email from bounced / help with reverse DNS lookups)
1. Actually another way is to have a cname for and this server has a wildcard ssl for *, then you merely create a cname for the server eg: cname In this way if you ever change or get a new server and it's called you can use the same ssl and just change the cname ( cname - thus clients just keep their existing setup in their email clients eg:

2. Doesn't matter, the other end will always see the mail as coming from so as long as that has the corect rDNS you should be fine.
Reply With Quote