Solved

eMail Transition from one ISP to another

Posted on 2009-07-15
10
523 Views
Last Modified: 2012-05-07
We have just transitioned from one ISP to a 2nd ISP. All went well for the web side of things but we are finding that incoming eMail from external addresses is being handled by the OLD eMail server!? Is there something the NEW ISP must do to update the MX Record? It was my understanding this would follow the nameservers. (remember this is external hosted eMail - nothing fancy). IP Addresses all resolve to the NEW ISP and I can connect to their eMail server without issue.

What's up?
How does it get corrected?

Thanks!
0
Comment
Question by:DanielT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
10 Comments
 
LVL 4

Accepted Solution

by:
MattShadbolt earned 400 total points
ID: 24866438
how long ago did you change the DNS records? It can take "up to 48 hours" for records to propigate for some hosted DNS providers
0
 
LVL 2

Author Comment

by:DanielT
ID: 24869260
The nameservers were changed 2009-0714 at 1730. Website was redirected by approx 2009-0714 2000 (or before) but was not "up" yet due to ISP last minute prep. The website itself was up and running by 2009-0715 1100 when ISP completed their work so DNS records are fine that way. Domain resolves to correct, new, IP address.

Would MX records not simply move with the domain?
0
 
LVL 50

Expert Comment

by:jcimarron
ID: 24873074
DanielT--I would think you would have to change the POP-3 and SMTP settings in the Account|Properties.
What is the email program?
0
Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

 
LVL 2

Author Comment

by:DanielT
ID: 24873966
Update.
Ya - thanks. All that was done.

Seems like it was just a propogation delay for the MX Record to take effect I guess - unless there was something on our ISP end they did not do it until today (and did not advise us, despite asking). As above, I thought that when the new website location was finally registered that eMail routing would have been updated at the same time.

All is working now but...
Any other ideas on why there would have been a longer delay for eMail than for web?

0
 
LVL 4

Assisted Solution

by:MattShadbolt
MattShadbolt earned 400 total points
ID: 24874740
IMO it sounds like the propagation delay - if most mail was being relayed correctly but some wasn't then it sounds like the mx records weren't refreshed on those hosts being relayed to the wrong server
0
 
LVL 2

Author Comment

by:DanielT
ID: 24900894
Thanks for the additional comments but I am not closer to understanding the difference between the domain name propogation delay and the MX Record propogation delay.

What exactly is the MX Record anyway? I mean I know what it is for but where is it setup, how does it tie itself to the domain. Where does it reside?

0
 
LVL 4

Assisted Solution

by:MattShadbolt
MattShadbolt earned 400 total points
ID: 24900974
the MX record is what an external mail server looks for. So when some one sends you a piece of mail, their server will do a MX lookup on the domain they are trying to send to. Normally, their ISP's name server responds with an mx record - say mail1.domain.com. The mail server then attemps to deliver the message to the mail1.domain.com server. So, if their ISP's name server is holding an old version of your MX record the person trying to deliver the mail will attempt to send it to the old server not the new server. The MX record is just like an A or CNAME record - but it is just dedicated to mail servers.
0
 
LVL 2

Author Comment

by:DanielT
ID: 24909747
MattShadbolt

Thanks.
Makes sense to me.

Last kick at this (I think) and more a matter of interest...
(Thanks for your patience)

So if the NEW nameservers have taken effect such that the NEW nameserver IP address is returned for the given domain and the NEW website is up and running why would the MX lookup not return the NEW MX record pointer (in the case of combined web and eMail hosting service)?

Are you saying then that the OLD MX record is cached on other servers between the eMail source and eMail destination independent of the NEW nameservers? Otherwise how could a query to the domain which is now pointed to the NEW nameservers return an OLD MX record? This was the reason for asking earlier if there was perhaps something the ISP did not do?



0
 
LVL 4

Assisted Solution

by:MattShadbolt
MattShadbolt earned 400 total points
ID: 24909775
no i think your ISP has done everything right - it may just be that some external mail servers who are trying to send you mail don't refresh their records as often as they should. Large ISPs or mail hosts especially will cache MX records for 2 or 3 days because MX records rarely change. It also saves the $ on bandwidith as they don't check for updates for every email that is sent through their servers.
This would explain why most of your email was being delivered to your new servers, and only a little delivered to the old server - a small minority of external mail servers just hadn't flushed their DNS cache and gone searching for updates.
0
 
LVL 2

Author Closing Comment

by:DanielT
ID: 31604092
Thanks for the help!
0

Featured Post

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Phishing attempts can come in all forms, shapes and sizes. No matter how familiar you think you are with them, always remember to take extra precaution when opening an email with attachments or links.
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

726 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