For a period of time there were two hosts configured in my setup by the discovery rule. This all worked fine.

These two hosts have now been taken out of production (and deleted from Zabbix), but the discovery rule keeps adding them again. The IP isn't reachable, snmp queries fail, yet it keeps adding the hosts and there is absolutely nothing there.

I deleted the A-record and PTR record to see if that had anything to do with it, but that didn't change the situation (except that the Zabbix hostname is now the ip address). Please see attached screenshots for configuration information.

attilla@zabbix:~$ ping 91.200.18.168
PING 91.200.18.168 (91.200.18.168) 56(84) bytes of data.
^C
— 91.200.18.168 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

attilla@zabbix:~$ ping 91.200.18.138
PING 91.200.18.138 (91.200.18.138) 56(84) bytes of data.
^C
— 91.200.18.138 ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

attilla@zabbix:~$ dig a 91.200.18.138

; <<>> DiG 9.7.3 <<>> a 91.200.18.138
;; global options: +cmd
;; Got answer:
;; >>HEADER<< opcode: QUERY, status: NOERROR, id: 63514
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;91.200.18.138. IN A

;; ANSWER SECTION:
91.200.18.138. 0 IN A 91.200.18.138

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jan 26 11:06:01 2012
;; MSG SIZE rcvd: 47

attilla@zabbix:~$ snmpget -v 2c -c xxx 91.200.18.138 1.3.6.1

Timeout: No Response from 91.200.18.138.