Unable to delete DNS record

[corruptcomputer]

What is the name of the domain?

gupton.xyz

What is the error message?

This record is managed by Email Routing. Disable Email Routing to modify/remove this record.

What is the issue you’re encountering

I am unable to delete the DNS record for “cf2024-1._domainkey”, it tells me I need to disable email routing, but email routing is already disabled.

What steps have you taken to resolve the issue?

I tried to delete the record, I checked all of the settings in the Email tab and was unable to find anything that looked helpful to removing this, and I tried the terrible AI support bot that was damn near useless; none helped with resolving the issue.

What feature, service or problem is this related to?

Mail records

What are the steps to reproduce the issue?

Try to delete the record for “cf2024-1._domainkey”, see error message.

Screenshot of the error

[corruptcomputer]

Oh thats awesome, it also deleted the first image when I added a second one. Heres the first image I was trying to add there:

[GeorgeAppiah]

Perhaps you disabled Email Routing without deleting the DNS records?

Do you have an option to delete the records when you expand the domain or click the three dots at the extreme right?

[corruptcomputer]

The only records it gives me the option to delete are my valid records that I want to keep:

I also don’t know exactly what ‘Fix records’ in the three dots menu does, but I’m guessing it would just try to delete my valid records.

[corruptcomputer]

@system Can someone from the support team manually unlock this record from your side so I can delete it? I’m having DKIM errors being returned for some emails I’m sending and I think this is the issue, but I am unable to resolve this on my own due to this bug in the Cloudflare web UI.

[corruptcomputer]

I was able to resolve this by causing a brief email outage: deleting my valid records, enabling email routing, disabling email routing, deleting the email routing records, and re-adding my valid records.

This is a terrible way to solve this issue, but since it seems like Cloudflare doesn’t want to give its customers any support this seems to be the best we can do to work around this bug.