It’s great to see Amazon announcement two days back about launch of their region in Mumbai. In past I was quite happy to see their Cloudfront CDN PoPs in Mumbai & Chennai (blog post here). Now it’s just great to see a full AWS region out of Mumbai. :) Though it’s going to eat most of important customers from the smaller players still it’s good for industry as industry is too big and we need more & more of such large Cloud players in India to bring more and more content hosting in India.
Today I spotted some routes from Amazon AWS Cloud services - AS16509 in Indian tables. AS16509 was originating prefixes while sitting in downstream of Tata-VSNL AS4755 and Reliance AS18101. I almost missed Amazon AWS's announcement on their blog about Indian PoPs for their DNS service - Route53 and CDN service - Cloudfront.
New PoP’s of Amazon in India are at Mumbai and Chennai and I see pretty much consistent BGP announcements to Tata and Reliance from these locations.
And finally academic session over. Done with all vivas and related stuff. Next will be exams likely in June. Time for me to get ready for travel. :) Anyways an interesting topic for today’s post - Google Public DNS. Lot of us are familier with popular (and free) DNS resolvers 188.8.131.52 and 184.108.40.206. I have covered reason in previous posts on why it tends to fail with Content Delivery networks like Akamai which rely on anycasting at bottom DNS layer and simple unicasting on application servers.
Just was looking at routing tables of BSNL. They have a significant address space in /10 - 220.127.116.11/10. Overall this /10 address space is divided into /18 and /20 subnets.
Let’s pick two of such subnets and observe routing tables from route-views:
18.104.22.168/18 22.214.171.124/20 Routing table for 126.96.36.199/18: * 188.8.131.52/18 184.108.40.206 0 3333 3356 6453 4755 9829 9829 9829 i * 220.127.116.11 0 3277 3216 6453 4755 9829 9829 9829 i * 194.