From: Daniel Stenberg Date: Thu, 10 Jul 2008 22:24:11 +0000 (+0000) Subject: (Added in the section for CURLOPT_DNS_CACHE_TIMEOUT, pointed out on the X-Git-Tag: cares-1_5_3~371 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6b7ccde1567f401018144e9fa9fcaa63616df338;p=curl (Added in the section for CURLOPT_DNS_CACHE_TIMEOUT, pointed out on the curl-library list on July 9th 2008 by Mathew Hounsell) NOTE: the name resolve functions of various libc implementations don't re-read name server information unless explicitly told so (by for example calling Ires_init(3). This may cause libcurl to keep using the older server even if DHCP has updated the server info, and this may look like a DNS cache issue to the casual libcurl-app user. --- diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 92056b589..f389f98b4 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -505,6 +505,12 @@ Pass a long, this sets the timeout in seconds. Name resolves will be kept in memory for this number of seconds. Set to zero (0) to completely disable caching, or set to -1 to make the cached entries remain forever. By default, libcurl caches this info for 60 seconds. + +NOTE: the name resolve functions of various libc implementations don't re-read +name server information unless explicitly told so (by for example calling +\fIres_init(3)\fP. This may cause libcurl to keep using the older server even +if DHCP has updated the server info, and this may look like a DNS cache issue +to the casual libcurl-app user. .IP CURLOPT_DNS_USE_GLOBAL_CACHE Pass a long. If the value is non-zero, it tells curl to use a global DNS cache that will survive between easy handle creations and deletions. This is not