3 - Cloudflare DNS Synchronization with CyberPanel

In version v2.0.0, CyberPanel has added the ability to synchronize DNS entries between Cloudflare and CyberPanel DNS on your own server

What is Cloudflare?

Cloudflare is reverse proxy service, which offers certain features such as

  • CDN (Cloud Delivery Network) by caching the data from your website and serving them from their Point of Presence nearest to your visitor. This decreases the load on your server and saves bandwidth
  • Network Gateway by automatically translating between IPv4 and IPv6
  • SSL provider by issuing a certificate for your domain on their own server with one click with zero changes on your server
  • WAF (Web Application Firewall) as Cloudflare sits between your visitors and your server it can block
  • It offers direct installation of many apps without changing anything on site.

Why do you need synchronization

In order to use Cloudflare the nameservers of the domain are changed to the ones provided by Cloudflare and that means any changes done such as adding subdomains or changing mail providers or using a new DKIM key on CyberPanel have to be manually inputted in CloudFlare’s DNS panel. You have to repeat the process for every change you make to every domain on your account on CyberPanel.

That’s a lot of manual data entry and we at CyberPanel made it easier for you to do by adding Cloudflare integration right into your CyberPanel.

What does CyberPanel Synchronisation do

CyberPanel has added deep integration with Cloudflare which can automatically do the following on your behalf

  • Add, edit or remove DNS records: Whenever you create new DNS entry like for email or subdomain or text verification, you don’t have to log in to your Cloudflare account and do it again manually
  • Create necessary zone info and domain in Cloudflare: When you create a new website on CyberPanel, CyberPanel checks if that domain is in your Cloudflare account.
    • If it is already present, Cyberpanel will create all the DNS records and copy them over to Cloudflare DNS records.
    • If it isn’t present. CyberPanel will create the domain in Cloudflare with a basic free account and then create all the DNS records and copy them over to Cloudflare DNS records.
  • Constant sync: If you change any of the records on CyberPanel or any record is missing from the Cloudflare account, this feature will update and/or populate the changes on your Cloudflare account. Note that changes on Cloudflare will not be synced to Cyberpanel.

How to use Cloudflare integration

From version v1.9.5 onwards, you can use Cloudflare integration by going into DNS-> Cloudflare

You will be greeted by a screen like this

In order to obtain API token from Cloudflare click the avatar on the right of you Cloudflare account and under profile setting click the API token tab

Click on the blue “View” button next to Global API Key. Enter your password to get your API token key

Please enter the email address that you use on the Cloudflare account and you Cloudflare API token generated in the last step on Cloudflare setting page in CyberPanel and select Enable for Sync local Records to Cloudflare

Click save

On the next screen, you can add remove or sync your DNS between CyberPanel and Cloudflare

Voila, in less than 10 minutes we were able to integrate Cloudflare with Cyberpanel and we have made DNS updates easy as a breeze directly from the CyberPanel



so i do not need input the DNS at CF anymore ?
only need add website… then… all set ?

Good question, what do we need first? put dns, or just sinc with cloudflare?

Only need to add website and all sync goes automatically

both sync ?
changing at CP will make change at CF ? and viceversa ?

How do I remove the Cloudflare details? When I clear the email and key, i get this error:


Also, disabling the sync doesn’t actually work - I just created a new website after disabling and the records synced with Cloudflare automatically.

Changes on Cloudflare won’t be synced on CyberPanel side.


@shoaibkk can you reproduce the issue mentioned by @nick.chomey

noted… so after i do sync… i never need to open/access (except emergency) my Cloudflare anymore to add or change/edit, add, remove the zone info like mx in-A cname etc

thankyou for your update/info…

1 Like

I have this error, what could be an isshue?

Hello, can you fixed the problem? I have the same problem and need a resultion. Thx for answer me

I agree! Synchronisation is one of the biggest players in digital communication. In telecommunication systems, timing synchronisation is critical for retrieving the original delivered signal. It is required to synchronise to the transmitter’s symbol timing in order to have a communication system that runs at the proper time and in the correct sequence. I am not sure if what I am about to say is still relevant in Cloudflare, but is it really correct that digital communication systems that use coherent modulation require three levels of synchronisation: 1. Phase, 2. Symbol, and 3. Frame?

1 Like

Why is CyberPanel creating all sorts of DNS entries in Cloudflare for mail (a mail.domain.com entry and, TXT, SPF, DKIM entries for all subdomains)? I don’t even have DKIM turned on for my site. Moreover, when I delete them all and resync with CloudFlare, they just get re-created again! I can’t get rid of them.

1 Like

This reason I don’t use sync, get tons of dns records I don’t have any clue what they for.

@Dreamer do you just manage DNS directly on cloudflare? I prefer CP because it is far more efficient - cloudflare requires far too many clicks to edit/create an entry.

I do everything from cloudflare so can proxy traffic from there.
I really like use their WAF custom rules and bot fight mode. With those I can easily reduce requests for server 20-60% per site depends how busy site.

Thankyou @usmannasir at first glance, it looks like a more streamlined way to handle DNS, but I see CP creates a lot of unnecessary DNS records.

I am not sure my DNS records on Cloudflare are optimally set up before creating this token. Everything works and I don’t get errors, but I have seen so many zone record examples, my head is spinning. Can you post what is the ideal DNS zone record to start out with? I have seen CNAME for www as well as others creating A records for www. So many different zone records, so which ones should we be using in CP and CF??

I already have mail related records on Cloudflare pointed to a third party mail provider using their provided MX, DKIM, DMARC, TXT, etc. So I don’t want Cyberpanel creating more mail related records and copying them over to Cloudflare DNS records, as I see [quote=“usmannasir, post:1, topic:103, full:true”]

In version v2.0.0, CyberPanel has added the ability to synchronize DNS entries between Cloudflare and CyberPanel DNS on your own server

These are my questions before making a move to syncing API.

I would agree, if we can be sure Cyberpanel is not going to start creating conflicting:unnecessary DNS records.

I also use CF proxy NS, but using this token on CP, from what I am reading, still benefit from Cloudflare’s proxying and WAF custom rules while syncing CP to CF?

On first read, this looks good in theory, but for existing sites it may be a bit tricky, if your DNS is not set up properly on Cloudflare to begin with.

I have posted my DNS zone record on CP with the appropriate identifications blurred. Can someone post what they think is the ideal DNS zone record.

Thanks in Advance.

I definitely don’t use CF token it’s just making tons of unnecessary records. I manually add all needed records to CF.

Thanks for a fast reply. @Dreamer. So far this forum’s replies are snail paced :snail: so it’s refreshing to know someone is actually reading these posts .

I just checked my DNS in CP, and you are right! CP has already created unnecessary A records, even one for mail.domain.com, which we don’t use, a CNAME for www and some TXT records, even though the mail records are on CF pointing to a third party mail server.

It’s more work maintaining everything in CF, at least I know what it is and why it is there. Now I just want to get it right in this domain so I can export/import the correct Zone files to the rest of the domains, since I want a uniform structure when I hand this project over to manage in my absence.

Here is what I have. How does it look to you?

Not sure what records you need. For my self I just set basic records for domains and mail records depending where mail is hosted.