net.dns / net.dns.query caches name servers

[atan]

Hi,

Does anyone know if this is a known problem/behaviour/bug? I have tried searching on support.zabbix.com with no luck.

I am running Zabbix on Ubuntu, and have encountered this problem and made some tests.

/etc/resolv.conf
192.168.0.1
192.168.0.2

External nameservers to monitor (assume the following)
1.1.1.1
2.2.2.2
3.3.3.3

Before using "net.dns" to check status of the above 3 external nameservers, all resolution of hostname using other items (i.e. web.page.get) goes through the nameservers in /etc/resolv.conf and are successful.

After using "net.dns" to check the status of the external nameservers, resolution of hostnames goes through these external nameservers which causes a "cannot resolve host" error.

Now the external nameservers serve a specific purpose, so are configured to only resolve certain hostnames.

The only way to solve this problem, is to restart the Zabbix agent. I am assuming it releases some sort of caching of the DNS making it use those configured in /etc/resolv.conf again. However the problem starts again, once you used net.dns again.

I hope the community will be able to shed some light into this.

Thanks!

[BDiE8VNy]

If so, i would suggest to create a bug report.
What happens when using "net.dns" with one of the name servers configured in /etc/resolv.conf?

[atan]

in fact, the agent will use the configured name servers (/etc/resolv.conf) and those that were used in the net.dns. Hence causing some errors.

I tried using net.dns with one of the configured name servers as suggested, and there doesn't seem to be any negative impact.

Will create a bug, after I gather the necessary logs.

Thanks for the reply!