Autonomous DEM
Enable Reverse DNS Lookup for Path Tracing
Table of Contents
Enable Reverse DNS Lookup for Path Tracing
Enable reverse DNS Lookup for path tracing to restrict DNS lookups on public only and
private IP addresses discovered between source and target during path tracking.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
You can control DNS lookups on IP addresses discovered between source and target
endpoints during DNS path tracing. By default, ADEM performs a reverse DNS lookup to
identify the hostname of every IP address it encounters. However, DNS lookups on
private IP addresses (RFC1918) fail to resolve which adds to DNS
traffic. The reverse DNS lookups are performed on the below RFC1918 private address
ranges:
- 10.0.0.0- 10.255.255.255 (10/8 prefix)
- 172.16.0.0- 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0- 192.168.255.255 (192.168/16 prefix)
You can configure ADEM to perform reverse DNS lookups only for public IP addresses,
ignoring all private ranges. If not explicitly configured, ADEM performs DNS lookup
on both public and private IP addresses.
- Select .(Optional) Select Enable reverse DNS Lookup for path tracing to restrict DNS lookups on public IP addresses only or both for public and private addresses discovered on the network path.Select one of the following options:
- (Default) All IP hops- The agent attempts a reverse DNS lookup for all IP addresses, both public and private.
- Public IPs hops only- The agent performs reverse DNS lookups only for public IP addresses and ignores all private IP ranges.
![]()
This setting automatically applies to all application tests created for mobile users and remote networks.
