[ZBX-17396] Non-existing DNS entries in Server= increase Zabbix Agent response time Created: 2020 Mar 03  Updated: 2024 Apr 10  Resolved: 2020 Mar 29

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Documentation (D)
Affects Version/s: 4.0.18, 4.4.6
Fix Version/s: 5.0 (plan)

Type: Documentation task Priority: Critical
Reporter: Edgar Akhmetshin Assignee: Marina Generalova
Resolution: Fixed Votes: 0
Labels: Windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
Duplicate
duplicates ZBXNEXT-1002 dns caching by zabbix daemons Open
Team: Team D
Sprint: Sprint 62 (Mar 2020)

 Description   

Steps to reproduce:

  1. Install Agent on Windows
  2. Try with correct DNS entries to get value from another machine:
    [root@c7zs1]# time zabbix_get -s 10.211.55.4 -k system.uname
    Windows VMZ 10.0.18363 Microsoft Windows 10 Pro x64
    
    real	0m0.052s
    user	0m0.003s
    sys	0m0.002s
    
  3. Try with incorrect DNS entries to get value from another machine (the more incorrect entries you have, the more time you need):
    Server=qwerty123,qwerty123,10.211.55.39 
    
    [root@c7zs1]# time zabbix_get -s 10.211.55.4 -k system.uname
    Windows VMZ 10.0.18363 Microsoft Windows 10 Pro x64
    
    real	0m2.312s
    user	0m0.003s
    sys	0m0.002s
    [root@c7zs1]# time zabbix_get -s 10.211.55.4 -k system.uname
    Windows VMZ 10.0.18363 Microsoft Windows 10 Pro x64
    
    real	0m4.640s
    user	0m0.001s
    sys	0m0.003s
    

On Linux it's not a problem, since ncsd daemon will cache negative answers, but on Windows you can see errors like:

Get value from agent failed: ZBX_TCP_READ() timed out

By default, Windows stores positive responses in the DNS cache for 86,400 seconds (i.e., 1 day) and stores negative responses for 300 seconds (5 minutes).

Expected:
Do not fail with timeout with negative DNS in the Server= option.



 Comments   
Comment by Alexander Vladishev [ 2020 Mar 15 ]

It should be documented as known issue.

Comment by Marina Generalova [ 2020 Mar 20 ]

Documentation updated:

Generated at Tue Apr 29 11:36:02 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.