Re: dig ignores +notcp when doing IXFR (DiG 9.5.0-P2)

2013-12-04 Thread Mark Andrews
In message , Matthew Pounsett writes: > > On 2013-12-04, at 21:22 , Mark Andrews wrote: > > > > > The options are processed left to right so the +notcp has to be > > after the ixfr=. > > There are two reasons I don't understand why this is the case. > > 1) Since there is only one query in the co

Re: dig ignores +notcp when doing IXFR (DiG 9.5.0-P2)

2013-12-04 Thread Matthew Pounsett
On 2013-12-04, at 21:22 , Mark Andrews wrote: > > The options are processed left to right so the +notcp has to be > after the ixfr=. There are two reasons I don't understand why this is the case. 1) Since there is only one query in the command, I don't understand why "left to right" matters.

Re: dig ignores +notcp when doing IXFR (DiG 9.5.0-P2)

2013-12-04 Thread Mark Andrews
The options are processed left to right so the +notcp has to be after the ixfr=. e.g. dig ixfr= zone +notcp Note, named will for the use of TCP in its UDP response. Below is a query log of ixfr requests with and without tcp. 'T' indicates a TCP connection. 05-Dec-2013

dig ignores +notcp when doing IXFR (DiG 9.5.0-P2)

2013-12-04 Thread Matthew Pounsett
I'm trying to debug an IXFR problem with a client, and using dig in its place to compare IXFR requests between it and the misbehaving client. I noticed that when I do an IXFR with dig it defaults to TCP rather than UDP. I tried forcing it over with +notcp but I still get a TCP query. >From t