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
I'm branching this issue off of #1707. The response generally is SERVFAIL when using 8.8.8.8:53 and 1.1.1.1:53, and it takes quite some time for the server to reply. Interestingly, I do not see any of this issue when using the resolver provided by Vodafone Italia, SpA. (I'm curious to figure out why!)
The legacy TH reports the response correctly. The new TH times out. I suspect the reason lies in the fact that our timing out strategy is not optimal. As an additional issue, I think we don't map SERVFAIL correctly: we say that the upstream server is misbehaving, which is what Go does. But this case is important enough to have its own mapping.
The reason why I am branching off this issue is that it's large enough to deserve its own time for investigating and fixing.
The text was updated successfully, but these errors were encountered:
I'm branching this issue off of #1707. The response generally is
SERVFAIL
when using8.8.8.8:53
and1.1.1.1:53
, and it takes quite some time for the server to reply. Interestingly, I do not see any of this issue when using the resolver provided by Vodafone Italia, SpA. (I'm curious to figure out why!)The legacy TH reports the response correctly. The new TH times out. I suspect the reason lies in the fact that our timing out strategy is not optimal. As an additional issue, I think we don't map
SERVFAIL
correctly: we say that the upstream server is misbehaving, which is what Go does. But this case is important enough to have its own mapping.The reason why I am branching off this issue is that it's large enough to deserve its own time for investigating and fixing.
The text was updated successfully, but these errors were encountered: