feature: add support to config dns client cache size #1308
Merged
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.
for each client key type (tcplocal, tcpremote, udplocal, udpremote), the cache client size is set 5. we can not configure the dns cache size dynamically. If the size is too small, the dns client will create new connections and discard the old ones which are still waiting for dns responses. And it leads to timeout and slow down the dns service.
So in the PR, it add a new configurable parameter for dns local
client_cache_size
, the default value is 5.In my own openwrt device, it works much better.