TazaTek wrote: > Eric Shubert wrote: >> I gather that you're trying to reduce the load on the network by >> essentially using the blacklist_ip file as a sort of RBL facility. >> Is RBL processing actually creating that much network traffic, or is >> this just a guess? >> >> Do you have a caching nameserver installed on your server? You should, >> as that will drastically reduce network traffic. >> >> How many / which RBLs are you presently using? You shouldn't need more >> than a few. Also, if you've specified an unresponsive or slow RBL, that >> can hinder your performance quite a bit > I had some problems with my nameserver last week ... long story... so I > was looking at my RBL list, and thought that I could reduce the overhead > of the RBL lookups by adding the IP to my blacklist_ip file... I've got > the makings of a script that will find all the new RBL rejects, add them > to the blacklist_ip file and then unique them... I would suspect that > there could be 10's of thousands of IPs in this file - eventually - but > over time could really have an impact on performance (increase my server > load, but decrease network traffic) I suppose that it could be > considered polite to do this to the RBL servers by reducing their > overhead as well. > > I belive (but not 100% sure) that I have a cacheing nameserver. I'm > using the default that plesk gives me (named), but I haven't modified it > myself. Is there anything simple I can do to check or configure? I'm > technical, but never played with named, so don't really have a clue on > where to start looking ....
I'm not familiar with plesk, but checking dns resolution is easy enough. First, check your /etc/resolv.conf file to see what nameservers are configured. An entry of 127.0.0.1 (localhost loopback address), preferably first in the list, indicates that the mail server's dns resolver will be used. You can verify which nameserver is answering requests using the "dig" command: # dig spamdyke.org will return information for spamdyke.org domain's server. Near the end of the output it will indicate the IP address of the DNS server that satisfied the request. "dig" is very flexible, and can also be used to query specific name servers. For instance, you could: # dig @127.0.0.1 spamdyke.org to test your localhost dns server specifically. See "man dig" for all it can do. If your localhost nameserver isn't working properly let us know and I'm guessing that someone here knows enough to help you get it working, although the plesk list (I'm assuming there is one) might be a better place for that sort of help. If your server's caching nameserver (resolver) is working ok, then you're on to Sam's recommendation (a slick solution btw). I'd want to be sure that the localhost resolver is working properly though before going in that direction. -- -Eric 'shubes' _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
