> Source: [sk183860](https://support.checkpoint.com/results/sk/sk183860)

# sk183860 - Incorrect DNS name displayed in logs after Smart-1 Cloud migration

| Property | Value |
|----------|-------|
| Solution ID | sk183860 |
| Date Created | 2025-11-15 |
| Last Modified | 2025-11-17 |
| Technical Level | Advanced |
| Products | Smart-1 Cloud |
| Versions | Cloud |
| OS | Gaia |

## Symptoms

- After migrating a cluster to Smart-1 Cloud, some hosts in the logs display incorrect Domain Name System (DNS) names, such as `ip-xx-xx-xx-xx.region.compute.internal` instead of the expected hostnames.

## Cause

The log indexer on the Smart-1 Cloud management server uses a DNS back-resolving feature. This feature attempts to resolve IP addresses to hostnames using reverse DNS lookups. In cloud environments such as AWS or Microsoft Azure, reverse DNS lookups often return internal cloud hostnames (for example, `ip-10-xx-xx-xx.egion.compute.internal`) instead of the organization's intended DNS names. The behavior is controlled by the `dns_backresolving` parameter in the log indexer configuration.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content