If you’re one of the lucky few to have an ISP that natively supports IPv6, you’ll find that you will now resolve and connect directly to this blog over IPv6 rather than IPv4. Nothing exciting, but I hadn’t realised that cPanel could let me use individual IPv6 addresses with /128 subnets.
It’s nothing exciting, sure, but I hadn’t realised that cPanel could let me use individual IPv6 addresses with /128 subnets. It’s interesting that when checking over this blog’s stats, there are an ever increasing number of people connecting via IPv6. So it’s all good news. IPv6 will play a much more important part in the infrastructure of the internet in the forthcoming months and years, so getting this done now ensures that I don’t have to worry about this too much in the future.
(Sidenote: This isn’t the first time drake.org.uk has been available with IPv6 connectivity; many moons ago when I was putting CloudFlare through its paces, it presented an IPv6 tunnel that connected to the backend – e.g. the webserver, via IPv4. I’ve also ran drake.org.uk on a Debian nginx server that had native IPv6 out the box too. But as I deal with cPanel enquiries every day, it makes sense for me to run this blog under cPanel – and up until fairly recently, IPv6 support in cPanel has been rather clunky.)