Randomly ConnectTimeout instead of ConnectError (Name or service not known) #2878
Unanswered
powellnorma
asked this question in
Potential Issue
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Version 0.25
Hi, not sure if this counts as bug, but I was relying on a
ConnectErrorbeing thrown that contains the stringName or service not knownin case the A-Record was missing, to detect DNS related issues. But in the current case only half the time it works as intended, in the other half a stack trace like below gets thrown.I do have strict timeout requirements (4 seconds), but I thought that the DNS resolution does not count into ConnectTimeout?
FWIW this ruby library does not count DNS-Delays into ConnectTimeout.
Is there a way to reliably get a
ConnectErrorin such cases? Or maybe we can add a ResolveTimeout? Thank you.Beta Was this translation helpful? Give feedback.
All reactions