Return an error rather than do nothing when having no valid result #138
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, if overture gets nothing from all of its backends, overture will not reply to the DNS query, cause the client to wait for a response.
Actually, overture should return something rather than keep the client waiting.
I'm facing this problem because many domains don't have an AAAA record. When using curl, curl wants to try ipv4 and ipv6, so curl make an AAAA query to the overture, but overture doesn't reply until timeout, cause curl to start ipv4 query very slow.
However, dig has the same problem.
Dig return after 15 seconds.