• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Cloudflare extension - Aliases

TomBoB

Silver Pleskian
Server operating system version
AlmaLinux 8.8 latest updates
Plesk version and microupdate number
Version 18.0.56 Update #4
Hi,
We're testing the Cloudflare extension. One of limits is that Aliases cannot be exported. Which is quite a drawback.

It doesn't state in the official "Limitations" that it's because of Cloudflare API limitation. On the other side it also doesn't state "currently / at the moment".

Can we assume that Alias syncing is being worked on and available at some point, just like it works in the DigitalOcean DNS extension?
 
If you do not have the following snippet in your panel.ini file, could you please add it and try again?
Code:
[ext-cloudflaredns]
adminDomainFilters = 1
 
Yes, we have. Instead of showing only the admins domains (default setting), with that entry it now shows all the clients domains. Which is what we need. However it only shows domains of hosting type website [IE proper website setups], but doesn't show Domains set up as Aliases. Which is a current limitation according to the documentation.
 
Hi Peter, any update if/when Aliases can be exported to Cloudflare?

Without going into too much detail, we'd like to finish projects where we moved from a previous name server provider {Digital Ocean] to CloudFlare. We can't finish those as DO allows for autosync of Alias DNS to their name servers through the DO Extension, whereas the CF extension doesn't allow for that yet.

Doing the switch for domains with Aliases right now means a step back in time and going back to lots more time spent on manual adjustments. (regular Lets Encrypt renewals)
 
@TomBoB Did Digital Ocean change their DNS policy on you? I was just informed by Digital Ocean that I had to establish a billing history to use the free DNS service via the Digital Ocean DNS extension. But being that this is a free service there is no way to establish a billing history :\
 
@TomBoB Did Digital Ocean change their DNS policy on you? I was just informed by Digital Ocean that I had to establish a billing history to use the free DNS service via the Digital Ocean DNS extension. But being that this is a free service there is no way to establish a billing history :\
Hi, just checked again. No, not so far.
 
What is the timeline or a rough ETA to have Aliases auto-transfer to CloudFlare via the CF DNS extension?
 
What is the timeline or a rough ETA to have Aliases auto-transfer to CloudFlare via the CF DNS extension?
Sorry for the delay in answering your question. There are currently no immediate plans to support domain aliases for the CF DNS extension. But we might add support for it in the future if there is sufficient demand for it. I realize that's probably not the answer you where hoping for, but I wanted to let you know anyway.
 
Sorry for the delay in answering your question. There are currently no immediate plans to support domain aliases for the CF DNS extension. But we might add support for it in the future if there is sufficient demand for it. I realize that's probably not the answer you where hoping for, but I wanted to let you know anyway.
Hi,

we have the same problems with our domain aliases. That's why we have the same demand for this function.

Regards,
Ronny
 
Back
Top