add dns.REFUSED #1458
Merged
add dns.REFUSED #1458
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a local DNS server does not allow recursion, it can return the error "Query Refused" as told in `**RFC1035 Section 4.1.1 RCODE 5**: Refused - The name server refuses to perform the specified operation for policy reasons. For example, a name server may not wish toprovide the information to the particular requester, or a name server may not wish to perform a particular operation (e.g., zone transfer) for particular data.` So this is another case which the request shoud go to the next resolver.
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When a local DNS server does not allow recursion, it can return the error "Query Refused" as told in
**RFC1035 Section 4.1.1 RCODE 5**: Refused - The name server refuses to perform the specified operation for policy reasons. For example, a name server may not wish toprovide the information to the particular requester, or a name server may not wish to perform a particular operation (e.g., zone transfer) for particular data.So this is another case which the request shoud go to the next resolver.NB! Nodemailer is frozen, so no new features please, only bug fixes.