Two MX Records both with [Preference = 0]

We keep getting delay notices and then failures when our users are sending to one domain in particular.  

I looked up the DNS info on the domain  and got the following:

blahblah.net.      MX      IN      86400      mx01.blahblah.net. [Preference = 0]
blahblah.net.      MX      IN      86400      mx02.blahblah.net. [Preference = 0]

Preference = 0 means that it has the highest priority.

What happens when you have two that are set to the highest priority?   Could this be causing the delay/failure notices.

We are running exchange 2003 sp2.   Is there anything I could do on my end get it to go though?
rasupportAsked:
Who is Participating?
 
rasupportConnect With a Mentor Author Commented:
Not in the last few months.

Thanks Chris for your help.  
0
 
Chris DentPowerShell DeveloperCommented:

> What happens when you have two that are set to the highest priority?  

It's load balanced over all servers of equal priority. Typically message 1 goes to mx01, message 2 to mx02, and so on.

Are you able to connect to both servers? "telnet mx01.blahblah.net 25"?

Chris
0
 
rasupportAuthor Commented:
Chris,  I can only connect to mx01, mx02 times out.


0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

That certainly won't help. Lets see if it's a problem on your end or theirs...

Head here and pop the mail server name in the box:

http://www.mxtoolbox.com/diagnostic.aspx

If that can't connect either then it suggests a problem on their end.

With one failing it should use the other MX record and connect to that. I wonder if that's reliable...

Chris
0
 
rasupportAuthor Commented:
response from mx01 came back with:

Transaction Time:         12.031 seconds - Not good!

(the other tests passed)


and mx02:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x

I'm guessing it's something on there end...

Great site by the way, thanks!  
0
 
Chris DentPowerShell DeveloperCommented:

Yeah, I'd say it was. I guess you don't have problems delivering to anyone else?

Chris
0
All Courses

From novice to tech pro — start learning today.