> My results are different and I DO testing. The big cache is the > strongest point in favor of OpenDNS and GoogleDNS. The Benchmark > Utility may bring you some surprises.
The "big cache" may also become a "big headache" :) and I'm not kidding, in my experience it's better to use a local DNS resolver or, if possible, more than one, and especially when it comes to a DNS which serves an SMTP server (or a filter, like ASSP), first of all, you can tune your cache and won't rely on 3rd parties to have the DNS up and running, then, your cache will fill up with hosts which are "hitting you" not with bots hitting just the other side of the globe, then, and not least important, using a local DNS you may setup slave-copies of several zones, starting from the root (.) one up to a bunch of DNS or URIBL lists and that would speed up things a whole lot... and btw you will LOOSE such an ability in case you'll use an external DNS; bottom line, if you can't use your own resolver (or don't know how to setup one) then... use OpenDNS or whatever else, but if you're SERIOUS about performances, then kick off all those "public resolvers" and use YOUR own one(s) ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
