Abstract: A scalable domain name system with persistence and load balancing receives requests from client DNS servers or other DNS servers. Each DNS server is associated with a subset of the DNS groups in the network and the invention checks to see if the client DNS server is part of the DNS group that the DNS server is authoritative. If the DNS server is not authoritative for the client DNS server's group, then the request is forwarded to the proper DNS server. Otherwise, the invention checks a persistence table to see if a persistent response is required for the request. If a persistent response is required, the appropriate IP address entry in the table is returned to the requestor. If a persistent response is not required, the invention determines the load, availability, and latency of the content servers from information stored in a latency table to determine the proper content server's address to return to the requestor. The DNS server sends any responses to forwarded requests to the client DNS server.

Abstract: A content delivery and global traffic management network system provides a plurality of caching servers connected to a network. The caching servers host customer content that can be cached and stored, and respond to requests for Web content from clients. If the requested content does not exist in memory or on disk, it generates a request to an origin site to obtain the content. A DNS Server (SPD) load balances network requests among customer Web servers and directs client requests for hosted customer content to the appropriate caching server which is selected by choosing the caching server that is closest to the user, is available, and is the least loaded. SPD also supports persistence and returns the same IP addresses, for a given client. The entire Internet address space is broken up into multiple zones. Each zone is assigned to a group of SPD servers.

Abstract: A method for a computer network includes sending a first request from a web client for resolving a first web address of a web page to a client DNS server, sending the first request from the client DNS server to a POP DNS server that determines a customer web server from the plurality of customer web servers, sending the web page that includes static content represented by an embedded URL from the customer web server, sending a second request from the web client for resolving the URL to the client DNS server sending the second request from the client DNS server to the POP DNS server that determines a web cache from the plurality of web caches, sending the static content from the web cache to the web client, and outputting the static content with the web client.

Abstract: A secure streaming content delivery system provides a plurality of content servers connected to a network that host customer content that can be cached and/or stored, e.g., images, video, text, and/or software. The content servers respond to requests for customer content from users. The invention load balances user requests for cached customer content to the appropriate content server. A user makes a request to a customer's server/authorization server for delivery of the customer's content. The authorization server checks if the user is authorized to view the requested content. If the user is authorized, then the authorization server generates a hash value using the authorization server's secret key, the current time, a time-to-live value, and any other information that the customer has configured, and embeds it into the URL which is passed to the user. A content server receives a URL request from the user for customer content cached on the content server.

Abstract: A method for determining metrics of a content delivery and global traffic management network provides service metric probes that determine the service availability and metric measurements of types of services provided by a content delivery machine. Latency probes are also provided for determining the latency of various servers within a network. Service metric probes consult a configuration file containing each DNS name in its area and the set of services. Each server in the network has a metric test associated with each service supported by the server which the service metric probes periodically performs metric tests on and records the metric test results which are periodically sent to all of the DNS servers in the network. DNS servers use the test result updates to determine the best server to return for a given DNS name. The latency probe calculates the latency from its location to a client's location using the round trip time for sending a packet to the client to obtain the latency value for that client.

Abstract: A user interface device and system for providing a shared GTM and CDN (collectively Universal Distribution Network) for a service fee, where the customer or user does not need to purchase significant hardware and/or software features. The present interface device and system allows a customer to scale up its Web site, without a need for expensive and difficult to use hardware and/or software. In a preferred embodiment, the customer merely pays for a service fee, which can be fixed, variable, lump some, or based upon a subscription model using the present system. The present device and system are preferably implemented on a system including a novel combination of global traffic management and content distribution.

Abstract: A network of point of presence servers sharing a hostname includes a first network probe server configured to determine traffic loads of a plurality of customer web servers, and configured to determine latency of web cache servers in the network of point of presence servers, each of the customer web servers storing a web page, a first domain name server coupled to the first network probe server, configured to receive a request from a user for the web page at a first web address, the first web address including the hostname, configured to determine a customer web server from the plurality of customer web servers that is appropriate for the request, the customer web server having a traffic load lower than traffic loads of remaining customer web servers from the plurality of customer web servers, configured to determine an IP address of the customer web server, configured to return the IP address of the customer web server, configured to receive a request from the user for static content on the web page at a sec

Abstract: A network of point of presence servers sharing a hostname includes a first network probe server configured to determine traffic loads of a plurality of customer web servers, and configured to determine latency of web cache servers in the network of point of presence servers, each of the customer web servers storing a web page, a first domain name server coupled to the first network probe server, configured to receive a request from a user for the web page at a first web address, the first web address including the hostname, configured to determine a customer web server from the plurality of customer web servers that is appropriate for the request, the customer web server having a traffic load lower than traffic loads of remaining customer web servers from the plurality of customer web servers, configured to determine an IP address of the customer web server, configured to return the IP address of the customer web server, configured to receive a request from the user for static content on the web page at a sec

Abstract: A content delivery and global traffic management network system provides a plurality of caching servers connected to a network. The caching servers host customer content that can be cached and stored, and respond to requests for Web content from clients. If the requested content does not exist in memory or on disk, it generates a request to an origin site to obtain the content. A DNS Server (SPD) load balances network requests among customer Web servers and directs client requests for hosted customer content to the appropriate caching server which is selected by choosing the caching server that is closest to the user, is available, and is the least loaded. SPD also supports persistence and returns the same IP addresses, for a given client. The entire Internet address space is broken up into multiple zones. Each zone is assigned to a group of SPD servers.

Abstract: A decrypting load balancing array system uses a Pentaflow approach to network traffic management that extends across an array of Decrypting Load Balancing Array (DLBA) servers sitting in front of back end Web servers. One of the DLBA servers acts as a scheduler for the array through which all incoming requests are routed. The scheduler routes and load balances the traffic to the other DLBA servers (including itself) in the array. Each DLBA server routes and load balances the incoming request packets to the appropriate back end Web servers. Responses to the requests from the back end Web servers are sent back to the DLBA server which forwards the response directly to the requesting client. SSL packets are decrypted in the DLBA server before being routed to a back end Web server, allowing the DLBA server to schedule SSL sessions to back end Web servers based on a cookie or session ID. Response packets are encrypted by the DLBA server before being forwarded to the client.