Cloudflare v2

AdamM

hi
Will integration with Cloudflare continue to be developed?
I believe it needs a few improvements

When "Impersionate client" I can't add the Cloudflare integration I set in CP for my clients and my websites.
CNAME flattening doesn't work, I can't add CNAME for root domain although cloudflare supports it.
I would like to set global Cloudflare DNS for each client with sync in my Cloudflare account.
Once the customer creates the domain, the NS change message should point to Cloudflare NS and already have the domain added in Cloudflare.

Does anyone else have any ideas for improvements?

XN-Matt

Don't think 3 will be possible.

CloudFlare binned off their hosting partner API which made this possible. They do have their standard partner API but won't support what you want and I believe a standard API key is limited to a set number of zones.

The hosting partner API (and account) was ideal as the end user could have their own CF login direct but you would still manage the account for them via the API. Shame they removed it.

AdamM

@Adam any update?
I am cary a lot in point 2

DracoBlue

Agree

lenineto

I'd like also to add the need for a non-destructive integration. Currently the integration wipes out cloudflare records. This is specially bad when migrating sites to our servers.
We should have the ability to initially SYNC what's in Cloudflare, and then when ready, we could update the records in Enhance and PUSH the changes.

josedieguez

lenineto 100% agreed. when we started and figuring out how to configure everything, we got our NS records wiped out, at least twice.

MissMyagi

Okay, that's really not in any way, shape or form a good thing. Hope the devs are onto this issue.

Adam

If you synchronise a domain from Enhance to CloudFlare, it is a one way process and will replace the current CloudFlare zone with the one in Enhance. When you select to synchronise a domain with CloudFlare, this is explained in a confirmation modal. If you are doing this with an existing domain and there are records in CloudFlare that you don't want to lose you can add those records to Enhance before syncing the domain with CloudFlare for the first time.

We have an open feature request to add an option to pull the existing records into Enhance before the initial sync. This may be possible in the future.

jeff

Adam

Making it easier in Enhance to import the Cloudflare DNS record export file would go a long way to helping. Manual data entry sucks.

MissMyagi

jeff Cannot disagree

fizzpopmedia

I am testing out Enhance as it has a lot of great features but the current cloudflare configuration is an absolute deal breaker for me. I was testing it out on my own website and selected the cloudflare integration and poof all of my existing records were gone.
The current approach seems completely backwards to me. Enhance should query cloudflare for all existing records and then allow suggested records to be saved by their individually or all at once.
Is there a plan for when this will actually be fixed?

twest

fizzpopmedia the way it works now if fine, you just need to setup your DNS records on enhance before activating the Cloudflare integration. I think a more advanced DNS system is coming eventually though, maybe it will have a records import feature or more configurable controls.

fizzpopmedia

For me, I want cloudflare to be the definitive information source as other parties have access to the data and could make updates within cloudflare. The functionality that I would prefer would be

The ability to pull in existing records from cloudflare
The ability to add/delete/modify individual Cloudflare records from within Enhance
Confirmation that the domain is properly connected in the domains section of a particular website.
https://nimb.ws/DM43q7v

FWIW - I am using Gridpane currently and while the integration is a bit slow, it does work the way that I need it to work

twest

fizzpopmedia a V2 would need to have a setting to allow either option to be the source, because for my use case (and I would presume most users) I need Enhance to be the definitive source. The reason is because if a server crashes, we need Enhance to be able to update all the dns records automatically for affected sites when they get restored to a new server. That's how it works now, an absolute lifesaver for disaster recovery.

fizzpopmedia

I can understand why you would want to manage it that way. Perhaps there could be a switch by each record (with an option to enable all) where you could choose to allow (or not) Enhance to override records.
Then, in your use case - all of the Enhance records would override.
And in my use case, I would only give Enhance override for the A @ record.

Out of curiosity twest what happens in your current setup (with Enhance as the definitive source) if someone edits a record in Cloudflare? Does it get overwritten by Enhance? If so, does it happen right away or would it only happen if you viewed the DNS records in Enhance?
It seems to me that some funky stuff could happen.

twest

fizzpopmedia I think enhance only syncs with CF when there's an event, like DNS in Enhance gets updated. Customers know to edit their Cloudflare DNS from their hosting panel, but there are some that choose not to use the Cloudflare integration. That's fine too, they just lose the automated DNS fix if/when their site gets moved to a different server (like during disaster recovery), and if they make a subdomain site then they need to manually create the record for it at cf.

fizzpopmedia

Seems like it would be more accurate to consider it a full record set overwrite then right?
For example, if the @ A record is updated in Enhance then ALL records in CF are deleted and only the records that exist in Enhance would be created in CF.
Does this 👆️ seem accurate to what actually happens?

xyzulu

fizzpopmedia That is what currently happens, yes.

slimx

Adding CF API key to the customer account is not very hard. I'm okay with that being separate as some clients have their own cloudflare accounts too. I vote against changing that.

The CloudFlare DNS record wiping, i think this would easily be solved by simply making a decent map of how cloudflare exports their records. Simply hit export cloudflare dns records, and import into enhance (when we have this feature it will solve the whole problem). (ChatGPT could write this lol)

I for the life of me do not understand why having a CAA record (prior to syncing) breaks enhance if enhance deletes all the records anyway. It's such an annoying setup lol.