My bad, should've been more clear - yes, it's the default in some places. What I meant is actually treating ipv6 as first class everywhere. For example:
In other words, I expect steering people to do ipv6, then maybe ipv4 as well rather than the opposite would give the internet as a whole another big jump in ipv6 usage.
This will show my lack of ipv6 knowledge but I’ll ask anyway. Say I have an endpoint service somewhere listening only on ipv6.
Let’s take any sort of CDN out of the equation for simplicity. Can I use Cloudflare DNS for the service, such that anyone using ipv6 will connect directly to my service, of course— but can CF do some magic ipv4->ipv6 translation/bridge sort of thing, so that someone on ipv4-only will also be able to connect to my ipv6-only service?
I’d imagine the answer is hopefully yes and perhaps this is trivial stuff these days, but anyway I’m thinking of setting up a blog and might go ipv6 only with it..
Cloudflare makes a website dual-stack from the user's perspective, regardless of whether the server is IPv4-only or IPv6-only.
Typically, both the A and AAAA records point to the same Cloudflare proxy, because serving IPv4 and IPv6 via different infrastructure requires a lot of care to avoid subtle brokenness.
You should be able to advertise your ipv6 endpoint in the AAAA record, going direct to the origin, while make the A records pointers to Cloudflare which can then proxy back to your v6-only origin servers.
And the chart in that blog shows the dent we made.