Re: high performance caching bind server
On Mon, Mar 12, 2007 at 11:15:22AM -0600, Michael Loftis wrote:
>
>
>--On March 12, 2007 9:57:26 AM +0100 Gregor Hermens <gregor@a-mazing.de>
>wrote:
>
>>Hi,
>>
>>Am Montag, 12. M?rz 2007 10:43 schrieb Jean-Paul Blaquiere:
>>>What do people use/recommend for high performance name serving?
>>>I currently have a few servers running bind9 (9.2.4-1sarge2) serving
>>>an average 750 requests per second running on Debian/sarge.
>>>kernel-2.4.32 (the stats say: low: 0.00, peak: 2500, avg: 750)
>>...
>>>We're either going to replace these, or if there is something we can do
>>>to poke it and make them happier, we'll do that.
>>
>>take a look at dnscache:
>>
>>http://packages.debian.org/stable/net/djbdns-installer
>>
>>It's a caching-only server, so you don't get the overhead of using a
>>full-featured bind. I have a couple of them running for years without any
>>problem.
>
>I can't really recommend dnscache because it breaks the DNS protocol in
>various ways, but the *real* problem is it doesn't do round robin, so your
>dns server always returns the same answer instead of round robin-ing
>through A records and such that are identical except for the content.
you're not recommending dnscache, you are recommending against it.
but really you are spreading FUD.
a) what various ways are you referring to?
b) I'm not sure what the distribution is, but it sure looks round-robin...
# dnsip testdnscache.galis.org
1.0.0.17 1.0.0.6 1.0.0.15 1.0.0.13 1.0.0.8 1.0.0.18 1.0.0.5 1.0.0.2
# dnsip testdnscache.galis.org
1.0.0.2 1.0.0.5 1.0.0.18 1.0.0.8 1.0.0.17 1.0.0.6 1.0.0.15 1.0.0.13
# dnsip testdnscache.galis.org
1.0.0.5 1.0.0.8 1.0.0.2 1.0.0.6 1.0.0.15 1.0.0.13 1.0.0.17 1.0.0.18
# dnsip testdnscache.galis.org
1.0.0.18 1.0.0.13 1.0.0.6 1.0.0.8 1.0.0.15 1.0.0.5 1.0.0.2 1.0.0.17
# dnsip testdnscache.galis.org
1.0.0.18 1.0.0.13 1.0.0.2 1.0.0.5 1.0.0.6 1.0.0.15 1.0.0.17 1.0.0.8
# dnsip testdnscache.galis.org
1.0.0.5 1.0.0.2 1.0.0.13 1.0.0.6 1.0.0.18 1.0.0.8 1.0.0.17 1.0.0.15
testdnscache.galis.org is 1.0.0.1-20, 20 A records assigned to it,
and is hosted by tinydns.
I would recommend dnscache before the OP had a problem BTW.
// George
--
George Georgalis, systems architect, administrator <IXOYE><
Reply to: