As we reported in an earlier post, 2020Media took part in World IPv6 Day, which took place on 8th June 2011. For 24 hours (or more) major websites around the world turned on IPv6 access to test how well this technology actually worked in practice.
Organised by the Internet Society, the project was intended to raise awareness about the need to start the global transition to IPv6 and to enable participants to gather data about potential glitches
2020Media’s website and blog were reachable over IPv6 (in addition to IPv4 of course), and we saw an increase in our normal website visitors on the day. We had no reported problems and our servers coped without any errors, so we consider the day a success.
Not so the boffins at Nominet, who were hosting one of the probes monitoring UK connectivity. For the early part of the day, routing problems there made UK sites, including the BBC look patchy.
One good thing about IPv6 day was that where there were any kind of routing problem, because everybody was watching, those problems were resolved fast.
2020Media staff attended a talk by DNS guru 
Popular content management systems require updating from time to time. Sometimes this is for new features, often because a security loophole needs patching. In this article we’re not going to look at which CMS most often requires updates, but at the upgrade procedure itself. How easy is it, are the instructions clear and easy to follow, what the potential problems, and what can you do if something goes wrong? At the time of writing new major versions of Drupal (7.0) and Joomla (1.6) have been released and no updates have yet been produced for these releases. We therefore concentrate on the older versions, which run the vast majority of existing sites. 
