Bug 712833 - in /etc/zabbix/zabbix_agent.conf server= should handle DNS
Summary: in /etc/zabbix/zabbix_agent.conf server= should handle DNS
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: zabbix
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-13 10:27 UTC by Trever Adams
Modified: 2011-06-14 07:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-13 10:48:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Trever Adams 2011-06-13 10:27:02 UTC
Description of problem:
I have a IPv4/IPv6 network. As such many domain names have both A and AAAA records. Reverse DNS works forward and backward for all of these things.

Zabbix will accept Server=FQDN. It some times works, some times doesn't. I do not know but it seems that it resolves to just one of the entries and then only accepts from that entry. Instead, it should create it's own comma sepparated list and accept connections from anything where forward <=> reverse DNS is true.

This seems to be suggested in the 1.8 documentation online, but it is NOT working in my case. 

Version-Release number of selected component (if applicable):
zabbix-1.8.5-1.fc15.x86_64


Additional info:
Server FQDN has one A and two AAAA records.

Interestingly enough, while other hosts work sporadically (whether the resolved Server= line matches the ip address used by zabbix to contact the agents or not), it NEVER works for the localhost.

Comment 1 Dan Horák 2011-06-13 10:48:32 UTC
There are no Fedora specific changes in the zabbix package so this issue should be definitely discussed/reported in upstream forums or bug tracker. Please open it there.

Comment 2 Trever Adams 2011-06-14 07:22:14 UTC
As you have requested: http://taipei.sapphiresunday.org/zabbix/discovery.php?sid=ee7cbd9ee6de57ce

This does include a patch which fully fixes the problem.


Note You need to log in before you can comment on or make changes to this bug.