Messaging Gateway

 View Only
  • 1.  Reverse DNS lookup failed

    Posted Apr 21, 2009 08:31 AM
    Hello,

    Since this morning, for some emails that are being sent out from our office (exchange 2007 to brightmail appliance) we get this bounce back:

    #< #5.0.0 smtp; 550 Host-Lookup-Failed: Reverse DNS lookup failed for 212.178.133.166 (failed)> #SMTP#

    the .166 ip is our brightmail gateway and if i look in the message audit logs of the gateway i see this:  Message rejected by MTA.

    Any idea?
    The mx records are set correct to the .166 IP so i dont understand why most mails deliver fine but some get this msg suddenly.



  • 2.  RE: Reverse DNS lookup failed

    Posted Apr 21, 2009 08:36 AM

    What about your ptr records Michiel?  Why don't you send me your domain name, you can also try some online tools to help resolve the issue:

    http://www.howismydns.com/tools.php

    Cheers,

    Kevin

     

     

     

     



  • 3.  RE: Reverse DNS lookup failed

    Posted Apr 21, 2009 08:42 AM
    I PM'd you the domain name, but here you go: techconnect.nl
    we dont have any PTR records set, in fact i cant set PTR myself anyway, why is that needed suddenly? before it worked fine.


  • 4.  RE: Reverse DNS lookup failed

    Posted Apr 21, 2009 08:47 AM
    Looks like our PTR record is set wrong, calling our backbone ISP now... sigh, still strange it worked fine before though.


  • 5.  RE: Reverse DNS lookup failed

    Posted Apr 21, 2009 10:03 AM

    Hi Michiel,

    You told us how your delivery binding settings looked after you made changes yesterday but you didn't mention what the values were originally pointing to. 

    Before you made changes yesterday was your 'Non-local messages' delivery binding set to '.167'? 

    If you change the setting back to what it originally was does it resolve the problem with the issues?  

    I suppose you can look into this if correcting the ptr records doesn't work, but I expect that should resolve the issue.

    Cheers,

    Kevin


  • 6.  RE: Reverse DNS lookup failed

    Posted Apr 21, 2009 10:08 AM
    It looks like after changing the PTR on the 166 IP it works..... so far,
    and yes it used to be .167 before in the non local.

    Thanks for your help.