mojave man page for curlopt_dns_cache_timeout

Query: curlopt_dns_cache_timeout

OS: mojave

Section: 3

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

CURLOPT_DNS_CACHE_TIMEOUT(3)				     curl_easy_setopt options				      CURLOPT_DNS_CACHE_TIMEOUT(3)

NAME
CURLOPT_DNS_CACHE_TIMEOUT - set life-time for DNS cache entries
SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_DNS_CACHE_TIMEOUT, long age);
DESCRIPTION
Pass a long, this sets the timeout in seconds. Name resolves will be kept in memory and used for this number of seconds. Set to zero to completely disable caching, or set to -1 to make the cached entries remain forever. By default, libcurl caches this info for 60 seconds. The name resolve functions of various libc implementations don't re-read name server information unless explicitly told so (for example, by calling res_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. Note that DNS entries have a "TTL" property but libcurl doesn't use that. This DNS cache timeout is entirely speculative that a name will resolve to the same address for a certain small amount of time into the future.
DEFAULT
60
PROTOCOLS
All
EXAMPLE
TODO
AVAILABILITY
Always
RETURN VALUE
Returns CURLE_OK
SEE ALSO
CURLOPT_DNS_USE_GLOBAL_CACHE(3), CURLOPT_DNS_SERVERS(3), libcurl 7.54.0 February 03, 2016 CURLOPT_DNS_CACHE_TIMEOUT(3)
Related Man Pages
curlopt_accepttimeout_ms(3) - mojave
curlopt_connecttimeout(3) - mojave
curlopt_connecttimeout_ms(3) - mojave
curlopt_ftp_skip_pasv_ip(3) - mojave
curlopt_resolve(3) - mojave
Similar Topics in the Unix Linux Community
about &quot;caching only name server&quot; !
Solaris 10 - DNS / Issues / Help
DNS needs to be refreshed periodically to work
DHCP &amp; DNS - Clients get IP but don't register in DNS
DNS flush is not working