# Metricbeat caching old IPs after DNS change
**URL:** https://discuss.elastic.co/t/metricbeat-caching-old-ips-after-dns-change/178278
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 24, 2019, 2:50pm UTC](https://discuss.elastic.co/t/metricbeat-caching-old-ips-after-dns-change/178278 "2019-04-24T14:50:02Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mcguacon](https://discuss.elastic.co/u/mcguacon)
#### Post date: [April 24, 2019, 2:50pm UTC](https://discuss.elastic.co/t/metricbeat-caching-old-ips-after-dns-change/178278/1 "2019-04-24T14:50:02Z")
We are using Metricbeat to collect info on our RabbitMQ cluster. With a DNS change we cutover our cluster, but the monitoring itself kept reporting on the cluster with the old IP address. A restart of the monitoring updated everything to correct addresses, we are just wondering if this is a known issue, or if there is an option for updating / turning-off this IP address caching?
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [April 25, 2019, 10:02am UTC](https://discuss.elastic.co/t/metricbeat-caching-old-ips-after-dns-change/178278/2 "2019-04-25T10:02:13Z")
Beats don't cache DNS results. The caching normally happens somewhere else. On Windows/macOS it is the OS itself that caches lookups. On Linux it depends on your `/etc/resolv.conf`, `/etc/hosts`, and `/etc/nsswitch.conf`.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 23, 2019, 10:16am UTC](https://discuss.elastic.co/t/metricbeat-caching-old-ips-after-dns-change/178278/3 "2019-05-23T10:16:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.