Incoming mail PTR records not resolving

Question asked by Robert Simpson - 12/4/2018 at 2:56 PM

Answered

(SM17 v6911) I submitted a ticket for this already and it's being investigated -- but is anyone else having a problem where all incoming mail is having the Received: header read "UnknownHost" ?

1. Reverse DNS antispam check is passing, so incoming mail arrives just fine.
2. The mail server sends and receives e-mail just fine, so DNS resolution is working

3. SMTP logs report "PTR host name for XXX.XXX.XXX.XXX resolved as UnknownHost" for every incoming IP address, no exceptions.

9 Replies

Reply to Thread

Linda Pagillo Replied

12/4/2018 at 3:05 PM

Hi Robert. Are you using an in-house DNS server with SmarterMail or are you using external servers such as Google's 8.8.8.8 and 8.8.4.4?

Linda Pagillo Mail's Best Friend Email: linda.pagillo@mailsbestfriend.com Web: www.mailsbestfriend.com Authorized SmarterTools Reseller Authorized Message Sniffer Reseller

Dave Feuer Replied

12/4/2018 at 3:11 PM

I am getting this too.

Using our own in house DNS that work fine with 15.x & 16.x

-Dave

Robert Simpson Replied

12/4/2018 at 3:15 PM

Using google DNS

I should also point out that all these IP addresses that SM is saying are "unknownhost" will resolve properly if I use NSLOOKUP to reverse DNS them from the same mail server.

Neil Harvey Replied

12/4/2018 at 3:30 PM

I am getting this too.

Using hosting DNS. Tried the google DNS servers and it still fails

v6898

Neil

Matt Petty Replied

12/4/2018 at 5:02 PM

Employee Post Marked As Answer

Hello thanks for reporting this. We have a fix for this issue. Contact me for a link to the build with fix. I've already sent the link to everybody here.

You can DM me by clicking my name and "Send Message"

Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com

Robert Simpson Replied

12/4/2018 at 6:17 PM

Soooo close, Matt!!

Received: from ms11p00im-qufo17291401.me.com (ms11p00im-qufo17291401.me.com. [17.58.38.43]) by mail.bcsft.com with SMTP     (version=TLS\Tls12     cipher=Aes256 bits=256);

There's now an extra dot after all the domain names. They are resolving, though!

[2018.12.05] 01:16:51.471 [17.58.38.43][63688589] Performing PTR host name lookup for 17.58.38.43
[2018.12.05] 01:16:51.471 [17.58.38.43][63688589] PTR host name for 17.58.38.43 resolved as ms11p00im-qufo17291401.me.com.
[2018.12.05] 01:16:56.580 [66.220.144.170][9679072] Performing PTR host name lookup for 66.220.144.170
[2018.12.05] 01:16:56.580 [66.220.144.170][9679072] PTR host name for 66.220.144.170 resolved as 66-220-144-170.mail-campmail.facebook.com.
[2018.12.05] 01:17:20.879 [64.44.134.96][1540034] Performing PTR host name lookup for 64.44.134.96
[2018.12.05] 01:17:20.879 [64.44.134.96][1540034] PTR host name for 64.44.134.96 resolved as 96-134-44-64.reverse-dns.
[2018.12.05] 01:17:26.129 [119.40.92.18][6083222] Performing PTR host name lookup for 119.40.92.18
[2018.12.05] 01:17:26.129 [119.40.92.18][6083222] PTR host name for 119.40.92.18 resolved as 119-40-92-18.spnetctg.com.
[2018.12.05] 01:17:47.786 [203.160.61.120][37276343] Performing PTR host name lookup for 203.160.61.120
[2018.12.05] 01:17:47.786 [203.160.61.120][37276343] PTR host name for 203.160.61.120 resolved as 120.sub-61-160-203.hanastar.net.id.
[2018.12.05] 01:19:15.094 [17.110.71.106][3182004] Performing PTR host name lookup for 17.110.71.106
[2018.12.05] 01:19:15.094 [17.110.71.106][3182004] PTR host name for 17.110.71.106 resolved as mr28p00im-ztfo03015001.me.com.

Dave Feuer Replied

12/4/2018 at 6:56 PM

Same, have the period but it is resolving.

[2018.12.04] 20:51:44.258 [74.113.33.55][41565236] Performing PTR host name lookup for 74.113.33.55
[2018.12.04] 20:51:44.258 [74.113.33.55][41565236] PTR host name for 74.113.33.55 resolved as mta55.connetrix.com.

-Dave