If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
I don't have direct answer to you, but I know Zabbix implementations where a caching DNS resolver is running and used on the Zabbix server (only serving locally) just to decrease the number of DNS resolution requests that are sent out to the normal upstream resolvers.
zabbix 6.2 in a container. all nodes are added by IP, there are no discovery rules.
I don't understand why it goes to DNS and asks for PTR.
I don't need to look up DNS by IP.
How can I get him to stop doing it?
It is very strange that there is no answer to this question at all, even in the communities....
zabbix 6.2 in a container. all nodes are added by IP, there are no discovery rules.
I don't understand why it goes to DNS and asks for PTR.
I don't need to look up DNS by IP.
How can I get him to stop doing it?
It is very strange that there is no answer to this question at all, even in the communities....
Oh there are existing discussions and support ticket(s) around this, AFAIK they all conclude that it is not Zabbix that does the lookups but it's the underlaying operating system. So you would need to find out a way to reconfigure your container if you want to change its behaviour. (You know how some say containers are easy way to deploy anything? They just skip the details...)
Markku
Comment