Verifying domains with both CNAME and TXT - breaking change releasing at Friday
cezary
PROOP

a month ago

I would like to request not deploying a breaking changes on the Fridays without prior notice. Seriously, please. I have devs complaining at 22:00 (my tz) at Saturday that our preview apps are broken.

I also have a question. The changelog has two points about TXT records. One is trusted domain verification.

The other is:
>We shipped support for verifying domains with both CNAME and TXT DNS records, giving you stronger proof of domain ownership and better protection against subdomain takeover.

Are these two distinct features? Is domains not verifying without TXT record desired behaviour? I do not need nor want to set a 'trusted domain'.

I'm asking, becouse It breaks my CI pipeline. We assign a domain and create DNS CNAME records in a GH workflow with subdomains related to PR number.

Bonus question: Are you going to list record names consistently? CNAME is listed without domain while TXT record has the domain.

Completed

0 Threads mention this feature

1 Replies

23 days ago

Hello,

This has been fixed in v4.30.3. We now print the TXT host and required value.


Status changed to Completed brody 23 days ago


Loading...