[f-nsp] Load balancing DNS servers on a ServerIron 8XL
Tom Samplonius
tom at uniserve.com
Wed Sep 27 16:01:38 EDT 2006
DNS2 might be too slow to respond, or lost a few hundred requests.
From reading the docs, the SI has special handling for DNS requests. It
removes the connection immediately after the response is processed. So if there
is no response, the connection will stay around until it is aged. So if DNS2
just discarded a bunch of requests, they would sit around as connections.
Tom
On Wed, 27 Sep 2006, Drew Weaver wrote:
> Howdy list, been using foundry load balancers for quite some time.
> I'm having a hard time understanding one issue.
> pertinent config:
>
> server real DNS1 10.1.0.2
> port dns
> !
> server real DNS2 10.1.0.3
> port dns
>
> server virtual DNS 192.168.0.89
> predictor round-robin
> port dns
> bind dns DNS1 dns DNS2 dns
>
> pretty straightforward right?
>
> OK, well I was looking at the real server stats and I noticed that DNS1
> had 37 active connections whilst DNS2 had 781 active connections all of
> the servers/pcs/devices are set to use 192.168.0.89 as their resolver,
> so why is there such a hugely unproportinate number of connections
> hitting DNS2?
>
> Thanks!
>
> -Drew
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
More information about the foundry-nsp
mailing list