Abstract: Client and user activity in an application or a browser are monitored to determine whether potential actions will result in a server being contacted. A DNS request to resolve the server's host name is generated to ensure the server's IP address is cached and available.

Abstract: Client and user activity in an application or a browser are monitored to determine whether potential actions will result in a server being contacted. A DNS request to resolve the server's host name is generated to ensure the server's IP address is cached and available.

Abstract: When a mobile device interacts with a network service, synchronous DNS resolution can significantly impact user experience due to lossy or moderate-high latency conditions. Network services that rely on low-TTL DNS records for failover require a client to frequently resolve the service's host name. It is undesirable to block on these frequent resolutions. In an implementation, user activity on a mobile device is monitored to determine whether the user is engaged in an activity that would contact a server. If such an activity is in progress, then DNS requests to resolve the server's host name are periodically generated to make sure the server's IP address is cached. In an implementation, if a request to communicate with a server fails, the DNS cache expires the entry for that server so that a new DNS request can resolve the server's IP address in case the server's IP address has changed.

Abstract: When a mobile device interacts with a network service, synchronous DNS resolution can significantly impact user experience due to lossy or moderate-high latency conditions. Network services that rely on low-TTL DNS records for failover require a client to frequently resolve the service's host name. It is undesirable to block on these frequent resolutions. In an implementation, user activity on a mobile device is monitored to determine whether the user is engaged in an activity that would contact a server. If such an activity is in progress, then DNS requests to resolve the server's host name are periodically generated to make sure the server's IP address is cached. In an implementation, if a request to communicate with a server fails, the DNS cache expires the entry for that server so that a new DNS request can resolve the server's IP address in case the server's IP address has changed.

Abstract: On a mobile communications device, visiting a link from a messaging application or web browser may result in an undesired action, such as visiting a phishing site, downloading malware, causing unwanted charges, using too much battery, or the device being exploited. In an implementation, a mobile application intercepts a request including an identifier associated with an action to be performed by another application on the device and evaluates the identifier to determine when the request should be permitted, blocked, or conditionally permitted. The client may use local data or make a request to a server to evaluate the identifier. In an implementation, server communications are optimized to minimize latency by caching evaluation results on the device, proactively priming the device's DNS cache, optimizing when DNS lookups are performed, and adapting evaluation policy based on factors such as the source of the request, and the currently active network connection.