zabbix-2.0.5-gethostbyip.patch
[ZBXNEXT-2710] Reverse DNS validation in network discovery Created: 2015 Feb 13 Updated: 2015 Mar 24 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Proxy (P), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Pavel Gashev | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | dns, networkdiscovery, patch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
zabbix-2.0.5-gethostbyip.patch
|
| Description |
|
It would be good to improve reverse DNS resolving by validating responses in direct DNS. So if 192.168.1.1 points to host.example.com, it can be used as hostname while discrovery only if host.example.com points back to 192.168.1.1. The patch is attached. It works for any versions from 2.0.5 to 2.4.3. |
| Comments |
| Comment by richlv [ 2015 Mar 24 ] |
|
it would be important to offer this as a configurable option on the discovery rule level to keep the previous behaviour - will involve the frontent a bit, too |