feat(NODE-2939): update hostname canonicalization opts #3129
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.
Description
Updates
CANONICALIZE_HOST_NAME
options to accepttrue
,false
, "none", "forward", "forwardAndReverse".What is changing?
When canonicalizing the host name when using GSSAPI, the driver will now behave as follows for these values:
true
or "forwardAndReverse": Performs a forward DNS lookup of the host and a reverse lookup of the IP address to obtain the hostname. If the reverse lookup fails the driver falls back to a cname lookup.false
or "none": Does no hostname canonicalization.When syncing the spec tests some other auth spec tests we hadn't synced yet were there, so I decided to leave them and skip the single failure.
This PR is branched off #3123 so needs to go in/be reviewed after that.
Is there new documentation needed for these changes?
None
What is the motivation for this change?
DRIVERS-1803 / NODE-2939
Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>