# Cross cluster search caches dns indefinitely

**URL:** <https://discuss.elastic.co/t/cross-cluster-search-caches-dns-indefinitely/121767>\
**Category:** Elasticsearch\
**Created:** [February 28, 2018, 2:24am UTC](https://discuss.elastic.co/t/cross-cluster-search-caches-dns-indefinitely/121767 "2018-02-28T02:24:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dylankpowers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dylankpowers/32/27589_2.png) [@dylankpowers](https://discuss.elastic.co/u/dylankpowers)\
**Post date:** [February 28, 2018, 2:24am UTC](https://discuss.elastic.co/t/cross-cluster-search-caches-dns-indefinitely/121767/1 "2018-02-28T02:24:19Z")

</div>

I want to be sure I'm not going crazy here, but it appears that cross cluster search will cache address values indefinitely? The only places in code I'm seeing the addresses resolved are upon initialization and when the seeds are updated.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 28, 2018, 2:24am UTC](https://discuss.elastic.co/t/cross-cluster-search-caches-dns-indefinitely/121767/2 "2018-03-28T02:24:32Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.