dig ignores +notcp when doing IXFR (DiG 9.5.0-P2)
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 the man page: +[no]tcp Use [do not use] TCP when querying name servers. The default behavior is to use UDP unless an AXFR or IXFR query is requested, in which case a TCP connection is used. This implies to me that it is simply the default to use TCP for *XFR, but one should be able to override it. Is that the correct interpretation of the man page? Even if that is not the correct interpretation, it seems to me that since IXFRs can and do happen over UDP, it should be possible to tell dig to do that. Is this a bug, or a design flaw? - Matt ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: dig ignores +notcp when doing IXFR (DiG 9.5.0-P2)
On 2013-12-04, at 21:22 , Mark Andrews ma...@isc.org wrote: The options are processed left to right so the +notcp has to be after the ixfr=serial. 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. If you could do something like dig IN IXFR=serial example.com +notcp IN A www.example.com +tcp then sure.. because changing the order of options would be ambiguous, but you can't do that. 2) dig is generally very forgiving of argument order, so I don't see why the location of +notcp would be any different. dig +short @8.8.8.8 IN A cbc.ca 159.33.3.85 dig @8.8.8.8 IN A cbc.ca +short 159.33.3.85 dig IN A cbc.ca +short @8.8.8.8 159.33.3.85 Note, named will for the use of TCP in its UDP response. What verb is missing from this sentence? ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: dig ignores +notcp when doing IXFR (DiG 9.5.0-P2)
In message c60198c7-b559-4e7d-bbcb-e3ba51687...@conundrum.com, Matthew Pounsett writes: On 2013-12-04, at 21:22 , Mark Andrews ma...@isc.org wrote: The options are processed left to right so the +notcp has to be after the ixfr=serial. 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. If you could do something like dig IN IXFR=serial example.com +notcp IN A www.example.com +tcp then sure.. because changing the order of options would be ambiguous, but you can't do that. Because tcp mode isn't a tri state (unset, true, false) but a boolean and ixfr=serial changes it the default (false) to true. IXFR is documented as setting TCP mode. 2) dig is generally very forgiving of argument order, so I don't see why the location of +notcp would be any different. In these examples the arguments are independent of each other and set a single thing (even +short). The are others that set multiple things. dig +short @8.8.8.8 IN A cbc.ca 159.33.3.85 dig @8.8.8.8 IN A cbc.ca +short 159.33.3.85 dig IN A cbc.ca +short @8.8.8.8 159.33.3.85 Note, named will for the use of TCP in its UDP response. s/for/force/ What verb is missing from this sentence? -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
