All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Need a little help in understanding IPv6-only site access
Hi,
let me keep it short. My origin-server had ipv4 (shared) and ipv6 (dedicated) both enabled. I'm using cloudflare dns. I've added A-record for IPv4. The site has cloudflare orange enabled. So its DNS + reverseProxy.
In last month due to heavy AI bot crawling on shared ipv4, somehow cloudflare was giving error in accessing sites on entire node as told to me by my host. They asked me to use IPv6 instead which was dedicated as a solution.
So I swapped IPv4 with IPv6, removed the A-record from CF, and added AAAA record.
On cPanel too i removed shared Ipv4 and enabled on ipV6.
Earlier the public Clouflare records (IP address) were showing that my site on their Edge could be accessed over cloudflare's IPv4 and IPv6 so it had 4 IP records publicly showing (2 for ipv4, and 2 for ipv6).
The moment I switched to IPv6-only on my origin, Cloudflare dropped the public record for their 2 Ipv4 address pointing to my site and only remaining 2 IPv6 started pointing.
My question is: It seems to me that my site is only accessed by IPv6 on cloudflare (as they removed IPv4). Does it harms the site in terms of connectivity from users? I mean, someone having IPv4 only residential IP can access the site or not?
Comments
Cloudflare can still serve the site over IPv4 even if your origin is IPv6 only. The visitor connects to Cloudflare over IPv4, and Cloudflare connects to ur origin over IPv6.
So IPv4 only users should still be able to access the site. it's need the proxy enabled
ok thanks.
If you have no A record, your site isn't going to work over IPv4...
I don't see how this is going to have any impact unless bots are crawling directly to your IP, bypassing Cloudflare?
Even if it’s IPv6, it still works behind the Cloudflare proxy because Cloudflare terminates the client connection at the edge and proxies the traffic to the origin. The origin IP stays hidden, and Cloudflare handles the IPv4/IPv6 connection between the user and the server.
I understand that.
Cloudflare still needs to publish an A record if it's providing NS services for you. I'm not saying it isn't, but I feel like fundamentals are being ignored here.
exactly. that's the problem.
when I removed A (ipv4) record from Cloudflare dns page, and checked my site on bgp.he.net, it returned only two IPv6 shared ips alloted by Cloudflare. Though my site was connecting correctly from my home as it has ipv4+v6 but i am worried if its get connect if some user on ipv4 is trying to connect my domain hosted with cloudflare ipv6. Actually, cloudflare should alot ipv4 and ipv6 both.
As long as the proxy icon is Orange, IPv4 only users can access your site without issues. You do not need to add dummy A records or extra configurations
Yes running a dns lookup to your domain should show both IPv4 and IPv6 alloted by cloudflare anycast.
if ur okay, send me the link cuz there's no IPv6 here. also, u can test it using a VPS.