Well, after some tinkering and ditching my free DNS provider, which I was relaying my he.net IPv6 tunnel through. I have now setup an AAAA record through my paid DNSs and it seems my test-ipv6.com score is now a 10/10, with only two (!) tags.
"Your browser has real working IPv6 address - but is avoiding using it. We're concerned about this." and..
"It appears that you use a tunnel mechanism for either IPv4 or IPv6."
The second one is obvious. The first one I can't seem to change in Firefox. Apparantly Firefox decides that it prefers to use IPv4 instead of IPv6. Isn't it supposed to try IPv6 first and fall back to IPv4 if the first try doesn't work?
It seems they're saying both Chrome and Firefox do this as they should, and that it's pretty much normal.. Should I just take that 10/10 and be happy with what it is since it's still a tunnel and not native?
Either way, I took a stab at contacting my ISP and asking them, only to get an answer that 1% is currently native IPv6, and that residential customers do not have it available at this time. Basically, "in the future" is about what I got out of them, along with an 800 contact number where I guess I can ask about it in the future. I haven't tried the number yet, only because it's probably just a regular customer support number anyways - where I won't get any information I don't already know - until it is offered to customers here.
Anyways, at least I got that 9/10 up to a perfect score now.
Is there some kind of new trendy way we could be putting both our IPv6 and IPv4 addresses in the nodelist that I don't know about? Examples for understanding purposes appreciated, please. :)
