[192325] in North American Network Operators' Group
Other name resolution impacts, as by-products of the Dyn event (e.g.
daemon@ATHENA.MIT.EDU (Stefan)
Tue Oct 25 09:25:58 2016
X-Original-To: nanog@nanog.org
From: Stefan <netfortius@gmail.com>
Date: Tue, 25 Oct 2016 08:14:27 -0500
To: "NANOG Operators' Group" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
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:
https://community.infoblox.com/t5/Support-Central/Support-Central-KB-118-What-does-quot-no-more-recursive-clients/ba-p/6321
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:
https://community.infoblox.com/t5/Support-Central/Support-Central-KB-3451-Configuring-CLI-commands-for-Automated/ba-p/6327
Any other related events, on other platforms or configurations?
***Stefan
