I would like to enable DNSBLACKLIST because I receiver since 3 days a lot of viruses …
I read about DNSblacklist it can be dangerous for the server and the server can crash after 1 hours after enable this …
I am afraid of that …i don’t understans what can I do to have a server not crashed after 1 hours
What can be the precaution for my domino not to crash if I enable DNSBlackList in the server Configuration …
I decided to put :
list.dsbl.org; relays.ordb.org;
Many thanks …
Subject: Enable DNSBLackList → Recommandation s
I have the blacklist enabled on a 601cf1 server on Win2000 without any problems. I am using: sbl.spamhaus.org It has also been enabled on several other machines without any problems.To block viruses I would also consider to enable the “verify connection hostname in DNS” option. Just be careful of any internal non notes clients that “relay” SMTP mail thru your server, they need to be in DNS or the hosts file on the server.
Subject: Enable DNSBLackList → Recommandation s
Some answers for you.
The server should not crash after 1 hour, 10 hours or 100 hours. DNSBL checking in Domino is very stable and you will only see bad behaviour if you have done something else wrong in the base OS or firewall.
If viruses are the main problem, then DNSBLs will probably not help - much. But choose wisely and they might just make a small impact.
a) Try dynablock.easynet.nl
That denies connections from dynamically assigned (e.g. home cable or DSL) connections and a large number of recent viruses propagate direct-to-MX and would be stopped by this.
b) Messagelabs now operates a DNSBL which lists for 48 hours IP addresses of known virus sources and some sites have reported good results using it. This DNSBL is at vbl.messagelabs.com - be warned; I have not tested this so have no idea how big the collateral damage may be.
Chris Linfoot
Subject: RE: Enable DNSBLackList → Recommandation s
And if that wasn’t enough, I now find that the DNSBL vbl.messagelabs.com has disappeared only a week or two after it became popular.
Who knows why, but DNSBLs as a defense against viruses look less relevant today than for some while…
Subject: Forum admin please note
Something odd going on here. I posted that response once and my browser window hung. Restarted browser, checked to see if post had made it to the forum. It hadn’t so posted again with same result. On fourth attempt it appeared to work and only one response by me was displayed in the forum.
This morning I check and there are four.
Something to do with session authentication and clustered Domino servers under heavy load I’ll wager…
Subject: Enable DNSBLackList → Recommandation s
Some answers for you.
The server should not crash after 1 hour, 10 hours or 100 hours. DNSBL checking in Domino is very stable and you will only see bad behaviour if you have done something else wrong in the base OS or firewall.
If viruses are the main problem, then DNSBLs will probably not help - much. But choose wisely and they might just make a small impact.
a) Try dynablock.easynet.nl
That denies connections from dynamically assigned (e.g. home cable or DSL) connections and a large number of recent viruses propagate direct-to-MX and would be stopped by this.
b) Messagelabs now operates a DNSBL which lists for 48 hours IP addresses of known virus sources and some sites have reported good results using it. This DNSBL is at vbl.messagelabs.com - be warned; I have not tested this so have no idea how big the collateral damage may be.
Chris Linfoot
Subject: Crash after one hour? Not here
We’ve had dnsbl enabled for quite some time on several ND6.x versions, without any crashes at all. Also, I haven’t heard of other people experiencing problems in this field. Are there any proven DNSBL related crashes? Any SPRs?
Subject: Nor here
We have used this for several months and NEVER had a server crash
Subject: RE: Nor here
look at that from Crashes Domino server
Subject: Did you read the whole thread?.. re: Nor here
Chris Linfoot outlined exactly what was wrong and recommended a set of solutions.
Why don’t you read Chris’s blog, which has about as much information on spam-fighting in Domino as has ever been provided anywhere.
Subject: Absolutely. Useful resource of information!
Subject: Enable DNSBLackList → Recommandation s
Some answers for you.
The server should not crash after 1 hour, 10 hours or 100 hours. DNSBL checking in Domino is very stable and you will only see bad behaviour if you have done something else wrong in the base OS or firewall.
If viruses are the main problem, then DNSBLs will probably not help - much. But choose wisely and they might just make a small impact.
a) Try dynablock.easynet.nl
That denies connections from dynamically assigned (e.g. home cable or DSL) connections and a large number of recent viruses propagate direct-to-MX and would be stopped by this.
b) Messagelabs now operates a DNSBL which lists for 48 hours IP addresses of known virus sources and some sites have reported good results using it. This DNSBL is at vbl.messagelabs.com - be warned; I have not tested this so have no idea how big the collateral damage may be.
Chris Linfoot
Subject: Enable DNSBLackList → Recommandation s
Some answers for you.
The server should not crash after 1 hour, 10 hours or 100 hours. DNSBL checking in Domino is very stable and you will only see bad behaviour if you have done something else wrong in the base OS or firewall.
If viruses are the main problem, then DNSBLs will probably not help - much. But choose wisely and they might just make a small impact.
a) Try dynablock.easynet.nl
That denies connections from dynamically assigned (e.g. home cable or DSL) connections and a large number of recent viruses propagate direct-to-MX and would be stopped by this.
b) Messagelabs now operates a DNSBL which lists for 48 hours IP addresses of known virus sources and some sites have reported good results using it. This DNSBL is at vbl.messagelabs.com - be warned; I have not tested this so have no idea how big the collateral damage may be.
Chris Linfoot