Tunnel public hostname regression!

[net1]

Looks like tunnel dashboard/configuration has a major regression that breaks existing apps!

The following example configuration used to work fine on my tunnels:

• app.example.com/path-protected
• app.example.com/path2-protected
• app.example.com/path-unprotected

Now it doesn’t! It complains about “Error: An A, AAAA, or CNAME record with that host already exists. For more details, refer to https://developers.cloudflare.com/dns/manage-dns-records/troubleshooting/records-with-same-name/”, when I try to add the second or more path entries for the same domain.

Please fix this. This is quite urgent as it breaks existing apps!

[net1]

Any one from Cloudflare can give an ETA to fix the problem. It’s blocking our testing/deployment.

[net1]

It appears the problem is in UI only (extra check for the POST dns_records call). API to set up the routes (PUT tunnel configurations) still works as expected

[net1]

IMO, the correct UI behavior should be “warn and confirm with user”.