[ZBX-2244] Change in net.tcp.dns causes checks to fail (agent 1.6.6->1.8.x) Created: 2010 Mar 30  Updated: 2017 May 30  Resolved: 2014 Sep 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 1.8, 1.8.1, 1.8.2
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Hunter Modes Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: agent
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos 5.4 i386


 Description   

The behavior of the net.tcp.dns agent check has changed between 1.6.6 and 1.8.x, causing items that function properly with a 1.6.6 agent to fail when the agent is upgraded to 1.8.x (tested with 1.8.0 and 1.8.2)

The 1.6.6 agent requests record type ANY, whereas 1.8.x requests SOA.

Key: net.tcp.dns[127.0.0.1,www.domain.com]

Behavior with 1.6.6 agent:

Observed query:
0.000000 127.0.0.1 -> 127.0.0.1 DNS Standard query ANY www.domain.com
0.000269 127.0.0.1 -> 127.0.0.1 DNS Standard query response A 10.1.1.1

Logged action:
25307:20100330:133300 Requested [net.tcp.dns[127.0.0.1, www.domain.com]]
25307:20100330:133300 Sending back [1]

Behavior with 1.8.x agent (1.8.0 and 1.8.2)

Observed query:
3.419397 127.0.0.1 -> 127.0.0.1 DNS Standard query SOA www.domain.com
3.419492 127.0.0.1 -> 127.0.0.1 DNS Standard query response

Logged action:
25380:20100330:133500.579 Requested [net.tcp.dns[127.0.0.1,www.domain.com]]
25380:20100330:133500.580 Sending back [0]

 Comments   
Comment by Alexander Vladishev [ 2014 Sep 23 ]

From version 1.8.0 zabbix will request SOA record by default. But you can change the type of record by using third parameter of the net.dns* checks.

I close the issue.

Generated at Fri May 02 06:49:20 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.