Resolving DNS Sync Conflicts: Cloudron and Cloudflare Interaction Issue

[IniBudi]

I discovered a conflict between Cloudron and Cloudflare when clicking the "Sync DNS" button.

Upon clicking it, I checked the DNS settings on Cloudflare and found that the domain my.cloudron.domain, which is not proxied, only uses IPv4 while IPv6 is still being proxied by Cloudflare. As a result, some services, such as email, are not functioning properly.

Moreover, not only is the my.cloudron.domain affected, but applications like the VPN on Cloudron are also using Cloudflare's proxy for IPv6, causing the VPN service to fail. Is this considered a bug?

I hope this information proves useful to others as well.

Thank you.
Regards.

[nebulon]

Have you enabled ipv6 in your Cloudron, so it also syncs up those records? If you don't use ipv6 you should be able to safely delete those records in the Cloudflare interface.

[IniBudi]

@nebulon yes, I am using ipv6 enable on my server. I think some app like VPN and my.cloudron.domain in my case didn't sync properly. It's only IPv4 that's not proxied with Cloudflare, the IPv6 still proxied with CF.

[girish]

@IniBudi you should remove the proxy status of IPv6 from inside CF. Cloudron doesn't touch the CF status unless it's adding a new record (this depends on the "proxy" checkbox in the Domains view). This allows users to set the proxy status outside Cloudron and manage it as they need .

[IniBudi]

@girish My question is: does the "Sync DNS" feature only disable IPv4, requiring manual deactivation of Cloudflare's proxy for IPv6? In my case, for both the VPN application and my.cloudron.domain, I had to manually disable Cloudflare’s proxy for IPv6.

[girish]

Do you have the "Enable proxying" flag enabled in the Domains -> Cloudflare configuration ? This whole discussion only applies if you have that flag changed. Cloudron does not touch the proxying flag if that is disabled.

When enabled, it will set the proxying flag when adding new cloudflare DNS records. This is set only when adding and in all other situations that flag is left untouched . It does this for both ipv4 and ipv6 records.