[ZBX-20326] Zabbix creates new dns interface in host with empty value Created: 2021 Dec 07  Updated: 2021 Dec 14  Resolved: 2021 Dec 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Proxy (P), Server (S)
Affects Version/s: 5.0.18
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Ramil Zakirov Assignee: Unassigned
Resolution: Duplicate Votes: 3
Labels: autoregistration, proxy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File empty_dns_interface.PNG     File zabbix_agentd_win.conf    
Issue Links:
Duplicate
is duplicated by ZBX-17060 Auto Registration changes from IP to ... Closed

 Description   

When auto-registration of the active zabbix agent is enabled and the proxy server cannot resolve the host by its ip address (there is no ptr record in the dns server), then as a result we get a host that starts being monitored using an empty dns interface. And naturally we get a server that is not monitored.
Moreover, this host in the zabix was already monitored and everything was fine, but for some reason auto-registration worked for it and updated the interface.

And that added interface, with empty dns, can't be removed: remove button is not active (see screenshot)

 Comments   
Comment by VAA-KIT [ 2021 Dec 08 ]

Seems to happen to random hosts at random times - at least a few hosts in a week.

Seeing this on version 5.4

Comment by Victor Breda Credidio [ 2021 Dec 09 ]

Hi Ramil.

Regarding the fact about being unable to remove the interface, it is so because this interface is in use by some item.

From the docs, about interface: (https://www.zabbix.com/documentation/current/en/manual/config/hosts/host)
Note: Interfaces that are used in any items cannot be removed and link Remove is grayed out for them.

I'm going to need some informations to help you.

What is the proxy and agent's version? Both 5.0.18?
Is the host's agent configuration file configured with HostInterface or HostInterfaceItem parameters? Can you please send this file?
Is this happening with other hosts, or just with this one?

Best regards.

Comment by Ramil Zakirov [ 2021 Dec 10 ]

Hi

Thanks for an answer

  1. We have tried with several proxy versions - 5.0.18, 5.0.16, 5.0.11 - all the same thing. We have several versions of agents on this problem servers - 3.0*, 5.0.18 and others - so I don't think that agent version matter much
  2. No, HostInterface or HostInterfaceItem is not configured. And this is odd that autoreg try to add dns interface, because it should use IP. Example agent conf file in the attachment.
  3. This is happenings for dozens of servers for us. All of them have IPs that can't be resolved to their dns name - nslookup HOSTIP - doesn't give us dns name. And, although I don't think that does matter, all servers are windows servers (2008 R2, 2012, 2016, virtuals and physicals, with serveral network interfaces or with one)
  4. zabbix_agentd_win.conf
Comment by Victor Breda Credidio [ 2021 Dec 10 ]

Ramil,

Thank you for reporting the issue. I found a similar case registered under ZBX-17060, so we will close this ticket. This issue's fix is already under development. Feel free to follow it.

 

Best regards.

Generated at Wed May 14 08:40:12 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.