Problems with MX Records

[Rene1024]

Hello,

I have an Exchange 2000 server to receive mail. I switch ISP providers recently (2 weeks ago), I asked the company that host our website to make the appropriate changes to our MX Record and it seemed to be working fine until one of my users complained that she was not receiving all her messages. Apparently there were some senders that are receiving bounce back messages when they try to email her.

I've talked to my hosting company and they insist that everything is fine. Is there anything I can check on my end to see what's going on?

Rgds.

Rene.

 

[Davetoo]

Go here,

http://www.dnsstuff.com/,

put in your info and verify your MX record is pointing to your mail server.

Two weeks is more than enough time for the update to propogate.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[Rene1024]

Thanks for the quick reply lander, I had already tried that unfortunatelly. This are the results I get.

xxx.com MX IN 86400 mx1.prserv.net. [Preference = 10]

xxx.com MX IN 86400 mx2.prserv.net. [Preference = 20]

xxx.com. MX IN 86400 my exchange server [Preference = 5]

Which lead me to think that everything was fine until the problems with my user started.

Is there anything else I can try?

Rgds.

Rene

 

[Zelandakh]

telnet mx1.prserv.net 25
helo
mail from: rene1024@hotmail.com
rcpt to: <user having problems>
DATA
Subject: Test message
Please email Rene on the helpdesk if you receive this email
.

Could be the MX10/MX20 bouncing them.

 

[Marcs41]

Another possible reason:
You would be surprised how many servers out there are mis-configured, and don not update their internal DNS. The resul is what you experience, and there is nothing you can do about that except contact their IT person to have it fixed.

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[Davetoo]

Yeah, if the DNS/MX info is correct and the problem is with a specific sender, then I'd look at that senders servers for the problem, not yours.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[Rene1024]

Thanks for all your help, it seems that their server did not hava the proper internal DNS. It all seems to be working now.

Have a great holiday everyone.

Rene.

 

[Marcs41]

There you go. Lesson to remember: if only 1 or a few complain, start checking THEIR side first, it saves a lot of time.

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!}