mathias-kettner.de “could not be resolved”

Home » mathias-kettner.de “could not be resolved”

So we use check_mk pretty extensively for all of our servers for health monitoring. Today we added a brand new bare metal centos 7 minimal install on-sit test server to nagios.

We were getting this strange service when we added the box to be invetnoried:

Resolve_mathias-kettner.de
CRITICAL 06-29-2015 13:43:49 3d 5h 14m 51s 3/3 CRIT - mathias-kettner.de could not be resolved

I couldn’t figure out what this check does so I took a peak at the git repo, and saw that its doing a nslooup.  Well my box didn’t have nslookup installed, so a quick

sudo yum install bind-utils -y

seem to do the trick!

Leave a Comment

Your email address will not be published. Required fields are marked *