Removal on "zone_set" from API

I just received this email with 0 days heads up:

We are making an emergency change today that will affect your ability to sign up customers via the Cloudflare Host API. Specifically, the ‘zone_set’ operation for creating partial zones will be disabled today,
We apologize for making this urgent breaking change.

This basically just killed our partner setup and the single most important reason to use it.
Anyone have any information on what’s going on? This is really frustrating having a client being in the middle of a project, having setup 5 zones, and is just about to move the “production” zone. I’ve worked with quite a few larger companies and the biggest hurdle is always moving the NS.

The biggest argument and possibility of talking clients into Cloudflare was just removed and now makes it easier to recommend other solutions.

6 Likes

I agree, this is our method of working. Transferring the complete DNS to CloudFlare is not an option for us. I wonder why we were not even notified up front so we could decide on an alternative.

2 Likes

Same here. We have many customers who only want to point a specific subdomain to us and want to keep everything else with an existing provider.

Same here :frowning: The vast majority of our clients cannot change name servers and cname was the only option available for them. This kills off a large part of the “partner” system without any explanation, reason or notice.

1 Like

Any idea @TKlein why this is happening? And what are our options to tell our clients.

Indeed. Not being able to add new zones can be worked around, albeit with pain. Not being able to modify existing zones is problematic.

But, we need to know if existing cname zones are going to be turned off with zero notice, as this would take the vast majority of our sites down. Some of our clients need several weeks notice to change DNS records so the same zero notice would not work well.

I received the following response to a support ticket, which wasn’t exactly helpful, apart from seeming to confirm that existing cname setups should continue to work:

grumpf…“potential” security risk…why not fix the real issue instead of removing the entire feature and crippling our services and basically leaves our customers stranded…?
discovering this after at least 10 years of operations makes me wonder…

1 Like

My thoughts exactly

@MoreHelp

As CloudFLare partners for many years, I believe we need more attention from the team.

Can you help us?

Will the API be completely disabled?

Will we no longer be able to use this feature?

Hope the CloudFlare team can answer us here

2 Likes

I replied to their last message on Tuesday morning asking if there were any plans to fix this, for suggestions on alternatives and pointed out this community thread. Still no response after 48 hours.

I think it is shocking how partners are treated. If they do this without communication, whatever the outcome is of this situation will be, they can do it again.

We will search for alternatives.

What! …you cannot even add any new subdomains to current zones anymore.
Now the partner account is useless and our customers are left on whats there for now.
No more sites can be added to the ones you already have.

I haven´t got any answers either and having 140+ zones in there gives me the creeps…

Can you all please raise tickets? It seem like it’s the only way to get CF eyes on this.

Or maybe tag @eastdakota and @jgrahamc on Twitter asking why they killed the partner program.

We’ll see if I get any response. This support/community doesn’t seem to have any CF reps.

Hello everyone, good afternoon.

We are having problems with the CloudFlare plugin in CPanel.

By clicking on (Provision Domain with CNAME Setup)
Return this error to me.

Do you know what it can be?

An unknown CloudFlare error has occurred during zone creation and has been logged. We apologize for the inconvenience and we will fix the problem promptly.

Try to uninstall the plugin and then reinstall the plugin.

Hello @CreatorRevealed
How are you?

This error has been occurring for a few days now, but I have about 160 sites added that were working fine.

Removing and installing the plugin won’t cause problems with those sites that are working fine?

Hi @user11508,

It may be related to this, not sure.

Looks like the same.

It’s an absurd change by Cloudflare.