Bump the default of CONFIG_NETDB_DNSCLIENT_MAXRESPONSE
It's better to have a default working for many cases. Usually DNS servers are not optimized for embedded clients. Users can fine tune for their environment anyway.
This commit is contained in:
parent
e783a59f9d
commit
76add63598
@ -103,11 +103,12 @@ config NETDB_DNSCLIENT_LIFESEC
|
||||
|
||||
config NETDB_DNSCLIENT_MAXRESPONSE
|
||||
int "Max response size"
|
||||
default 96
|
||||
default 256
|
||||
---help---
|
||||
This setting determines the maximum size of response message that
|
||||
can be received by the DNS resolver. The default is 96 but may
|
||||
need to be larger on enterprise networks (perhaps 176).
|
||||
can be received by the DNS resolver. The default used to be 96,
|
||||
which might be enough if you have a control on the DNS servers.
|
||||
It may need to be larger on enterprise networks.
|
||||
|
||||
config NETDB_DNSCLIENT_RECV_TIMEOUT
|
||||
int "DNS receive timeout"
|
||||
|
Loading…
Reference in New Issue
Block a user