4
Getting a lot of 600 Failed to connect to the recipient's mail server. No DNS information was found
Problem reported by Brian Bjerring-Jensen - 9/11/2023 at 12:54 AM
Submitted
Remote Server returned: '600 Failed to connect to the recipient's mail server.  No DNS information was found for the 'xx.xx' domain. Status: 544 5.4.4 Host not found (not in DNS).'

Getting a lot of these. Thought is was DNS related so I changed from our internal DNS to QUAD9 and OpenDNS.

Didnt help.

Any ideas?

6 Replies

Reply to Thread
1
Kyle Kerst Replied
Employee Post
Hey Brian, sorry to hear you're seeing DNS errors. Can I have you submit a ticket on this so we can help take a look? We have a debug log or two we should be able to use to help track this down.
Kyle Kerst
System/Network Administrator
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Brian Bjerring-Jensen Replied
Hi Kyle :)

Done.
2
Kyle Kerst Replied
Employee Post
Thanks Brian! I'll note the community post on the ticket (if you didn't already) so we can circle back here with an update when we get to the bottom of it!
Kyle Kerst
System/Network Administrator
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Duarte Replied
Hi,

We are using the latest build (8657) and we also just had an episode related to DNS queries.

We do not use the SmarterMail DNS cache. When we used nslookup on the server we were able to carry out queries, but in SmarterMail the spool accumulated messages, because were unable to query blacklists or discover the MX records of the domains for delivery.

We rebooted and the situation returned to normal...
0
Brian Bjerring-Jensen Replied
Use the primary ip of the interface under SMTP out. :)

We havent had issues since.
1
Duarte Replied
Yes, we have this set on all servers. That's not it...

Furthermore, there are performance problems. We compared the average time of 3 servers in build 100.0.8251.30716 (Aug 4, 2022) with 3 servers in most recent build (100.0.8657.28945, 100.0.8657.28945 and 100.0.8601.21923) and the average time to consult blacklists increased significantly.

In the older build only 1 RBL has the average time longer than 500ms, in the most recent builds more than 18 RBLs are longer than 1000ms, including two with 7500 ms. (They are identical servers with the same anti-spam settings).

Reply to Thread