• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 751
  • Last Modified:

DNS & MX Record, Intermittent delivery failures

After a new exchange server implementation I am receiving intermittent delivery failures. The failures look as if the sender has no A host record for my domain. I have checked my DNS, A Host and Mx records with http://www.dnsstuff.com/ and http://www.mob.net/~ted/tools/index.html. Everything seems to be in order. Any suggestions would be appreciated. The following is an example of a failure message:

04/21/2006 15:39:41) by <<User>>: group=WW_SECURITY_SERVICE

  (First 50 Lines Only)   Apr 19 09:44:04 pivsbh1
postfix-idmz/smtp[12638]: 45EAF26DCD: to=<myname@mydomain.com>,
relay=127.0.0.1[127.0.0.1]:10025, delay=13,      
                          delays=0.61/1.5/0.73/10, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2756E1EDD6)

                          Apr 19 09:44:04 pivsbh1 postfix/smtp[11011]:
2756E1EDD6: to=<myname@mydomain.com>, relay=none, delay=10, delays=10/0.01/0.17/0, dsn=5.4.4,
                           status=bounced (Host or domain name not found. Name service error for name=mydomain.com type=A: Host found but no
data record of        
                          requested type)

 

                          Local Time: 04/21/2006 01:32:13 (GMT:
04/21/2006 05:32:13) by xxpmjenn: group=WW_ECT_EXCHANGE

                          test mail was not successful.

                          =================

                          From: <<User>>

                          Sent: Fri 4/21/2006 1:12 PM

                          To: myname@mydomain.com

                          Subject: test mail, pls ignore. thanks!

 

                          Your message did not reach some or all of the intended recipients.

 

 

                          Subject:  test mail, pls ignore. thanks!

                          Sent:  4/21/2006 1:12 PM

 

                          The following recipient(s) could not be
reached:

 

                            myname@mydomain.com on 4/21/2006 1:12 PM

                            The message could not be delivered because the recipient's destination email system is unknown or invalid. Please
check the address  
                          and try again, or contact your system administrator to verify connectivity to the email system of the
recipient.                        
                            < amrmr1003.accenture.com #5.1.2>

 

                          Local Time: 20/04/2006 20:01:56 (GMT:
21/04/2006 00:01:56) by <<User>>: group=WW_SECURITY_SERVICE

                          Exchange group: please send a test email from an external address to myname@mydomain.com and notify us the results.

 

                          . <<User>> has sent email to: <<USer>>,  on
20/04/2006 19:56:46

 

                          I just sent a test email to myname@mydomain.com and it bounced back also. Looks like their email server is misconfigured.  However, I'll  
                          ask the exchange group to send an email from an external account to test this.

 

                          Local Time: 04/21/2006 07:03:45 (GMT:
04/20/2006 23:03:45) by xxpmbuen: group=WW_ECT_EXCHANGE

                          escalating to WW_SECURITY_SERVICE to check on the bastion hosts.

                          FYI

 

 

                     

 
0
pwanveer
Asked:
pwanveer
1 Solution
 
ECNSSMTCommented:
Just in case; it does take about 48 hrs for DNS information to proprogate thru the internet.  (Yes I see the 4/19 post date)  But some sites may be using older cached information.  And the external site may need to have their DNS records updated.  I assume that you are recieving mail from other sites as DNSSTUFF has reported your up-to-date A and MX records.

Regards  

0
 
ECNSSMTCommented:
just for kicks; test from a Yahoo, google account or the like...

Regards
0
 
pwanveerAuthor Commented:
That's what is so confusing, I've tested from Yahoo, Hotmail, Comcast and a number of other external accounts. They all come through correctly. Yet a number of people trying to deliver messages get kick backs.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ECNSSMTCommented:
Yahoo Hot mail, etc are well travelled and well updated sites.  
If mail flows from them to you, everything is good; at least from your prospective to the general internet.  (that should be almost everyone)  How it get elsewhere is as fast as DNS proprogation goes.  If you can wait for proprogation, great.  If its urgent; then you will have to test with the distant end email admin.  See if they can at least telnet to your server and do a helo.

regards,
0
 
CKWTCommented:
did your problem clear up by know, How many mail server do you have?
Could it be a time out problem on your connection?
or maybe made an IP address the main server and was a secundary server before?.. switching around like those could confuse DNS server that has not updated yet...
I made a server change and IT REALLY took 72hours to the minute for emails to work at 100%...
What im saying that for the time there isn't much you could do but wait on all servers would update.. create and email form some weird free email system, and send yourself an email, somewhere that PROBABLY you have never received email from...

0
 
ECNSSMTCommented:
Hi pwanveer,

I've been thinking.  My above thought still stands.  But I am rather curious "how many sites are affected?".  Underneath it all, it should be about 1 site in terms of a normal occurance (or at least a very LOW magnatude) and the site in question is uasually small.  Usually for some odd reason, either they or their 3rd party support group propbably have their DNS server update once a week as an odd rule of thumb.  
In dealing with a DNS update, the average rule of thumb is "the information will proprogate throughout in the internet in 48 hours".  
The only thing that the sending site has to do is a DNS update from their ISP, that should clear up the problem.

Regards,
0
 
upul007Commented:
Just to be sure run a report on your domain at www.dnsreport.com see if there are any errors.
0
 
ECNSSMTCommented:
hey upul007,
check out www.dnsstuff.com as listed by pwanveer, it is a little more thorough.

Regards
0
 
upul007Commented:
@ECNSSMT,

I use both sites. Dnsreport gives the option of checking the overall settings for a domain. The Dnsstuff site carries the link to Dnsreport on the top left hand part of the page. Use DNSReport to get a third party appraisel of a site anytime.....

0
 
ECNSSMTCommented:
Hi pwanveer,

At this point, I am assuming that it has been about 9 days since you've updated your MX record to reflect the current path to your mail server.   Any sites that update their DNS tables on a daily basis are sending to you (like Yahoo, Google, etc) as you stated.  Any sites that infrequently update should have automatically updated their DNS tables by now and should be able to send to you without issues.

Regards,  
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now