How do I create a Static MX Address for an another company's email server in my DNS

I've got a customer that we work with who can't receive our emails.  When I do a NSLookup on a customer's domain in our network, it returns the incorrect MX record.  Instead of mail.XX.net it returns a MX record of xx.net.  Their IT admin told me to enter a static MX record to replace what I'm getting back.  I don't know why I have to do that, but if it makes my boss and his boss happy (and communicating) then we'll do it.  But first, I don't know how to do that (please help) and second I don't know why this is a problem in the first place.  I did run a dnsstuff.com dnsreport on his domain, it passed everything but the "Mail" section (full failure).  It passed the MX section, but not Mail.  Again, not sure and neither is their IT admin.  They are getting email from other sources  because I can mail him from an outside email.
Thanks for your help, Stephen
seddlemanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DrDave242Commented:
In order to do what you're describing, you'd first have to create a forward lookup zone named XX.net on your DNS server, then create a host (A) record in that zone for mail.XX.net, and finally create an MX record that points to the host record.  That should work, but there are issues:  Your DNS server is not really authoritative for XX.net, but once you create that zone, it will think that it is, so any DNS queries for that domain from inside your network are going to go to your server and no further.  Your server will not forward those queries to the server that is actually authoritative for that zone.  This means that if anyone on your network needs to access somehost.XX.net, you will have to create a host record for it on your server.
A better solution would be for the people on the other end to figure out what's wrong with their DNS, rather than asking you to work around the problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
seddlemanAuthor Commented:
Just what I was thinking....
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.