Timeout from DNS resolver crashes program about fierce HOT 3 CLOSED

Thanks again for reporting! Yes! We should definitely continue searching even if one query times out. I'll commit a fix!

from fierce.

Looks good!

Might be worth moving the whole subdomain loop body to a function and wrapping it in a more general exception handler -- I think besides the EmptyLabel and Timeout exceptions, I might have seen another one. I'll report it if I see it, but a more general solution (skip ones in error? die, but allow restarting from next subdomain position?) might be worth considering.

from fierce.

Yeah, I need to find a way to handle exceptions better. It feels like I'm playing whack-a-mole with all the possible network/DNS errors. Perhaps the best way forward would be catching exceptions generally, logging them, and moving on. Although, some exceptions may be more dire than others. Hmm, probably requires some further investigation...

from fierce.