CMK version: Checkmk Raw Edition 2.4.0p14
OS version: Official Checkmk container with Debian GNU/Linux 13 (trixie) host
Error message: (No error message)
I set up container monitoring with Checkmk Raw Edition (“CRE”) a while ago and am getting the expected output from many containers across several hosts. This article was very helpful: Monitoring Docker
However, upon reviewing my network’s DNS logs, I see CRE constantly querying for the short and long hostnames of all of the defined containers. This is despite the fact they are all configured to have No IP and only use piggyback data, and the response always comes back NXDOMAIN.
When I disable a single container, I see the queries for it stop. When I disable all active & passive checks, all the queries stop.
If I set my DNS server to respond to a query for a container with 127.0.0.1, the queries for that host stop while all the other continue.
Why is DNS being queried for a host with no IP? Can this be disabled manually, or perhaps automatically after the response is NXDOMAIN a few thousand times?
Thanks!!
Combined screenshots attached:
- TOP: Pi-hole (dnsmasq) logs showing a couple of the container names being queried. 192.168.1.142 is CRE, and 192.168.1.1 is the DNS server.
- BOTTOM: The CRE configuration of the first queried container, freshrss-00002, showing no IP, API integrations, or agent configured.
