Other name resolution impacts, as by-products of the Dyn event (e.g. recursive queries limit reached)

Have not seen any mentions yet, so thought of asking here: has anybody paid
attention to other name resolution issues, even outside the Dyn hosted
services directly sourced ones? I am talking about what we observed, as
result of:


i.e. "active queue" filled with the Dyn caused event, but leaving thusly no
"room", at times, for valid recursive queries, inclusive of internal name
resolution, where the SOA sits in another tier (e.g. GSLBs).

One possible mitigation for such scenarios is:


Any other related events, on other platforms or configurations?