| 12345678910111213141516171819 | [[networkaddress-cache-ttl]]=== DNS cache settingsElasticsearch runs with a security manager in place. With a security manager inplace, the JVM defaults to caching positive hostname resolutions indefinitelyand defaults to caching negative hostname resolutions for tenseconds. Elasticsearch overrides this behavior with default values to cachepositive lookups for sixty seconds, and to cache negative lookups for tenseconds. These values should be suitable for most environments, includingenvironments where DNS resolutions vary with time. If not, you can edit thevalues `es.networkaddress.cache.ttl` and `es.networkaddress.cache.negative.ttl`in the <<jvm-options,JVM options>>. Note that the valueshttp://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.ttl=<timeout>`]andhttp://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.negative.ttl=<timeout>`]in thehttp://docs.oracle.com/javase/8/docs/technotes/guides/security/PolicyFiles.html[Javasecurity policy] are ignored by Elasticsearch unless you remove the settings for`es.networkaddress.cache.ttl` and `es.networkaddress.cache.negative.ttl`.
 |