Bug 712833

Summary:	in /etc/zabbix/zabbix_agent.conf server= should handle DNS
Product:	[Fedora] Fedora	Reporter:	Trever Adams <trever>
Component:	zabbix	Assignee:	Dan Horák <dan>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	dan, jeff, nelsonab
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-13 10:48:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.