Similar to mapping a hostname to an IP address, the agents provide the capability to map a hostname to another hostname. When this feature is configured, the browser agent replaces the origin host with the new host destination, and it tries to resolve that new host to an IP address.
When more than one destination host is provided, the agent will work down the list of hosts until it can successfully resolve a destination host to an IP address. As soon as it has an IP address, it considers the mapping successful. If the agent cannot connect to the IP address, a connection failure is reported. In the case of a connection failure, it does not attempt the next host in the destination list. If none of the destination hosts successfully resolve to an IP address, a DNS failure is reported.
If a hostname-to-hostname mapping is added to a script that already has a hostname to IP Address mapping for the same origin hostname, the agents will only attempt the hostname to IP Address mapping. The hostname-to-hostname mapping is ignored.
The browser agents do not support chaining hostname-to-hostname mappings (e.g., map
123.com, then map
xyz.com, with the expectation that
abc.com will be mapped to