Hello,

all our Domains are pointing to Cloudflare DNS Management via Nameserver. We know you are working on a automated Cloudflare-Sync-Solution. In the meantime is there a solution not to manually enter all DNS records that Enhance creates automatically into Cloudflare? Or is the only way to do without Cloudflare and enter the Enhance nameservers directly in the domain registrar to enable automated DNS management?

Thank you in advance!

At the moment we don't have any deep integration with Cloudflare. We are looking into the possibility of a deep integration with their API.

I believe that Cloudflare will look for and duplicate any common DNS records from your existing zone. Therefore if you leave your nameservers set to your Enhance cluster then add the domain to Cloudflare, they should be able to pull in records like mail, @, etc without manual entry.

The only issue is when you move sites between servers in your cluster, you will still need to update Cloudflare with the new IP.

The only issue is when you move sites between servers in your cluster, you will still need to update Cloudflare with the new IP.

This could be addressed by enhance making an API call to CF when the site is migrated OR I really like that idea of have a proxy role where potentially any IP where the role is installed could forward the request to the correct backend allowing for continuous migration and even multiple A records / a little DNS based availability-load balancing.

Huge upvote here as we have thousands of sites operating through Cloudflare. In fact at this point, I rarely see a site not using cloudflare in one way or another.

If the offering doesn't exist presently, just keep it simple, disable internal nameservers/dns completely. Allowing management of everything through cloudflare.

  • updating IPs is easy in CF, even when migrating/moving sites
  • adding records is easy, for instance, following best practices to add "staging.domain.com"
  • mail records, easy

@necrom like the suggestions, but see these more as long-term options vs right now.

Curious as to how you are all using Cloudflare currently.

I have tried a few times to join their partner program with no luck, Are you able to just purchase the business tier and add the offering to your clients?

Currently a fan of BunnyCDN/DNS and using that for clients but it's all manual - wouldn't be opposed to jumping on the Cloudflare bandwagon if Enhance adds it and there's a way to use it for clients without partner program.

I have several customers who for privacy reasons wouldn't want to use Cloudflare, for legal reasons couldn't use Cloudflare or for anti-competitive and bad-neighbour reasons want to avoid Cloudflare. While I welcome cloudflare support it should IMHO be a lower priority than other stability focused features like seamless server migrations / Proxy on server migrations.

Actually I guess this is where you argue priority should be put into third party module capability, so the users or suppliers can decide what is priority by developing their own support for their prefeed third party providers. I'd rather not see a circumstance where enhance is favouring any third party over any other.

Not this is remotely about other features, isn't server migrations working?

@Ned I doubt business worth much. We're on the Enterprise plan and it runs us about 5k a month. That being said we're working with high-traffic bloggers and easily over 100 million monthly pageviews.

I can't imagine not using Cloudflare, I have site or consult pass my desk, 99.99% already have it. Are there exception, but fuck me can't imagine sidelining something like this because of it.

Would be good to see people put forward positives, vs negatives we have no control over. And anyone trying to offer best in class, isn't offering some inhouse offering they concocted just because, they are leaning on industry leaders.

Would love Cloudflare support in Enhance, where all/most part of the DNS is handled by Cloudflare.

5 days later

+1 for Cloudflare. Don't forget QUIC.cloud too.

FYI Quic.cloud has launched the beta of their new partnership program and you should take a look at their control panel. It's superb, much easier for end users than CF and doesn't cost 5K/month. For people on LSWS i think it makes more sense to use QUIC.cloud since it adds all the page optimization services and sync with LSCP.
You can now create a CDN package within QC, attach your QC client domains to your partner panel and manage all the CDN settings, client domains etc... from your Quic.cloud partner dashboard.

If you can't afford CF enterprise, then QUIC.cloud partner is the best alternative.

@Adrien we're on LSE (litespeed enterprise) and Cloudflare Enterprise partners. What most overlook is that CFE comes with CSM (customer solutions manager) and CSE (customer solutions engineer), hence the price (which would cost me an arm and leg internally). And from a performance standpoint it's simple, we have edge caching at 270+ location worldwide, argo smart routing, smart tiered caching, and a mind blogging number of features.

Beyond that, there is nothing wrong with Cloudflare Free, Pro, or Business plans, which cover the entire spectrum needs wise. And the functionality is essentially the same across accounts. Plus it is dead simple to operate, while still offering an API for more complex cases.

My hope overall is that at least 1 leading solution is added first rather than trying to add 2-3 all the same time and causing unnecessary delays and chaos.

    I would also be looking for Cloudflare integration. Beyond the caching in multiple locations, we have customers who undergo DDoS attacks and since placing them into the Cloudflare infrastructure, they have all been mitigated. That's my prime reason for using Cloudflare. DDoS attacks are hard for anyone to mitigate, but their network is unmatched (in my opinion).

    For me... if there was somehow I could integrate into the ECP properly (webhooks, addons, etc) then I could code something myself to communicate with the Cloudflare API.

    @ss88us absolutely, our servers drop everything not flowing through Cloudflare. You own the servers and have access, I imagine if you really want to you could. But are likely similar to us, why bother given it works as is and focus on growing the business and other priorities.

    digitalexpanse Yes I entirely agree with you. No confusion here and CloudFlare first.
    It will benefit a majority of users.
    PS: thank you for the explanation about CF enterprise. didnt know about these tools.

    6 days later

    Hi all - I'm new here. I'm looking to migrate entirely to Enhance by the end of 2023.

    A really cool feature of Enhance is the seamless server migrations - but it's not exactly seamless if clients are using Cloudflare's proxied DNS. I recently migrated a bunch of managed sites for clients, and for each one, I had to obtain and access their Cloudflare accounts to update proxied A records.

    The benefit if there was this integration and it allowed for the changing of proxied records is that the DNS migration would be instant. It typically takes less than 30 seconds for a proxied record change to propagate to all of the CF datacenters.

    So if you were to build an API integration - would you allow per-site/account API keys?

    24 days later

    +1 Cloudflare integration is a required feature. Most websites today use cloudflare and very few use quic.cloud too. If there is an integration it would be awesome. Also, it would show "connected" when cloudflare is integrated on enhance cp

    17 days later

    Hopefully coming very soon, it's one of the most-requested features.

      Adam can you write some documentation of how it works before I enable it? Some DNS entries for my Cloudflare point to 365 and they cannot get erased. I think I'll need to know if Enhance is the "master" and if so, I've got the task of making sure all DNS entries on Enhance are correct BEFORE it syncs to Cloudflare, etc.

      Aliysa_Enhance changed the title to Integration Cloudflare DNS Management [RELEASED].
      Write a Reply...
      Follow @enhancecp