RE: Dig: specifying a source port

Joe,
You've hit the nail on the head before I had the chance. If it was easy
enough to change from our customers' beliefs and expectations, then I would.
But it's not.

Jim,

The patch actually came from the bind users list
(http://marc.theaimsgroup.com/?l=bind...5736501990&w=2).

I'm no programming whiz, but the way I read this code is that all it's doing
is allowing a source port to be specified and used, not changing the way
that the connection is torn down. I don't feel I need your recommendation in
order to understand this. Even without the patch, the connection remains
open in a TIME_WAIT state. So I think my question is appropriate for this
list and it still stands.

-Jason

> On Wed, Aug 04, 2004 at 07:24:58PM +0100, Jim Reid wrote:
> > >>>>> "Jason" == Jason Richards <jrichards@gci.com> writes:
> >
> > Jason> I need to be able to specify the source port (since bind is
> > Jason> configured with transfer source port 53). I know this isn't
> > Jason> natively available, but I found a patch online for dig
> > Jason> v9.2.2 and have seemed to be able to make it work under
> > Jason> 9.2.3.
> >
> > Insisting zone transfers requests use a specifc port number is dumb.
> > Please don't do that.
>
> Some firewalls [;-(] still require that the source port be 53 as in the
ancient versions of BIND! While this would > normally be useless, if that
is the case in his situation, it would be necessary.


-- Binary/unsupported file stripped by Ecartis --
-- Type: application/x-pkcs7-signature
-- File: smime.p7s