Fixed dns lookup in case of server close connection with econnrefused #1557
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.
In case of ns server responded with {error, econnrefused} we should close udp connection and start new one for next ns server.
In my case there is
/etc/resolve.conf
with folowing structureand i tried to resolve an srv record, but local dns server (127.0.0.1) crashed on request.
In case of first ns server crashes erlang should use next dns server (8.8.8.8), but request crashes on erlang side with {error,einval} badmatch.
Here is simple example what's going on if we dont close connection after first {error, econnrefused}:
The solution is to close udp connection on {error, econnrefused} message