If the named instance is responding from authoritative data, it is not
initiating any outbound transaction, and therefore "timeout" has no
meaning in that context.
- Kevin
On 5/19/2014 8:00 PM, Shawn Zhou wrote:
What about non-recursive queries?
In particular case, our test
What about non-recursive queries?
In particular case, our test queries are non-recursive and we expect the name
server should have answers. We are sending test host with very high query rate
so BIND may be too busy to respond to all the queries.
On Monday, May 19, 2014 4:25 PM, Kevin Darcy
If a client sends a recursive query to the BIND instance, and that
instance needs to fetch the answer from one or more other upstream
sources, then my understanding is that the "resolver-query-timeout"
global option (see the BIND docs) controls the timeout for each one of
those upstream transac
I am looking at some scripts that use IO::Socket::INET and IO::Select for
testing BIND.
UDP sockets are created use use IO::Socket::INET and sockets are polled via
IO::Select at 6-second interval.
my $sock = IO::Socket::INET->new(
PeerHost => $server,
PeerPort =
4 matches
Mail list logo
