Solved

How do I route mail traffic to remote server?

Posted on 2008-10-13
11
224 Views
Last Modified: 2012-05-05
I'm currently running a Fedora Core 6 web server that handles my website, database, and email.  I would like to offload the processing of email message to a new server.  I couldn't figure out the DNS settings to route email traffic for this domain to a different server/IP address.  Any suggestions on the best method?
0
Comment
Question by:laicc
  • 4
  • 3
  • 3
  • +1
11 Comments
 
LVL 40

Expert Comment

by:omarfarid
Comment Utility
you need to change the MX record for that domain in dns to point to the other server ip address
0
 
LVL 4

Expert Comment

by:tweaky
Comment Utility
omarfarid is very correct. You need to change the MX records for that domain. How and where do you manage your domain? If you give us details, we might be able to help you further.
0
 
LVL 9

Expert Comment

by:michofreiha
Comment Utility
changing MX record is the best solution...Another solution is to forward emails to another server based on each account but this method change from mail server to another...If you tell us which mail server are you using then we can help much more better
0
 

Author Comment

by:laicc
Comment Utility
Here are my DNS records ...
Host            Record Type            Value
70.110.120.025 / 24      PTR            mydomain.com.
mydomain.com.      NS            ns.mydomain.com.
mydomain.com.      A            70.110.120.025
mydomain.com.      MX (10)            mail.mydomain.com.
ftp.mydomain.com.      CNAME            mydomain.com.
mail.mydomain.com.      A            70.110.120.025
ns.mydomain.com.      A            70.110.120.025
webmail.mydomain.com.      A            70.110.120.025
www.mydomain.com.      CNAME            mydomain.com.

There's an MX and A record for handling mail ...
0
 
LVL 4

Expert Comment

by:tweaky
Comment Utility
In your case the easiest thing would be to change the following record:

"mail.mydomain.com.      A            70.110.120.025"

Change the IP address of mail.mydomain.com  to whereever you want your mail to go to.

A that's it.

Actually it may take upto 48 hours for the DNS change to propagate all servers, but you should see the change take affect quite fast on most servers.  
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 40

Expert Comment

by:omarfarid
Comment Utility
The mail.mydomain.com is not the FQDN to which mail is sent by other domains. Other domains will be looking for the MX records of the domain. This FQDN will be mostly used by the domain users to point to for sending and receiving emails.
0
 
LVL 4

Expert Comment

by:tweaky
Comment Utility
omarfarid:

If you look above at the DNS records that laicc provided, you will notice that the MX (10) for this domain is mail.mydomain.com. Further down, there is A record for the mail.mydomain.com.  The user can EITHER modify the MX record directly with the IP  or FQDN or the new host that will handle email for this domain OR change the A record for the mail.mydomain.com (because that's what the MX record is pointing to).

If the user changes the MX record directly, there is less potential for other things to break - like mails clients and such.  
0
 

Author Comment

by:laicc
Comment Utility
So is the recommendation to ...

A) Chnage both MX and A records to the new IP
B) Change A record to new IP address and leave MX alone
C) Change MX record to new IP address and leave A record alone

Thanks!
0
 
LVL 4

Accepted Solution

by:
tweaky earned 250 total points
Comment Utility
Don't do option A. Either do option B or option C, but not A. To minimize the side affects of this change, it is probably best to implement option "C) Change MX record to new IP address and leave A record alone"
0
 
LVL 40

Assisted Solution

by:omarfarid
omarfarid earned 250 total points
Comment Utility
Sorry, It seams that I posted my comment before seeing your posting of dns records.

Here you are setting:

A record for mail.mydomain.com.
MX record to point to mail.mydomain.com.

So, as tweaky commented ( ID: 22711807 ), you may do B) unless you need mail.mydomain.com to point for something else, then you need to do C)

How your users are sending mail and accessing their mailboxes? Are they using webmail or SMTP / IMAP / POP ?
0
 

Author Comment

by:laicc
Comment Utility
I'm using webmail to access email so I should probably change the A record for webmail to point to the new IP as well.

Thanks Omar and Tweaky for the great discussion!!!
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

This is the error message I got (CODE) Error caused by incompatible libmp3lame 3.98-2 with ffmpeg I've googled this error message and found out sometimes it attaches this note "can be treated with downgrade libmp3lame to version 3.97 or 3.98" …
The purpose of this article is to demonstrate how we can use conditional statements using Python.
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now