Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 45 replies
  • Subscribers 1 subscriber
  • Views 32200 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[8.201] RDNS missing

Tribmos
I saw the other thread but it is locked currently.

I have been noticing a large increase of 'RDNS missing' entries in the Mail Log.

Typically a user sends me a message that they have not been getting mail (often the client sends it from a gmail or such to inform them).  Verify the log and see the RDNS entries.  Pop over to MXToolbox and run their checks and see it labeled as OK on the RDNS check.

So I am at a loss as to why it is occurring.

For example: seagullscientific.invisionzone.com - this is a support forum for label software, it got a RDNS missing despite it appears to be all correct (unless i'm missing something).  Astaro logged it as coming from 208.67.212.34


This thread was automatically locked due to age.
Parents
  • 0
    Bruce, to give one example.  One customer's Astaro hostname is mx2.domain.com.  The rDNS for the IP of "External (Address)" is mx2.domain.com.  Prior to V8, that passed.

    Now, since the MX records for domain.com no longer include one with mx2.domain.com, my 8.202 box rejected the email from their Astaro.

    Cheers - Bob
    PS Danitaz, outside of a problem with the flow monitor when accessing with IE8/9, 8.202 looks good - definitely an improvement over 8.201.
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    Bruce, to give one example.  One customer's Astaro hostname is mx2.domain.com.  The rDNS for the IP of "External (Address)" is mx2.domain.com.  Prior to V8, that passed.

    Now, since the MX records for domain.com no longer include one with mx2.domain.com, my 8.202 box rejected the email from their Astaro.

    Cheers - Bob
    PS Danitaz, outside of a problem with the flow monitor when accessing with IE8/9, 8.202 looks good - definitely an improvement over 8.201.


    Hence, a DNS issue... the MX record should be fixed.  [:)]

    Oh, and DKIM appears to be broken in 8.2xx (including 8.202) ...

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply
  • 0 in reply to BAlfson
    Bruce, to give one example.  One customer's Astaro hostname is mx2.domain.com.  The rDNS for the IP of "External (Address)" is mx2.domain.com.  Prior to V8, that passed.

    Now, since the MX records for domain.com no longer include one with mx2.domain.com, my 8.202 box rejected the email from their Astaro.

    Cheers - Bob
    PS Danitaz, outside of a problem with the flow monitor when accessing with IE8/9, 8.202 looks good - definitely an improvement over 8.201.


    Hence, a DNS issue... the MX record should be fixed.  [:)]

    Oh, and DKIM appears to be broken in 8.2xx (including 8.202) ...

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Children
No Data
Cookie Information Banner