Proxy IPV6 request to IPV4

Feedback Feature Request Submitting & Feedback
1

Type

Product improvement

Description

I would like to be able to access an IPV4 only server from an IPV6 host, when using a proxied CNAME

Benefit

Currently, I have an AWS EC2 instance which only has an IPV6 network interface, due to the additional cost of IPV4 addresses.

I would like to have this instance be able to call an API Gateway deployment, however API Gateway does not support IPV6.

I am able to call IPV6-only hosts from an IPV4-only host through a cloudflare proxy, but not the other way around.

This feature would allow easier transition to IPV6, as IPV6 only servers would still be able to call services which don’t support it.

2

That’s not true. Cloudflare will switch either way.

  • If a AAAA record is :orange: Proxied, it will accept IPv4 and IPv6 requests, and send them to the IPv6 origin.
  • If an A record is :orange: Proxied, it will accept IPv4 and IPv6 requests, and send them to the IPv4 origin.

Here are my test server logs from my testing. My first two requests were curl -4, and my second two requests were curl -6

172.70.230.32 - - [19/Jul/2024:20:52:31 -0700] TLSv1.3 "ipv4.example.xyz" "GET / HTTP/1.1" 200 4306 "-" "curl/7.68.0" "4.62" "gzip, br"
2400:cb00:650:1024::a29e:9fe4 - - [19/Jul/2024:20:52:45 -0700] TLSv1.3 "ipv6.example.xyz" "GET / HTTP/1.1" 200 4306 "-" "curl/7.68.0" "4.62" "gzip, br"
172.70.114.157 - - [19/Jul/2024:20:53:04 -0700] TLSv1.3 "ipv4.example.xyz" "GET / HTTP/1.1" 200 4306 "-" "curl/7.68.0" "4.62" "gzip, br"
2400:cb00:650:1024::a29e:9ed1 - - [19/Jul/2024:20:53:15 -0700] TLSv1.3 "ipv6.example.xyz" "GET / HTTP/1.1" 200 4306 "-" "curl/7.68.0" "4.62" "gzip, br"
3

Hey, thanks for your reply - I am in particular referring to CNAME records here. I’ll investigate a bit further.

4

Turns out the problem was that I needed to prepend https:// to my curl request…

Apologies.

1 Like
5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.