With window servers they are registering with dns for interface, but shortly afterwards, it adds another interface with ip as connect to instead of dns.
Our auto registration action is

our zabbix agent config
LogType=system
LogFile=C:\Program Files\Zabbix Agent\zabbix_agentd.log
AllowKey=system.run[*]
EnableRemoteCommands=1
LogRemoteCommands=1
Server=x.x.x.x
ListenPort=10050
ServerActive=x.x.x.x
HostnameItem=system.hostname
HostMetadata=WindowsServer
HostInterfaceItem=system.run[powershell.exe -command $c=@(); $c += (gpv HKLM:\SYSTEM\CurrentControlSet\services\Tcpip\Para meters HostName);$c+=(gpv HKLM:\SYSTEM\CurrentControlSet\services\Tcpip\Para meters Domain);$c -join '.']
Include=C:\Program Files\Zabbix Agent\zabbix_agentd.d\
How can we stop this from happening?
Thank you in Advance.
William
Our auto registration action is
our zabbix agent config
LogType=system
LogFile=C:\Program Files\Zabbix Agent\zabbix_agentd.log
AllowKey=system.run[*]
EnableRemoteCommands=1
LogRemoteCommands=1
Server=x.x.x.x
ListenPort=10050
ServerActive=x.x.x.x
HostnameItem=system.hostname
HostMetadata=WindowsServer
HostInterfaceItem=system.run[powershell.exe -command $c=@(); $c += (gpv HKLM:\SYSTEM\CurrentControlSet\services\Tcpip\Para meters HostName);$c+=(gpv HKLM:\SYSTEM\CurrentControlSet\services\Tcpip\Para meters Domain);$c -join '.']
Include=C:\Program Files\Zabbix Agent\zabbix_agentd.d\
How can we stop this from happening?
Thank you in Advance.
William