For hosts that are monitored via zabbix_proxy 1.6 I'm having a resolution problem for all hosts that are connected to by name instead of IP. I have the name set correctly and "Connect to" set to "DNS name" which works great for any host monitored directly on the local LAN, but when monitoring via proxy the remote zabbix_proxy.log shows that the proxy is unable to resolve the host name and so failing to connect.
I've verified that the DHCP server is registering the host names in DNS and that the system zabbix_proxy is running on is using the correct DNS server and resolving the names fine. If I dig the name it resolves properly. As far as I can see, every other app on the proxy box can resolve the names just fine, only zabbix_proxy fails to resolve them.
Update: I found a solution/workaround for my particular environment and wanted to make it known here in case it helps somebody else:
Although the server that zabbix_proxy runs on has no problem resolving local registered DHCP hosts via DNS by name, zabbix_proxy fails. For example, if I ping or dig the name from a shell it resolves. If I configure the host in zabbix via the proxy using the same name, zabbix_proxy.log shows name resolution failures.
I'm not using a local domain or search domain in resolv.conf, and so am resolving by hostname only. By adding a period to the end of the hostname to force it to be absolute, zabbix_proxy successfully resolves the name and connects fine.
I've tested this on multiple instances of zabbix_proxy in different environments and found that when using hostname-only DNS lookups adding a period always works regardless of whether it works without it, so I'm making it my standard practice for now for my agents on DHCP-assigned desktop PCs.
I've verified that the DHCP server is registering the host names in DNS and that the system zabbix_proxy is running on is using the correct DNS server and resolving the names fine. If I dig the name it resolves properly. As far as I can see, every other app on the proxy box can resolve the names just fine, only zabbix_proxy fails to resolve them.
Update: I found a solution/workaround for my particular environment and wanted to make it known here in case it helps somebody else:
Although the server that zabbix_proxy runs on has no problem resolving local registered DHCP hosts via DNS by name, zabbix_proxy fails. For example, if I ping or dig the name from a shell it resolves. If I configure the host in zabbix via the proxy using the same name, zabbix_proxy.log shows name resolution failures.
I'm not using a local domain or search domain in resolv.conf, and so am resolving by hostname only. By adding a period to the end of the hostname to force it to be absolute, zabbix_proxy successfully resolves the name and connects fine.
I've tested this on multiple instances of zabbix_proxy in different environments and found that when using hostname-only DNS lookups adding a period always works regardless of whether it works without it, so I'm making it my standard practice for now for my agents on DHCP-assigned desktop PCs.