SMTP & DNS Question

Version:

iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)

libimta.dll 5.2 HotFix 2.14 (built 16:39:09, Aug 8 2006)

Microsoft Windows 2000 Professional version 5.0 Service Pack 4 (Build 2195)

Hi all,

A few days ago our smtp services slowed to a crawl; I could not telnet to port 25 from the server itself (connection refused). When I disabled the NIC smtp services returned and I could telnet into port 25 from the console and get the 220 response. This situation persisted for more than 20 hours (accompanied by frantic efforts to find and fix the problem) after which it cleared. My belief is that the DNS server was not doing recursive lookups and smtp was waiting for an answer that never came, tyeing up all threads. I wish I'd thought to test this during the crises, but I only did nslookup, non recursive, from the server to see if I could reach the DNS server; I could. The network & DNS people here believe that the problem is internal to the Messaging Server - a mangled query or not using the DNS server defined for the system, or . .

Below are snippets from some of the log files during the crises. I would like to know if my theory is a possible explanation; Would the smtp service wait for the recursive reply, tieing up all the treads? Is there a way to (temporarily) tell smtp to accept non authoritative answers? Does this entry of the tcp_local_master - ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 - indicate that this is a reply, not a logging of the query (query bit set to 1)? Any ideas, thoughts, or suggestions will be appreciated.

Thanks,

Steve

mail.log_current

Failed MX lookup; try again later

tcp_local_slave.log

Invalid socket descriptor, status = -1

tcp_local_master

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2155

;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;;intonewhy.com, type = MX, class = IN

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2139

;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;;QUZUSOKO.phydam.info, type = MX, class = IN

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2123

;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;;melloexchange.com, type = MX, class = IN

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2123

;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;;bounce.tainoncount.com, type = MX, class = IN

[2592 byte] By [liebhartsa] at [2007-11-27 9:33:42]
# 1

Hi,

DNS resolution on a windows system is an inexact science. Have a read through the following mail thread, which will provide some pointers/general discussion on how messaging server handles DNS resolution and the various registry keys to check etc.:

http://lists.balius.com/pipermail/info-ims-archive/2007-May/028031.htm

If this issue occurs again, make sure you collect the output of ./imsimta dispatcher_stats_tty which will output all of the active email connections. Also try connecting to port 587 (submit port) which will tell you if the dispatcher itself has hung or if you have hit a dispatcher limit just on port 25 and may need to tweak the limits (dispatcher.cnf).

DNS resolution times are especially important if you are using some kind of DNS lookup in the PORT_ACCESS mapping table as the dispatcher won't return the usual SMTP banner until the resolution has occurred. Is this the case with yourself?

Ideally however I would recommend looking towards installing Messaging Server 6.3 on a Solaris x86 system and moving off your current platform (no more windows releases going forth and iMS5.2 is in limited support/EOL status).

Regards,

Shane.

shane_hjortha at 2007-7-12 22:55:51 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2
Shane,Thank you! The information in the Info-iMS email list was helpful, and with the additional suggestions should allow us to pin down the problem should it recur. We don't have any sort of DNS lookup in the mappings.Steve
liebhartsa at 2007-7-12 22:55:51 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...