You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During today's DynDNS outage I noticed dingo will issue a query for the same name in all threads given enough applications ask for it (eg. github.com). We should avoid this, eg by letting the query go back / timeout before trying in another thread.
The text was updated successfully, but these errors were encountered:
Is having dnsmasq fronting dingo an alright setup to avoid bloat and less-scalable computational requirements? would this subject dingo to a DoS attack surface?
During today's DynDNS outage I noticed dingo will issue a query for the same name in all threads given enough applications ask for it (eg. github.com). We should avoid this, eg by letting the query go back / timeout before trying in another thread.
The text was updated successfully, but these errors were encountered: