1 Title: "Update DNS cache" action is now really cleaning up the cache
11 As written in the documentation
12 (https://mathias-kettner.com/cms_wato_hosts.html) Check_MK is keeping an
13 internal DNS cache for the hosts that have configured no static IP address in
18 With the host name method Check_MK uses cached data in order to minimise
19 repeated DNS requests during an Activate Changes – which is very important for
20 accelerating the activation procedure. Furthermore, the cache ensures that a
21 changed configuration can still be activated if the DNS stops working.
23 The catch is that Check_MK doesn't automatically notice the change to an
24 address in DNS. For this reason, in the host details there is the button which
25 deletes the entire DNS cache and forces a new resolution at the next Activate
26 changes. This file is found under ~/var/check_mk/ipaddresses.cache in your
27 instance, by the way. Deleting this file has the same effect as the button as
32 The problem was that previous versions did not really delete the entire cache,
33 but only updated it. We have now changed this to make the cache invalidation