Last updated
Last updated
Due to recent platform-wide naming, navigation, and URL changes in the product, you may notice some discrepancies between the product and the screenshots displayed in our technical documentation. The instructions and actual pages in the product are still valid and haven’t changed. Please bear with us as we update our screenshots to better match the in-product experience. See the full scope of changes on .
A reverse DNS lookup or resolution (rDNS) queries the Domain Name System (DNS) to determine the domain name associated with an IP address. This is the opposite of a standard DNS lookup, which determines the IP address associated with a domain name.
ThousandEyes Enterprise Agents perform rDNS lookups for addresses by default. The agent performs lookups for each hop in the path, until it encounters a non-RFC 1918 address, or one that is not in the configured rDNS ranges.
This article provides the steps to extend rDNS lookups by the agent for public IP addresses.
One or more ThousandEyes Enterprise Agents or clusters.
To configure the agent's reverse DNS behavior:
In the ThousandEyes web app:
For Enterprise Agents, navigate to Network & App Synthetics > Agent Settings > Enterprise Agents > Agents.
For clusters, navigate to Network & App Synthetics > Agent Settings > Enterprise Agents > Clusters.
Click the Enterprise Agent or cluster you wish to configure to open the Edit Configuration panel.
Open the Advanced Settings tab.
In the Reverse DNS section, add the public IP ranges that should be used for the rDNS lookups.
After adding the ranges, click Save Changes.
To configure multiple Enterprise Agents at once:
Navigate to Cloud and Enterprise Agents > Agent Settings > Enterprise Agents > Agents.
Select the checkbox beside each desired Enterprise Agent, or the checkbox beside Agent Name to select all.
From the bottom configuration options panel, open the Edit menu and select Edit Reverse DNS.
In the Reverse DNS side panel, configure the public IP ranges, and click Save Changes.
Once configured, the domain name for each hop will be displayed in the Path Visualization. Hover the cursor over the node to see that node's details:
