News for hackers. Stuff that matters.

A comment on AWS adds an extra 5.5M IPv4 addresses. Parent comment

Re:AWS adds an extra 5.5M IPv4 addresses by jgrahamc on Saturday August 14, 2021 @03:52AM (#28178904)
We do default IPv6 on. https://blog.cloudflare.com/always-on-ipv6/

And the chart in that blog shows the dent we made.

[ Parent | on HN ]
Re:AWS adds an extra 5.5M IPv4 addresses by viraptor on Saturday August 14, 2021 @04:30AM (#28179058)
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:

This guide doesn't even mention AAAA records: https://www.cloudflare.com/learning/dns/dns-records/

API examples are ipv4 unless the option takes ipv6 only: https://api.cloudflare.com/#dns-records-for-a-zone-update-dn...

Your terraform examples use ipv4 only: https://registry.terraform.io/providers/cloudflare/cloudflar... https://registry.terraform.io/providers/cloudflare/cloudflar...

And many others.

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.

[ Parent | on HN ]
Re:AWS adds an extra 5.5M IPv4 addresses by indigodaddy on Saturday August 14, 2021 @04:37AM (#28179092)
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..

[ Parent | on HN ]
Re:AWS adds an extra 5.5M IPv4 addresses by p1mrx on Saturday August 14, 2021 @11:35AM (#28181449)
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.

[ Parent | on HN ]
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.
[ Parent | on HN ]
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!
[ Parent | on HN ]
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.

[ Parent | on HN ]
Re:AWS adds an extra 5.5M IPv4 addresses by glogla on Saturday August 14, 2021 @04:36AM (#28179085)
Nice, good work!
[ Parent | on HN ]