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
Shouldn't a ServerFailedException simply invoke the next SimpleResolver? Currently, a (possibly transient) DNS error response seems to be irrecoverable.
ServerFailedException is created from a SERVFAIL response in LookupSession, regardless of the used resolver. If you're using a SimpleResolver this naturally ends the lookup.
For ExtendedResolver, well, good question. A SERVFAIL response is not a network error and thus is considered a completed lookup. I guess there could be a (new) option added to ExtendedResolver that continues on SERVFAIL responses.
Activity
ibauersachs commentedon Apr 7, 2022
Sorry for not getting back to this earlier.
ServerFailedExceptionis created from aSERVFAILresponse inLookupSession, regardless of the used resolver. If you're using aSimpleResolverthis naturally ends the lookup.For
ExtendedResolver, well, good question. ASERVFAILresponse is not a network error and thus is considered a completed lookup. I guess there could be a (new) option added toExtendedResolverthat continues onSERVFAILresponses.