One of my friend went for a VM with a German hosting provider. He got single IPv4 (quite common) and a /64 IPv6. Overall /64 per VM/end server used to be ok till few years back but now these days running applications inside LXC containers (OS level virtualization) make more sense. This gives option to maintain separate hosting environment for each application. I personally do that a lot and infect blog which you are reading right now itself is on a LXC container.
Some updates from personal life… I have joined Fremont based IP backbone & colocation provider - Hurricane Electric and would be working on some cool things at AS6939. :) Updates on blog… I have changed theme and entire look of blog and re-designed it with new plugins, more tweaking etc. As of now blog has more cleaner while theme which gives more space for posting, improved security with some ACLs, forced HTTPS to avoid telcos from injecting iframe in readers on 3G networks (which is very bad and worrying).
Fest time at college - Good since I get lot of free time to spend around looking at routing tables. It’s always interesting since last week was full of some major submarine cable cuts and has huge impact on Indian networks. Anyways, an interesting issue to post today about Global IPv6 routing . There are “dark spots” in global IPv6 routing because of peering dispute between multiple tier 1 ISPs involving Hurricane Electric (AS6939) & Cogent Communications (AS174).
Just now completed IPv6 certification with Hurricane Electric. It was very much fun! Starting was pretty much simple and basic, followed by email server running on v6 - which also I was doing already. I was stuck at most unexpected part - when I had to setup IPv6 based DNS servers. My first reaction was - that’s so simple….later on realized that system was just not accepting my entry and kept on giving error with AAAA records.