activateahsd
asked on
MX records and A records have changed according to Nslookup but mail still sent to the wrong server.
Hi
I have changed the mx record of europeanbusinessjets.com from pointing directly at the exchange server back to the ISP (we need to use pop connector for email redundancy) I changed the mx record about 12 hours ago and an nslookup returns the right info, namely mail.securahosting.com. If i send a test mail it still gets delivered straight to the server for some reason? In looking further at the domain control panel I noticed that there is a section for an A record which was still pointing to the IP address of the exchange server - I changed that about 1 hour ago to be mail.securahosting.com as well - firstly is that right?, secondly why is mail still being delivered direct to the server? Is it just a case of wating abit longer?
Thanks
Andy
I have changed the mx record of europeanbusinessjets.com from pointing directly at the exchange server back to the ISP (we need to use pop connector for email redundancy) I changed the mx record about 12 hours ago and an nslookup returns the right info, namely mail.securahosting.com. If i send a test mail it still gets delivered straight to the server for some reason? In looking further at the domain control panel I noticed that there is a section for an A record which was still pointing to the IP address of the exchange server - I changed that about 1 hour ago to be mail.securahosting.com as well - firstly is that right?, secondly why is mail still being delivered direct to the server? Is it just a case of wating abit longer?
Thanks
Andy
ASKER
Thanks for your reply, i was wondering if it was just a case of waiting.
Re the POP connector, I agree i would rather leave it as it is but you are wrong to say that if exchange goes down i am no more redundant - if the server is not available to collect the email then the company will be able to log on to the isp webmail from any internet connection to get their email. Their email is extremely time sensitive, if the server is not available for 4 hours that could be a major problem and lead to clients missing flights etc...
Re the POP connector, I agree i would rather leave it as it is but you are wrong to say that if exchange goes down i am no more redundant - if the server is not available to collect the email then the company will be able to log on to the isp webmail from any internet connection to get their email. Their email is extremely time sensitive, if the server is not available for 4 hours that could be a major problem and lead to clients missing flights etc...
>>but you are wrong to say that if exchange goes down i am no more redundant
And that is where we disagree, I will explain why.
>>if the server is not available to collect the email then the company will be able to log on to the isp webmail from any internet connection to get their email.
That is partially true, or I should say, that CAN be true - but if that is the case, then you will need to manage your users THREE times - adding a local account, a remote account and the pop3 connector for each "joint". So yes, they can do that, but you are creating a TON of admin work there.
>>if the server is not available for 4 hours that could be a major problem and lead to clients missing flights etc...
I have clients that do travel - I know exactly what you are talking about, but I would still never use a pop3 connector. The real problem is that POP3 connectors are not designed as primary delivery mechanisms - they break, and they also mean that you cannot use good anti-spam systems.
So, while I agree with your logic that it can work this way, and will achieve what you want - I do not believe this is the best way. I leave it up to the client to make the decision, as it purely comes down to cost. The options you have are 3rd party exchange replication, standby servers, clusters, redundant links, etc.
When I put this to my travel client, he was able to make a business decision, and we opted for a standby server and redundant link - if the server dies, I can have it back online in no more than an hour, at least in part - and if the line goes down, it fails over to the other one.
But hey, I guess you are the Admin - so if you are happy with it, go for it, personally I feel that the less time I spend on duplication of work, the more I can do important things (like going home early) ;)
-red
And that is where we disagree, I will explain why.
>>if the server is not available to collect the email then the company will be able to log on to the isp webmail from any internet connection to get their email.
That is partially true, or I should say, that CAN be true - but if that is the case, then you will need to manage your users THREE times - adding a local account, a remote account and the pop3 connector for each "joint". So yes, they can do that, but you are creating a TON of admin work there.
>>if the server is not available for 4 hours that could be a major problem and lead to clients missing flights etc...
I have clients that do travel - I know exactly what you are talking about, but I would still never use a pop3 connector. The real problem is that POP3 connectors are not designed as primary delivery mechanisms - they break, and they also mean that you cannot use good anti-spam systems.
So, while I agree with your logic that it can work this way, and will achieve what you want - I do not believe this is the best way. I leave it up to the client to make the decision, as it purely comes down to cost. The options you have are 3rd party exchange replication, standby servers, clusters, redundant links, etc.
When I put this to my travel client, he was able to make a business decision, and we opted for a standby server and redundant link - if the server dies, I can have it back online in no more than an hour, at least in part - and if the line goes down, it fails over to the other one.
But hey, I guess you are the Admin - so if you are happy with it, go for it, personally I feel that the less time I spend on duplication of work, the more I can do important things (like going home early) ;)
-red
ASKER
I didnt want to do it but there was no other cost effective way to achieve the result that i could see.
Anyway, thanks for all your input. There is one thing that puzzels me, if I do an mx record nslookup using my isp dns server it returns what it should be i.e mail.securahosting.com, so am i not right in thinking that email i send from me should be routed via mail.securahosting.com not sent direct to the server (as is still happening)??
Anyway, thanks for all your input. There is one thing that puzzels me, if I do an mx record nslookup using my isp dns server it returns what it should be i.e mail.securahosting.com, so am i not right in thinking that email i send from me should be routed via mail.securahosting.com not sent direct to the server (as is still happening)??
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Your DNS records look fine, but it can take up to 48 hours for the changes to be completed.
As for using a POP3 connector - that is just horrible. All you are going to do is increase mail delivery problems, and if exchange goes down, you are no more redundant.
Considering you are already so far down this path, I expect you are beyond convincing that you should UNDO these changes, but that would be my recommendation.
-red