feat: force fully qualified domains for s3 requests TDE-1084 #940
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.
Motivation
Inside kubernetes dns resolution uses
ndots: 5
this means any dns requests that has less than 5 dots will go through all the search domains before looking up the actual domain. AWS s3 has 4 dots.We are seeing 10-20 DNS requests per s3 DNS request due to the number of search domains as well as IPV6 requests.
Modification
Any DNS requests to S3 are modified to have a trailing "." to force the DNS lookup to be fully qualified.
Checklist
If not applicable, provide explanation of why.