Emails still going to old email server.

TheDjinn

• January 29, 2017 21:00

We recently upgraded our email provider to Exchange Online and switched all the DNS and MX records accordingly. After about an hour I did a test email, and it went to the new server like it was supposed to. However, the second test email went to the old server and every email since then. I've checked with whatsmydns, and everything is pointing to the new server correctly. After a bit of google research, I found out that MX records are often cached and typically don't follow the TTL expiration. So is there any way to forward all emails sent to the old server to the new server while we wait for the DNS servers around the world to get the memo? Thanks,

• 

  SysSachin

  • January 30, 2017 03:33

  Hello, Try to change MX record on old server and point it to new server. Edit DNS zone file on old server and change MX record.

  0
• 

  cPanelMichael

  • January 30, 2017 14:18

  Hello, Emails routed to the cPanel server should bounce to the sender if the "Email Routing" setting for the domain name is set to "Remote Mail Exchanger". Could you verify how the affected emails are sent if this is still happening? For instance, are the emails coming from local users on the cPanel server, or sent directly from remote email applications? Thank you.

  0
• 

  Gaurav755

  • December 20, 2020 03:02

  i have the same issue.I have changed my old mail server to a new server.I have changed my DNS also.But still my mails are routing from old server.I was using other service provider for my old server,and now this one is new.Should I have to do any changes in old server ? Or what kind of changes i need to do on the new server ?? If anyone give me brief details for this steps(FRom start to Last) it will really great for me. Thank you in advance.

  0
• 

  cPRex Jurassic Moderator

  • December 21, 2020 18:33

  Hey there, @Gaurav755 ! Are the sites properly pointed to the new machine, but only the emails are routed to the old IP? If do, the first thing I would check is the MX records that are in place for the domain. You can test that on the command line, preferably from your personal workstation to ensure that you aren't getting data from the local system:
  dig mx domain.com
  That will tell you what the MX record is for the domain you are working with. Once you have that, you can check and confirm the IP address of the MX record and make sure it is pointed to the correct location.

  0

Please sign in to leave a comment.