Tunnel public hostname regression!

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

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

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!

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

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 :joy:

BTW, a UI only workaround is to delete the DNS record manually, whenever you want to add additional routes with the same hostname.

Hopefully CF UI team can add some basic regression tests after the UI revamp/refactor is done.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.