Re: [DNSOP] Unexpected behaviour of dig +trace

On 28/03/2014 19:44, Doug Barton wrote:
> On 3/26/2014 9:41 AM, Evan Hunt wrote:
>> On Wed, Mar 26, 2014 at 06:52:44PM +0800, Warren Kumari wrote:
>>> "Feature", but does catch many folk by surprise.
>>> I'd written a patch and given it to someone at ISC that makes dig
>>> output a warning message if you hand it both the "+trace" and
>>> "@server" options. Dunno what happened, but never got integrated...
>>
>> My apologies for not sending feedback directly. (That's something
>> we really need to work on.) IIRC, we opted to clarify the documentation
>> rather than add a warning to dig itself.  There's also a knowledge base
>> article on this topic at http://tinyurl.com/o37rpgm.
> 
> Given that the number of people using the tool vastly exceeds the number
> who read the docs, multiplied by the number of times this comes up on
> bind-users (where this discussion should have happened in the first
> place), IMO also putting the warning in the tool makes more sense.
> 
> FWIW,
> 
> Doug
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

Feature request is #31814 (I merged Warren's original suggestion with a
later one asking for much the same).

Comments noted and I've 'prodded' this one for you (although the outcome
may depend on other factors, including future plans for the new delve
tool - see BIND 9.10.0b2).

Cathy