I had setup several Web scenarios on the main zabbix server and all were reporting successful. I then assigned the host to a proxy because I want to know if the services are down from the remote site's perspective. This is when all of the monitors that use my internal domain are reported as unable to resolve DNS. There's no issue with other internet IP's
These are internet facing Hosts that I delegate to public DNS to resolve, since all internal hosts should use an internet IP to connect to these hosts. I've run into issues where the non-authoritative responce from an authoritative domain can cause lookup issues, and in these situations i just put in an unbound DNS in the middle so that all of the responces are returned without a-typical errors. I can ping the hosts used by these failing web scenarios from the webpart, connect via curl, and nslookup looks clean, when run from the zabbix proxy.
I don't think this split-horizon dns is the issue here, and none of the hosts at the remote site have issues connecting to these services, so it's just an issue in the zabbix proxy environment.
It may not just be an issue with web scenarios, because I have a simple check that is also failing, but it's not my priority and I didn't notice if it was working or not on the main server without pr
Zabbix server and proxy are 6.4, however the proxy is running in an alpine linux edge LXC container​
These are internet facing Hosts that I delegate to public DNS to resolve, since all internal hosts should use an internet IP to connect to these hosts. I've run into issues where the non-authoritative responce from an authoritative domain can cause lookup issues, and in these situations i just put in an unbound DNS in the middle so that all of the responces are returned without a-typical errors. I can ping the hosts used by these failing web scenarios from the webpart, connect via curl, and nslookup looks clean, when run from the zabbix proxy.
I don't think this split-horizon dns is the issue here, and none of the hosts at the remote site have issues connecting to these services, so it's just an issue in the zabbix proxy environment.
It may not just be an issue with web scenarios, because I have a simple check that is also failing, but it's not my priority and I didn't notice if it was working or not on the main server without pr
Zabbix server and proxy are 6.4, however the proxy is running in an alpine linux edge LXC container​