dns server redundancy
Elzey, Blaine A (Blaine)
belzey at lucent.com
Fri Jan 14 03:59:55 UTC 2005
What is "rndc recursing", and how does one implement that rndc command?
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Mark Andrews
Sent: Thursday, January 13, 2005 5:25 PM
To: Kevin Darcy
Cc: bind-users at isc.org
Subject: Re: dns server redundancy
> Kris wrote:
> >What's the best way to have dns server redundancy? In my case, we have
> >issues with running out of recursive queries (we've jacked that limit up to
> >10000). From what I've read, it seems my best bet is to add more
> >nameservers to the mix. If I set up the zone information for the nameserver
> >as so:
> >nameserver 600 IN A 10.0.0.3
> >nameserver 600 IN A 10.0.0.4
> >nameserver 600 IN A 10.0.0.5
> >does this mean that requests for nameserver will be divided equally among
> >the 3 servers listed? Will this, then, help alleviate the issue we're
> >having with server failure due to excessive recursive lookups?
> No, the address that a name resolves to has nothing logically to do
> with what nameserver you ask to resolve it. If you want to spread out
> the load from a bunch of recursive clients the most straightforward way
> to do so is by changing the resolver configurations on those clients.
> This isn't so hard if you're using DHCP; in fact, some DHCP products
> have a "rotate" option which automatically gives out different
> permutations of a given resolver list to different DHCP clients,
> specifically for the purpose of spreading out query load.
> Another option, I suppose, is to put load-balancer(s) of some sort
> between your nameservers and their clients...
> - Kevin
Or find out what queries you are stalling on and fix the problem.
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users