A method of providing static proximity load balancing via a multi-core intermediary device, the method comprising: (a) identifying, by an intermediary device providing global server load balancing (GSLB), a size of a location database that associates source IP addresses with location information such as a domain name, an IP address for a server hosting a site associated with the domain name, qualifiers associated with the hosting server's location - e.g., city, state, and/or country - and/or geographical coordinates of the hosting server, the intermediary device comprising a plurality of packet processing engines, each of the plurality of packet processing engines executing on a corresponding core of a plurality of cores of the intermediary device, the intermediary device establishing a source IP address range for each packet processing engine and transmitting to each packet processing engine the source IP address range that the packet processing engine will own; (b) storing, by the intermediary device, the location database to an external storage of the intermediary device responsive to determining the size of the location database is greater than a predetermined threshold; (c) receiving, by a first packet processing engine of the plurality of packet processing engines operating on a first core of the plurality of cores, a domain name service request having a source IP address; (d) determining, by the first packet processing engine, that proximity information for the source IP address is not stored in a first memory cache of the first packet processing engine; (e) identifying, by the first packet processing engine, a second packet processing engine of the plurality of packet processing engines operating on a second core of the plurality of cores as the owner of the source IP address of the domain name service request; (f) transmitting, by the first packet processing engine, a request to the second packet processing engine for proximity information for the source IP address; (g) transmitting, by the first packet processing engine, a request to the external storage for proximity information for the source IP address responsive to the second packet processing engine not having the proximity information; (h) receiving from the external storage, by the first packet processing engine, a response to the request, the response including proximity information for the source IP address; (i) storing, by the first packet processing engine, the proximity information for the source IP address to the first memory cache and communicating the proximity information for the source IP address to the second packet processing engine; and (j) selecting, by the first packet processing engine, a server for the DNS request based on the proximity information. (a) identifying, by an intermediary device providing global server load balancing (GSLB), a size of a location database that associates source IP addresses with location information such as a domain name, an IP address for a server hosting a site associated with the domain name, qualifiers associated with the hosting server's location - e.g., city, state, and/or country - and/or geographical coordinates of the hosting server, the intermediary device comprising a plurality of packet processing engines, each of the plurality of packet processing engines executing on a corresponding core of a plurality of cores of the intermediary device, the intermediary device establishing a source IP address range for each packet processing engine and transmitting to each packet processing engine the source IP address range that the packet processing engine will own; (b) storing, by the intermediary device, the location database to an external storage of the intermediary device responsive to determining the size of the location database is greater than a predetermined threshold; (c) receiving, by a first packet processing engine of the plurality of packet processing engines operating on a first core of the plurality of cores, a domain name service request having a source IP address; (d) determining, by the first packet processing engine, that proximity information for the source IP address is not stored in a first memory cache of the first packet processing engine; (e) identifying, by the first packet processing engine, a second packet processing engine of the plurality of packet processing engines operating on a second core of the plurality of cores as the owner of the source IP address of the domain name service request; (f) transmitting, by the first packet processing engine, a request to the second packet processing engine for proximity information for the source IP address; (g) transmitting, by the first packet processing engine, a request to the external storage for proximity information for the source IP address responsive to the second packet processing engine not having the proximity information; (h) receiving from the external storage, by the first packet processing engine, a response to the request, the response including proximity information for the source IP address; (i) storing, by the first packet processing engine, the proximity information for the source IP address to the first memory cache and communicating the proximity information for the source IP address to the second packet processing engine; and (j) selecting, by the first packet processing engine, a server for the DNS request based on the proximity information.