zone transfers sticking on one port?

[Chris Fabri]

At 03:19 PM 3/16/2004, Barry Margolin wrote:
>In article <c37om5$2vok$1 at sf1.isc.org>, Jim Reid <jim at rfc1035.com>
>wrote:
>
> > >>>>> "Barry" == Barry Margolin <barmar at alum.mit.edu> writes:
>
> >
> >     Barry> BIND asks the OS to select a port when it first starts up.
> >     Barry> So for the life of that named process it always uses the
> >     Barry> same port number.
>
>
>I was describing the UDP socket, not the TCP socket, since the OP's
>filter was blocking UDP.  TCP works as you said (you can't reuse the
>same socket for multiple connections), but is irrelevant to the
>discussion.


Sorry, i'm going to be redundant, I touched on this in an earlier email.

If this is the case, then when I happen to magically stumble onto this port 
on startup, it won't work at all.  But what I saw was it working for a 
while, then the error started.    Am I missing some other portion of what's 
going on here with the port selection?   chris