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.
Re:AWS adds an extra 5.5M IPv4 addresses
by jon-wood on Saturday August 14, 2021 @05:26AM
(#28179321)
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.
Re:AWS adds an extra 5.5M IPv4 addresses
by indigodaddy on Saturday August 14, 2021 @02:28PM
(#28182885)
Awesome, thanks for the answers all! Sounds simple enough!
Re:AWS adds an extra 5.5M IPv4 addresses
by cortesoft on Saturday August 14, 2021 @01:10PM
(#28182247)
It wouldn't be magic.... the AAAA record for DNS would point to your server, and the A record would point to cloudflare.
Of course, it is up to the client, then, to decide which address to use. Not all clients default to v6 even if it is available.
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..