Untested: "spawn" several several PoCo::Client::DNS aliases. You could
either strictly round-robin your posting to the spawned resolvers in
start_next_lookup. Or, if you really want to balance things out, keep up
with how many queries each resolver is currently handling by incrementing
some counter at the start of start_next_lookup and decrementing it in
got_answer. Then choose a resolver accordingly (don't forget to randomly
pick from resolvers that are available).
-
Lance Braswell - + 1 469 357 6112
"Lari Huttunen"
<[EMAIL PROTECTED]
tu.net> To
<[email protected]>
04/28/2005 01:45 cc
PM
Subject
Fwd: Re:
Please respond to POE::Component::Client::DNS woes
<[EMAIL PROTECTED]
tu.net>
Oops, sorry forgot to CC: the list.
------ Original Message ------
Subject: Re: POE::Component::Client::DNS woes
To: Mathieu Longtin <[EMAIL PROTECTED]>
From: "Lari Huttunen" <[EMAIL PROTECTED]>
Date: Thu, 28 Apr 2005 21:39:57 +0300
On 21:00:51 28/04/2005 Mathieu Longtin <[EMAIL PROTECTED]> wrote:
> Hum, if the first DNS servers works, why should it try the
> other ones?
To even out the query load between the different servers, but yes I see
your point. :) Which means that I will probably have implement some kind
of a round-robin logic for the queries, maybe? I would like to use the
exisiting modules but what I was looking for is distribution of the query
load between many different nameservers.
--
Sincerely,
Lari Huttunen
