Dear Chris, On Mit 27.07.2011 10:59, Chris Lewis wrote:
On 7/26/2011 10:41 PM, Jared Johnson wrote:
[snipp]
Now each of our qpsmtpd instances has their own rbldnsd (serving ~700Mb zone consisting of almost all the DNSBLs we use as one merged zone) plus the "Unbound" DNS server package. This is probably overkill even at 30+ million emails/day, but it works extremely well. The unbounds are configured to route DNSBL queries to the co-resident rbldnsds (they can failover to other server rbldnsds), DNS queries of our infrastructure to the corporate bind9 instances, and external queries through normal recursive resolution (involving the root servers if necessary), and unbound caches all of it.
[snipp]
Unbound is easy to install and configure. I chose not to use Bind9 partially because of previous experiences with much older versions. I did run DJB's dnscache for a while instead, but unbound works so much better. Avoid using dnscache for this. I can explain why if people are interested.
Please, yes. I use dnscache on my home network and would like to know why anybody decide to move from dnscache. Thank you for your detail infos. I will try to setup the http://unbound.net/ as caching server. BR Aleks
