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

Quote:
Originally Posted by mrrow View Post
server.com - 123.123.123.123 - This is the address and IP of the physical hardware. It runs the mail server, mail.server.com
client.com - 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 mail.server.com for every client.
2. Set the MX record to mail.client.com and have an A record pointing mail.client.com -> 123.123.123.123
3. Set the MX record to mail.client.com and have an CNAME record pointing mail.client.com -> mail.server.com
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 mail.server.com 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 (mail.server.com) they will always get an error popping up in their client.

Quote:
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 user@client.com bounced / help with reverse DNS lookups)
1. Actually another way is to have a cname for mail.server.com and this server has a wildcard ssl for *.server.com, then you merely create a cname for the server eg: smtp1.server.com cname mail.server.com. In this way if you ever change or get a new server and it's called mail3.server.com you can use the same ssl and just change the cname (smtp1.server.com cname mail3.server.com) - thus clients just keep their existing setup in their email clients eg: smtp1.server.com

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