E-mail/DNS delivery problem

We moved authoritative DNS servers on Friday and ever since we cannot send to one of our bigger clients.   It appears that they are performing reverse-lookups on incoming mail and they are denying delivery with a message that says:

<xxx@bigclient.com>:
160.62.1.168 does not like recipient.
Remote host said: 553 5.1.8 <xxx@bigclient.com>... Domain of sender address my-email@glen-eagle.com does not exist

then the rest of the header:

Return-Path: <my-email@glen-eagle.com>
X-VirusChecked: Checked
X-Env-Sender: my-email@glen-eagle.com
X-Msg-Ref: server-4.tower-84.messagelabs.com!1099830386!1066811
X-StarScan-Version: 5.2.10; banners=-,-,-
X-Originating-IP: [66.225.84.20]
X-SpamReason: No, hits=0.2 required=7.0 tests=HTML_80_90,HTML_MESSAGE
Received: (qmail 28326 invoked from network); 7 Nov 2004 12:26:26 -0000
Received: from glen-eagle.com (HELO linux.glen-eagle-va.com) (66.225.84.20)
  by server-4.tower-84.messagelabs.com with SMTP; 7 Nov 2004 12:26:26 -0000
Received: from DGMR40 ([10.10.10.159])
      by linux.glen-eagle-va.com (8.11.6/linuxconf) with ESMTP id iA7CQTY14324
      for <xxx@bigclient.com>; Sun, 7 Nov 2004 07:26:29 -0500
Return-Receipt-To: "Drew McCann" <my-email@glen-eagle.com>
From: "Drew McCann" <my-email@glen-eagle.com>
To: <xxx@bigclient.com>
Subject: test
Date: Sun, 7 Nov 2004 07:26:26 -0500
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAfTqGmWI1M0uD+bY2iLwDzMKAAAAQAAAA63zPSaCVQkePeM8OVeafOwEAAAAA@glen-eagle.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
      boundary="----=_NextPart_000_0006_01C4C49B.17CC0C80"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcTDiww9MzhWmAM3Qj2qQq6HGqfgeA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Disposition-Notification-To: "Drew McCann" <my-email@glen-eagle.com>

This is a multi-part message in MIME format.

This client does use messagelabs.com to process their incoming mail.  However, I spoke with the messagelabs folks and they confirmed that they are accepting the message and delivering it to the destination server and that the destination server is the one rejecting it.  

Our DNS is currently at zoneedit.com and it looks like everything is set up properly.  Need to resolve this today.

Thanks,
Drew
mccann_dgAsked:
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.

ridCommented:
DNS changes take some time (like up to 48 h) to propagate through the system. The reverse lookup may fail because records aren't updated yet.
/RID
0
mccann_dgAuthor Commented:
I understand that these things can take time... but here is my circumstantial evidence that this is not the whole problem:

#1: This change was made on Friday and we began having the problem within a few hours... which means that their DNS cache updated at some point on Friday.  Therefore I find it difficult to believe that they are not updating their cache at least once every 24 hours.

#2: I am getting a lot less spam than normal.  However.. all other e-mail address I have sent to and received from have worked.

Thanks,
Drew
0
SembeeCommented:
It might be your CNAME in the MX records.
DNS Report flags some warnings on your domain "glen-eagle.com". It is an odd way of configuring the DNS and that might be why the remote machine is rejecting the message - it cannot deal with the CNAME for the MX record.

http://www.dnsreport.com/tools/dnsreport.ch?domain=glen-eagle.com

Simon.
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
mccann_dgAuthor Commented:
OK.. things are starting to work again.  Sembee, thank you for that link.. it has some very good information.   I am going to split points on this (with a higher weight toward Sembee) because what I think happened was that the irregular configuration reported in Sembee's post caused the record to take much longer to update than expected.. thereby reinforcing rid's comment about the amount of time it can take (but really shouldnt) to update DNS records.  Thanks again.
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
Email Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.