dingo
dingo copied to clipboard
avoid parallel lookups for same name
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.
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?