However, I'll have a question on Step-1 of the Cache-Hit scenario;
The LG U+ subscriber enters www.youtube.com into his browser to access a YouTube server. The subscriber device sends a DNS query to an LG U+ DNS server (the DNS server doesn't have to be an LG U+ DNS server) to obtain the IP address of the YouTube server.
This doesn't quite explain why Google requires an ISP to advertise its "resolver prefixes" to GGC (in addition to the user prefixes).
Can you advise on this?
Thanks,
Mohammed Salah2018-04-27 21:52:55
Hello Team,
thank you for this very usefull explain.
As we know everything is based on DNS query replay.
So, How can we force our subscriber to get thier video from our GGC. if MISS, our GGC will cache fill it from parent GGC.
this issue to prevent the very bad situation "Cache Fill is performed for a content requested more than a specified number of times"
Best Regards
Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.
Thanks for the great article.
However, I'll have a question on Step-1 of the Cache-Hit scenario;
This doesn't quite explain why Google requires an ISP to advertise its "resolver prefixes" to GGC (in addition to the user prefixes).
Can you advise on this?
Thanks,
Hello Team,
thank you for this very usefull explain.
As we know everything is based on DNS query replay.
So, How can we force our subscriber to get thier video from our GGC. if MISS, our GGC will cache fill it from parent GGC.
this issue to prevent the very bad situation "Cache Fill is performed for a content requested more than a specified number of times"
Best Regards