Client App DNS Report
The Cloudamize Client App DNS Report is a specialized report that focuses on network dependencies from a DNS perspective. While other reports may show IP-to-IP communication, this report specifically captures and maps DNS resolution requests from your source machines. This is a critical report for migrations, as it helps you identify which applications rely on specific hostnames and ensures you can correctly update DNS records in the cloud environment.
This report shows DNS activity originating from machines in your environment, essentially tracking what domain names client applications are querying, and how frequently.
Steps to navigate to the Client App DNS Report:
Log in to the console https://console.cloudamize.com/#/
Navigate to the Plan page of your completed assessment.
Click on the Reports Section as shown in the screenshot below under the Plan section.
Click on Client App DNS → Detailed for Client App DNS to download the report.
Column Name | Detailed Description |
|---|---|
Application Name | The name of the software application or service to which the DNS record belongs. This helps identify the purpose or business function the DNS entry supports (e.g., CRM system, internal API, analytics tool). |
DNS Name | The fully qualified domain name (FQDN) that maps to the application or asset. This is the human-readable address used to access the system over the network (e.g., |
IP Addresses | The numeric network addresses (IPv4 or IPv6) associated with the DNS name. These are used by devices to locate and connect to the resource on a network. |
Group Name | The classification or grouping to which the asset belongs, often based on department, function, security zone, or ownership. This helps in organizing and managing assets logically. |
Asset Name | The registered name of the asset in the organization’s asset inventory often represents a server, virtual machine, or network device associated with the application. |
Instance Name | A unique identifier for a specific instance of the asset or application. Useful in environments with multiple deployments of the same application (e.g., development, staging, production instances). |
Example Report: