Re: If IP6v hadn't been made so goddamn complicated...
"The register though is not one of those sites using IPV6 but of course google and their ad companies are"
Microsoft doesn't, last I checked [except on a few specific servers, last time I sniffed a win-10-nic VM that had IPv6 enabled, which might not actually be theirs, and was probably over a year ago].
Which brings me to the REAL source of the problem: Imagine EVERY! WINDOWS! CLIENT! in the world having a PUBLICALLY! VIEWABLE! IP! ADDRESS!!! [yes, the "no NAT" FUD rears its ugly head].
Truth is that IPv6 CAN be NAT'ted, but nobody will bother doing it. It's truly better if it's FIREWALLED to block ALL of the listening ports that Micro-shaft suddenly FEELS it needs to listen on, but EVERY! STINKING! VERSION! of Windows since XP has been listening on open ports bound to "::" or 0.0.0.0 and the list of ports GROWS (and occasionally MORPHS) with each release. And those ports are (more or less) "well known" especially to those who might want to use them for nefarious purposes (and when new ones show up, they'll be known, too).
So what is the _CAUSE_ of the IT "my computer got hacked while I was on the corporate network" problem? That's right, it's MICROSOFT that CAUSES the problem, with their far-less-than-adequate approach to security. 'Microsoft Firewall' - what a joke. Anyone ELSE remember 'code red'? 'Win Nuke'? Look forward to more of the same when every Windows box is exposed unfiltered to the intarwebs.
Of course this COULD be fixed. By Micro-shaft. But they don't even bother implementing their OWN IPv6, and last time they TRIED, they completely cluster-blanked it...
http://www.theregister.co.uk/2017/01/19/windows_10_bug_undercuts_ipv6_rollout/
(I just checked, and microsoft.com _STILL_ has no AAAA records)