Unreachable IP in allow transfer

[Barry Margolin]

In article <grfimj$1gjg$1 at sf1.isc.org>,
 "Hayward, Bruce" <Bruce.Hayward at mtsallstream.com> wrote:

> We were chasing why we were seeing slow responses when busier (running
> 9.5.1-P1/Solaris 10).
> 
> =20
> 
> In our named.conf we had an allow-transfer for IP 123.123.123.123 for
> zone fredderf.com (IP/names have been changed to protect the innocent):
> 
> =20
> 
> If the IP was not reachable  we see a timeout where it tried for 224.694
> secs.
> 
> =20
> 
> I believe that this was holding up one or two processes - so the rest
> had to wait
> 
> =20
> 
> >From the xfer.log
> 
> 31-Mar-2009 06:38:50.591 client 123.123.123.123#54651: received notify
> for zone 'fredderf.com'
> 
> 31-Mar-2009 06:38:51.482 transfer of ' fredderf.com/IN' from
> 123.123.123.123#53: failed to connect: timed out
> 
> 31-Mar-2009 06:38:51.482 transfer of 'fredderf.com/IN' from
> 123.123.123.123#53: Transfer completed: 0 messages, 0 records, 0 bytes,
> 224.694 secs (0 bytes/sec)
> 
> =20
> 
> Thoughts?

This look more like the result of "masters { 123.123.123.123;}".  If a 
slave can't connect to the master, it will time out when it tries to 
perform a zone transfer.

I'm not sure why this would cause slow response times, though.  I assume 
the zone transfer is done in a separate thread from query processing.

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***