[ZBX-8091] Order net.dns.record respond Created: 2014 Apr 15 Updated: 2019 Mar 25 Resolved: 2019 Mar 17 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G) |
Affects Version/s: | None |
Fix Version/s: | 4.0.6rc1, 4.2.0rc1, 4.2 (plan) |
Type: | Problem report | Priority: | Minor |
Reporter: | halt | Assignee: | Andrejs Kozlovs |
Resolution: | Fixed | Votes: | 2 |
Labels: | dns, order | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Team: | Team A |
Sprint: | Sprint 49 (Feb 2019), Sprint 50 (Mar 2019) |
Story Points: | 0.125 |
Description |
To be able to compare, the responds, check for changes etc, the respond addresses should be ordered sample: zabbix_get -k net.dns.record[8.8.8.8,google.com,A,2,1] -s random.host |
Comments |
Comment by Alex Bond [ 2017 Jul 18 ] |
Dear Zabbix team, 3 years have passed, and this issue is still exists. Without sorting of results this check is absolutely useless. |
Comment by PNRtM5 [ 2017 Jul 18 ] |
It's impossible to use dns check feature for dns names with multiple records due to record sort issue. Just an example - for NS records check or for A-records with multiple IP addresses. |
Comment by halt [ 2017 Sep 04 ] |
The patch should be tiny, any reason why this is still pending ? |
Comment by PNRtM5 [ 2017 Sep 04 ] |
@halt Zabbix issue tracker contains more than 150 blocking and critical bugs, so this minor issue will never be fixed. |
Comment by Andrejs Kozlovs [ 2019 Mar 06 ] |
Fixed in:
|