4 ms·
There's a problem that just having an IPv6 address is indistinguishable (for such users) from a server that's not configured or is down. We need a good solution
by PeterisP 7y ago
There's a problem that just having an IPv6 address is indistinguishable (for such users) from a server that's not configured or is down. We need a good solution to indicate to end users that the server is working just fine, but just you don't have IPv6 support and can't reach it because of that.
But I can't send anything to such a user directly if they don't support IPv6 and I don't have an IPv4 address.
Perhaps we need some community-run webservice with an explanatory page saying "Website [something.com] requires IPv6, here's lots of documentation on how to try and fix this" and everyone could point their domain name IPv4 address to that webservice, and the IPv6 address to the real server.
- umanwizard 7y agoWhy would anyone set up such a site? Fewer than 30% of people have IPv6 today.
- PeterisP 7y agoWell, because they (and their entire organization) may be unable to get a publicly routable IPv4 address, because NCC can't and won't assign any more. You can work around it for now, but in the future this will be a more and more common situation.
- umanwizard 7y agoIt means they can’t get one for free, not that they can’t get one at all. IPv4 addresses are trading for around 20/each when bought in blocks of 256. They won’t be prohibitively expensive for any serious hosting provider for the foreseeable future. For hobby projects hosted on a Raspberry Pi in someone’s bedroom, I can imagine a static IPv4 being prohibitively expensive, but that’s about it.
- devit 7y agoBrowsers could just present an appropriate error page when a domain has an AAAA record but not an A record.