http://bugzilla.spamassassin.org/show_bug.cgi?id=3500
------- Additional Comments From [EMAIL PROTECTED] 2005-10-01 09:48 ------- (In reply to comment #18) IIRC RBLDNSD doesn't cache, it is just lean and mean. So... First things first, DNS caching is very efficient, not just for you but for the whole Internet ecosystem. Proper DNS configuration is paramount if you do anything other than minor traffic in order to get a quick answer. Running a caching nameserver on the local machine is the "must do first" task for efficiency with network tests enabled. (ok second task after installing NET::DNS ;>) IMHO this should be in the readme under "Optional Modules" and before "What Next?" ;) The next step it to make sure your ISP's nameserver is your next point of contact, because it is caching queries for all the other SA users they have and their DNS is close and quicker than using the RBL directly for everything. Running a local caching nameserver that forwards requests to a local rbldnsd (see Jeff's comment #6) is a possible/minor enhancement, IMHO for the 200+mails/min club. RBL NS's don't "talk" to every SA install, they almost exclusively "talk" with ISP's name servers because of all the caching that's going on. It's just not fair to expect them to setup and admin sync accounts for everyone who want the extra 0.005% out of SA. The traffic generated by the rsync jobs is not insignificant and it falls on the owner of the RBL to foot that bill for the traffic and resources to complete service all their rsync peers. I should think the last thing they want is that admin becoming a daily task for them. Lastly if a bunch of people decided to set their RBL nameserver directly to the NS's of the RBL's (clueless, because I can, misguided security, whatever) they would probably consume almost as much bandwidth from the RBL server their ISP. That can't be good for anyone in the long term. If you really really really want to roll your own local rbldnsd and do without caching nameservers then couldn't you configure your local NS to serve up fake/local NS records for the zones your using direct to your rbldnsd box. Job done? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
