nuttx-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xiaoxi...@apache.org
Subject [incubator-nuttx] 03/03: Bump the default of CONFIG_NETDB_DNSCLIENT_MAXRESPONSE
Date Fri, 15 May 2020 06:24:00 GMT
This is an automated email from the ASF dual-hosted git repository.

xiaoxiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git

commit 76add63598c6bd6e4b2fb55f5adb1d6fb9249947
Author: YAMAMOTO Takashi <yamamoto@midokura.com>
AuthorDate: Fri May 15 14:11:54 2020 +0900

    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.
---
 libs/libc/netdb/Kconfig | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/libs/libc/netdb/Kconfig b/libs/libc/netdb/Kconfig
index 507f665..254284d 100644
--- a/libs/libc/netdb/Kconfig
+++ b/libs/libc/netdb/Kconfig
@@ -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"


Mime
View raw message