fix.diff
|
Duplicate |
|||
| is duplicated by |
|
DNS monitoring improvements: add net.... | Closed |
Team C
[ZBXNEXT-3826] net.dns.record PTR too strict Created: 2017 Apr 27 Updated: 2024 Apr 11 Resolved: 2023 Nov 19 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Agent (G) |
| Affects Version/s: | 3.2.5 |
| Fix Version/s: | 7.0.0alpha8, 7.0 (plan) |
| Type: | Change Request | Priority: | Minor |
| Reporter: | Zak Peirce | Assignee: | Artjoms Rimdjonoks |
| Resolution: | Fixed | Votes: | 6 |
| Labels: | dns | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
fix.diff
|
||||||||
| Issue Links: |
|
||||||||
| Epic Link: | Zabbix 7.0 | ||||||||
| Team: | Team C |
||||||||
| Sprint: | Sprint 106 (Nov 2023) | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
I have a monitoring solution where I would like to verify that HOST.IP and HOST.DNS map correctly. I assumed that using the following check would work
"net.dns.record[8.8.8.8,1.2.3.4,PTR]"
The end result is an unclear zabbix message ZBX_NOTSUPPORTED: Cannot perform DNS query. I realize that PTR is a special record and I would need to query like this
"net.dns.record[8.8.8.8,4.3.2.1.in-addr.arpa,PTR]"
Could there be an option to put in an option for "reverse" so that dummies like me can use the HOST.IP macro to do a reverse lookup? something like this
"net.dns.record[8.8.8.8,1.2.3.4,reverse]"
|
| Comments |
| Comment by Vitaly Zhuravlev [ 2019 May 14 ] |
|
This is really good and useful case. All well known DNS tools such as dig, nslookup, host and so on do PTR transpose from '1.2.3.4' to '4.3.2.1.in-addr.arpa' automatically. But since Zabbix can't do it, it is impossible to check that Zabbix host IP {HOST.IP} has proper PTR record. |
| Comment by Artjoms Rimdjonoks [ 2023 Nov 15 ] |
|
Available in versions:
|
| Comment by Arturs Dancis [ 2023 Nov 16 ] |
|
Documentation (7.0) updated:
|