Hi

I've found out to define a secondary DNS server in spamfilter.

Problems is, when it should use the secondary server (when primary is down) I get a socket error instead of lookups.

This results in than all domains has invalid MX records and therefore are rejected.

Im running Spamfilter 2.1.2.402 Registered on a Windows 2003 server, any ideas?

The primary DNS server is a Windows 2003 DNS server located at same machine as spamfilter.

This is a output from the logfiles, when primary server is down.

My server are able to lookup adresses from the secondary server.

01-17-05 08:16:03:923 -- (1724) Connection from: xxx.xxx.xxx.xxx  -  Originating country : United States
01-17-05 08:16:05:375 -- (1724) Resolving xxx.xxx.xxx.xxx - Error occurred during DNS lookup: Socket Error # 10054 Connection reset by peer.
01-17-05 08:16:05:375 -- (1724) - Invalid MX record -
01-17-05 08:16:05:375 -- (1724) xxx.xxx.xxx.xxx - Mail from: dsa@dsa.xx To: dsadsa@todomain.xx will be rejected
01-17-05 08:16:06:467 -- (1724) EMail from dsa@dsa.xx to dsadsa@todomain.xx was received and quarantined. Size: 1 KB, 1024 bytes
01-17-05 08:16:06:507 -- (7732) Time to add Msg to Bayes corpus:9
01-17-05 08:16:06:717 -- (1724) Disconnect

Best regards...

Torsten Christiansen

Torsten,

Can you please check to see if when you stpo the DNS service in Windows 2003, the DNS port 53 is actually shut off and Windows is not listening on it? You can verify this by issuing from a DOS prompt:

telnet aa.bb.cc.dd 53

if a connection is established, then Windows is not really releasing the DNS port and SpamFilter may be getting "confused" as to if DNS is available or not, and we may need to investigate on what is really happening.

Torsten,

You were absolutely correct, we were able to duplicate the problem now. I believe we fixed it, and a pre-release patch is available in build 2.1.2.403 which we have just uploaded in the registered user area of the website. If you'd like to try it, please let us know if it fixes the problem in your environment as well.