Question : Public DNS Conflict with GoDaddy

One of my clients has a SBS 2003 running Exchange with @pdslex.com as email extensions.
They are having problems with mail not getting to them from other email users.

Outside users will send email and it comes back right away.  This has been going on for a few weeks that we know of.  Not everyone is blocked, as  a matter of fact most email, probably 95% goes through just fine.
So because of someone's advice from this site on another question I had, I ran the pdslex.com through DNSStuff.com and got this result: http://i55.photobucket.com/albums/g142/chrisdfoley/DNSStuffReport.png (everything else on this report was clear.)

This domain is registered through GoDaddy.  So I went to GoDaddy's site to remove the bad MX listing.  There is no record listed that has a host as the IP address.  Here is the GoDaddy screen: http://i55.photobucket.com/albums/g142/chrisdfoley/GoDaddyDNS.png (the top was cut off but the first section is the A records.)

I have called GoDaddy 3 x's and spoken to 5 different people and they all say the same thing.  It isn't their problem and that bad MX record does not exist.  But according to DNSStuff.com it does.

Can anyone point me in another direction maybe of what I have to do to get this IP removed as a HOST name from an MX listing that does not exist.

FYI, I have 3 other Exchange servers set up exactly the same for other clients and they come back perfect through DNSStuff.com so I'm pretty sure the setup is right.

Answer : Public DNS Conflict with GoDaddy

Problem solved.  Switching to Network Solutions removed the faulty listing.  I have a few other minor things to work out but at least the big ones are fixed.  Everyone, thanks for your input!