-
Problem report
-
Resolution: Duplicate
-
Minor
-
None
-
4.0.45, 5.0.14, 6.0.17, 6.4.2, 7.0.0alpha1
-
None
-
OEL 7.7 (kernel 4.14) + Zabbix Proxy 5.0.14
CentOS 8 + Zabbix Server 5.0.14
2xCentOS + DNSMASQ (as DNS server)
-
S24-W16/17, S24-W18/19
Steps to reproduce:
- Install Zabbix Proxy 5.0.14 on OEL 7.7 (kernel 4.14)
- Install Zabbix Server 5.0.14 (in test CentOS 8 was used)
- Register Zabbix Proxy on the Zabbix Server
- Install 2x local DNS servers (in test CentOS 8 + Dnsmasq were used)
- Register Zabbix Proxy's DNS name on both DNS servers for resolving into local private IP
- Set the 2 DNS servers in the Zabbix Proxy's "reolv.conf" so that Zabbix Proxy would resolve DNS names via those 2 local DNS servers (including Proxy's own DNS name)
- In the Zabbix frontend create 7-10 hosts for Zabbix proxy with Agent interface configured with Zabbix Proxy's DNS name registered on the 2 local DNS Servers.
- Set those 7-10 Proxy host instances to be monitored via Zabbix Proxy itself
- Stop the "dnsmasq" service on the first local DNS server
- Observe the queue growing on the server
So in case the first DNS server becomes unavailable host checks by DNS name become slow and queue starts to grow.
- duplicates
-
ZBXNEXT-8620 Add async DNS resolver for HTTP, SNMP and Zabbix agent
- Closed