Ad Widget

Collapse

MSSQL Agent2-Get value from agent failed Cannot resolve address Domain name not found

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • philh99
    Junior Member
    • Sep 2025
    • 5

    #1

    MSSQL Agent2-Get value from agent failed Cannot resolve address Domain name not found

    My Zabbix server is up in AWS, as I need to monitor internal and external customer databases.

    I have an on-prem MSSQL (2019) running on a Windows 2022 server with Agent2 and the plugins running.
    Through the agent, I am successfully running the Windows by Zabbix Agent Active and I can see various graphs being populated and displaying data.

    My problem is when I add the MSSQL by Zabbix Agent 2, the server checks are still going through, but the passive connection shows the error in the title (Get value from agent failed: Cannot resolve address: Domain name not found)

    Click image for larger version

Name:	image.png
Views:	137
Size:	8.1 KB
ID:	507643
    I've blanked out the server name (ie MYSERVER:10050).

    I have the following Macro items set:

    {$MSSQL.URI} = sqlserver://MYSERVER:1433 - also tried localhost as server name and IP Address
    {$MSSQL.HOST} = MYSERVER
    {$MSSQL.PORT} = 1433
    {$MSSQL.USER} = myzabbixuser
    {$MSSQL.PASSWORD} = thepassword

    This appears to be a passive problem.

    I have these set in my zabbix_agent2.conf file:

    Server=WebAddressOfMyZabbixServer (ie monitor.mydomain.com)
    ServerActive=WebAddressOfMyZabbixServer
    Hostname=MYSERVER

    Anyone successfully got past this problem?

    Thanks in advance.

  • PSklyar
    Member
    • Sep 2025
    • 30

    #2

    Hey, hey
    I can suggest you to check first if AWS can access your DNS
    You can try to use command "dig" or "nslookup" to verify that
    As currently, I can see that problem is with DNS name and how host were added in Zabbix frontend
    To test forward DNS resolution of your MSSQL server, you can use following commands:
    nslookup MYSERVER
    To test reverse DNS of your MSSQL server's IP use:
    nslookup YOUR_MSSQL_SERVER_IP

    Comment

    • philh99
      Junior Member
      • Sep 2025
      • 5

      #3
      Hi, thanks for the reply.

      Yes, I agree that must be the problem, however, AWS is never going to be able to see into my network and resolve that IP/DNS itself.
      I thought that the purpose of the Agent2 was to provide that tunnel.
      It does work for the Windows Server by Active Agent2 is successfully connecting through on the same host and retrieves data.



      Comment

      Working...