Understand URL.Destination.IP Behavior
The URL.Destination.IP property captures the IP address of the destination server for a requested URL. When the request is sent, the value is typically obtained through a DNS (Domain Name System) query. If DNS resolution fails, the property falls back to the placeholder IP address 255.255.255.255.
Cache Behavior
For example, when a user accesses google.com, the IP address of the google.com server is recorded in the URL.Destination.IP property. With Secure Web Gateway (SWG) caching enabled, the behavior of the URL.Destination.IP property varies depending on whether the request is served from the cache and whether Next Hop Proxy (NHP) is enabled.
- If NHP is not enabled and a URL request triggers a DNS lookup, SWG stores the resolved destination IP address along with the cached content. When subsequent requests for the same URL are served from the cache, SWG retrieves the destination IP from the stored entry and populates it in the
URL.Destination.IPproperty. This allows users to identify the destination server they previously connected to. - If NHP is enabled, SWG still performs a DNS lookup for the destination URL, even when serving content from the cache. After the lookup, SWG retrieves the resolved IP address and populates it in the
URL.Destination.IPproperty.
Limitation
If SWG caches the content while NHP is disabled, it stores the destination IP address with the cached data. Later, if NHP is enabled and a user accesses the same URL, SWG serves the request from the cache and skips the DNS lookup. It populates the URL.Destination.IP property using the previously stored IP address.
