DNS can’t ID Controller hostname when installing Java Agent

[#1]

After Java Agent installation, there is an “unable to identify hostname” error and the Controller can’t connect to Windows

When installing Java Agent for Windows, there is an "unable to identify hostname"

Error when telnet is checked to Controller connection.

Diagnostics

To troubleshoot the issue, start by reviewing the following:

1. Can your DNS resolve the SaaS Controller host name? To confirm this, review the result of command: "nslookup <YOUR HOST NAME HERE>".
   

   ---<example>-----
   C:\Users\myaccount>nslookup mysaasaccount2020021717171312.saas.appdynamics.com
   
   Server: UnKnown
   
   Address: xxx.xx.xxx.xx
   
   Name: xxxxx.saas.appdynamics.com
   
   Addresses: xx.xx.xx.x
   Xx.xx.xx.x
   Aliases: mysaasaccount.saas.appdynamics.com.localdomain

   If the hostname successfully resolves, continue to step 2 of the diagnostics.

2. Is your <controller-host> set in <agent_home>/verx.x.x.x.x/conf/controller-info.xml?
   
   Be sure you have also set the property such as <application-name>, <tier-name> and <node-name>, to "Required:Yes" as described in the Java Agent Configuration Properties, Agent-Controller Communication Properties
   documentation.
   
   
3. Do you use a proxy? If so, be sure to set the information in your system property as described in the Java Agent Configuration section of the Java Agent Configuration Properties documentation.

Still experiencing a problem? Open a Support ticket where you’ll share the Agent log files—particularly the lines that show errors.