Icinga For Windows - zones.conf

Icinga 2
1

Hi Guys,

When running the new Agent config via IC2 for Windows PowerShell, I always land with an actual IP address in zones.conf file. So for example:

Object Zone "satellite" {
     host = "IP_ADDRESS"
}

Is that expected behaviour to translate DNS into IP? I always correct it manually (my hosts are always CNAME) so wonder if there is maybe some switch I missed to change this behaviour?

Thanks
D

2

I think so as DNS cold be down and then you could loose monitoring data.
Also the noise, that the monitoring generates, in the DNS logs could get quite loud.

3

I usually recommend to use IP-Addresses for your monitoring configuration instead of Domain Names, due to the dependency on your DNS infrastructure.

4

Hey

Thanks all for the answers! Marking as resolved.

Understanding dependency on DNS however, does not consider it as risk (AWS managed service) and using DNS names in zones.conf allows me painfully for example present to customer DR Process (AMI restore to different AZ).

All makes sense and I guess depends on environment and requirements.

Thanks
D

1 Like
5

True, it depends on the environment and maybe there should be command line switch if it’s not yet existing.