In recent versions of BIND ANY queries still work pretty well as a debugging tool when `minimal-any` is turned on, because you get the traditional full-fat response over TCP, and dig automatically uses TCP for ANY queries.
I implemented `minimal-any` in BIND to reduce problems caused by large responses in DDoS attacks. It helps in situations when RRL is not quite enough.
Awesome, thanks a lot for that! I was indeed mostly using ANY through dig (as do most, I suspect), glad to know there's still a way to make it work!
Many people were. I and others have repeatedly pointed out that "ANY is not ALL" over the decades. As a randomly selected example, here is Paul Jarc back in 2004:
* https://dns.cr.yp.narkive.com/MSBPuJCn/newbie-question-about...
I liked the ANY type as a convenience and debugging tool, but I guess the disadvantages far outweigh that perceived convenience. And now that I read about the actual semantics of ANY with respect to caches, turns out I was using it wrong anyway!