ok, but i have no idea why ISP is asking for BGP and matter of fact is,
i'll have to make BGP work somehow, so local caching server will fetch the
new subnets from ISP router automatically (and i don't know how).

Btw, our local ISP provided us with some testing ip prefixes to check nginx
based caching. i.e
geo {
default 0;
10.0.0.0/8
39.23.2.0/24 1;
112.50.192.0/18 1;
}

Now whenever we add the prefix 112.50.192.0/18 in geo {} , all the requests
coming from the 39.23.2.0/24 and 10.0.0.0/8 returns 504 gateway error and
videos failed to stream. To resolve this issue, we have to remove
112.50.192.0/18 1; from geo block.



On Wed, Jun 18, 2014 at 12:50 AM, itpp2012 <nginx-forum@nginx.us> wrote:

> You don't need to do anything with a dns that is only local to the clients
> served by the ISP.
>
> Suppose I am in Africa;
> Question to my ISP: I'd like to go to new-york
> ISP: new-york is located in south-Africa
>
> Suppose I am in the US;
> Question to my ISP: I'd like to go to new-york
> ISP: new-york is located in the US
>
> The DNS is just a pointer, where ever you have an edge server make the dns
> name point to it, when not point the dns to origin.
> Every ISP client gets the DNS servers from their ISP, its really simple.
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,249997,250957#msg-250957
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx