We're using video streaming website and want to cache mp4 files on local caching server to save the bandwidth. We have two servers, one in US and one is in our country's local ISP(Caching Server).

Request first goes to Main-server and it checks the client ip using nginx geo module in order to decide routing. Now we want to route any ip coming from our local ISP towards the caching server. Currently, we're using nginx geo module on main server located in US to check if the coming request is from the ip 1.2.3.4 and direct it to the local caching server.

Our ISP provided us with pools i.e 10.0.0.0/8 to route these ips on their local caching server.

The problem occurs now that we'll have to get the ip pools from our local ISP each time whenever they add the new clients to their network.

Is there a way to detect new ip pools automatically using some services maybe like BGP ? I've no idea about BGP but just heard from my friend.

If yes, how i am going to work with BGP ? Currently we're using nginx on both our servers.

Help will be highly appreciated.

How does nginx decide route, based on routing table in kernel or configuration in nginx?

>>How does nginx decide route, based on routing table in kernel or configuration in nginx?
Its nginx geo module, which supports CIDR notation to route that specific ip prefix towards the local caching server and rest will be server from the main server. I configured this module on Main Server because request first goes there, so nginx checks if the ip is 1.2.3.4 and it is added in geo {} so it'll route that ip towards the local caching server using proxy_pass directive of nginx.

http://nginx.org/en/docs/http/ngx_http_geo_module.html

The server stores objects in serialized form in the cache. When a cache client requests an object from the cache, the server sends it to the client over the network. The cache client then deserializes the object for use by the client application. To speed up the process of retrieving an object, enable local cache. For more information about enabling local cache, see Enable Windows Server AppFabric Local Cache or Enable Windows Server AppFabric Local Cache (XML).

The BGP is too big, normally it is used on backbone, not end user. You can use OSPF to get updated routing table. And then a code or script add these change into geo {}.

Can following script help me for fetching the prefixs from ISP router (via ASn of ISP) ?

https://code.google.com/p/bgpsimple/wiki/README

I'll add this script to our local caching server located in ISP and fetch the ISP routing table feed using this script ? And than will sync this script to my webserver.

I might be wrong. The script look like update entire routing table through BGP. Yes, you can use the script to update entire routing table in geo {}. If only doing different each time, it is better.