Understanding Cloudflare IPv6 compatibility

Check whether the hostname is proxied and identify the actual problem before changing network settings. Distinguish a visitor’s connection to Cloudflare from Cloudflare’s separate connection to the hosting origin.

1. Open the Cloudflare zone and review its DNS proxy status and Network settings.
2. For ordinary plans, understand that IPv6 compatibility is enabled by default. Current Cloudflare controls allow customising or disabling this setting only for eligible Enterprise zones.
3. If an application cannot process IPv6 visitor addresses, update its address handling where possible. Review Cloudflare’s Pseudo IPv4 option only when a compatibility workaround is appropriate.
4. Test the proxied hostname from IPv4 and IPv6-capable networks. Check application logs and visitor-IP handling without assuming the origin must have a public AAAA record.
5. For DNS-only records, configure their actual A or AAAA destinations according to the underlying service rather than relying on the proxy setting.

The website should work for both supported visitor network families, and application logs should handle the address format correctly.

If a toggle described in an old guide is missing, check current plan eligibility instead of looking for an obsolete cPanel plugin control. Do not publish an incorrect origin AAAA record to force IPv6. Remove or correct an invalid record only after confirming the intended DNS-only or proxied design.

• Checking whether Cloudflare is active for a hostname
• Adding an IPv4 A record in cPanel Zone Editor
• Connecting a hosted domain to Cloudflare without breaking email
• Understanding Cloudflare CNAME flattening at the zone apex

• Cloudflare documentation