Citrix Systems, Inc.

Josh Thomas Gray

Steven Lyons

Thomas E Roth

Darren Gilroy

Alok Aggarwal

Described embodiments provide systems and methods for resolving Domain Name Service (DNS) requests. An authoritative DNS server may receive, from a recursive resolver, a DNS request to resolve a query on behalf of a client. The authoritative DNS server may determine whether the recursive resolver is classified as a non-client representative resolver or a client representative resolver. The authoritative DNS server may identify a redirect server based on the recursive resolver classified as the non-client representative resolver or the resolved server based on the recursive resolver classified as the client representative resolver. The authoritative DNS server may transmit, to the recursive resolver, a response to the DNS request including an address of one of the redirect server or the resolved server.

Intelligent redirector based on resolver transparency

Described embodiments provide systems and methods for resource appropriation in a multi-tenant environment using risk and value modeling. A resource server can provide a plurality of applications access to a plurality of resources in response to requests from clients based in part on risk scores and value scores. The resource server can generate and execute a risk model and a value model to determine a risk score and a value score for each of the applications. The resource server can use the risk and value scores to determine access to a particular resource for a requested application. The resource server can assign a first allocation of resource tokens to an application. The resource tokens can correspond to access privileges to plurality of resources. The resource server can dynamically modify the resource allocation for applications responsive to changes to a risk score or value score of a respective application.

Resource appropriation in a multi-tenant environment using risk and value modeling systems and methods

Described embodiments provide systems and methods for cross protocol association using internet addresses for metadata association. An association between IPv4 addresses and IPv6 addresses can determined and used to bridge metadata from collection context in a first protocol into usage for a second protocol. A server can monitor a plurality of handshake exchanges to generate the association between IPv4 addresses and IPv6 addresses for a device or group of devices. The handshake exchange can include an IPv4 address, an IPv6 address, or both an IPv4 address and an IPv6 address for a respective device. The handshake exchanges can include a unique identifier corresponding to the respective device. The server can use the association to generate a mapping linking a range of IPv4 addresses to a range of IPv6 addresses corresponding to the same device. The mapping can be used to associate metadata to devices within the same ranges.

Growing community of inventors

Washington County, OR, United States of America

Josh Thomas Gray