Skip to content

Conversation

@eusouovh
Copy link
Contributor

Description
This PR adds quotes to DNS records to ensure Route53 compatibility during the DNS-01 ACME/Let's Encrypt validation process.

Problem
The current code didn't include quotes in DNS record values, causing DNS-01 challenge failures when used with Route53. Route53 has specific formatting requirements that require certain values to be quoted.

@ldez ldez changed the title fix(vinyldns): add quotes for Route53 compatibility vinyldns: add quotes for Route53 compatibility Jul 11, 2025
@ldez
Copy link
Member

ldez commented Jul 11, 2025

Use the Route53 provider instead of the Vinyl one.

Maybe I'm missing something?

@ldez ldez self-requested a review July 11, 2025 19:42
@eusouovh
Copy link
Contributor Author

Hi, @ldez !
I use VinylDNS to manage Route53. With this setup, I cannot go directly to Route53 - all DNS changes must be made through the VinylDNS provider.

@ldez
Copy link
Member

ldez commented Jul 11, 2025

I found nothing in the API documentation about quotes around the TXT value.

I have no proof that it will not break the other users of Vinyl DNS.

@ldez
Copy link
Member

ldez commented Jul 11, 2025

I added an option to add quotes (VINYLDNS_QUOTE_VALUE=true).

The default behavior is unchanged, so no possible regressions.

@ldez ldez changed the title vinyldns: add quotes for Route53 compatibility vinyldns: add an option to add quotes around the TXT record value Jul 11, 2025
@eusouovh
Copy link
Contributor Author

Perfect, my friend. :)
I really appreciate your help.

Copy link
Member

@ldez ldez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend opening an issue to explain your problem before opening this type of PR.

@ldez ldez enabled auto-merge (squash) July 11, 2025 20:15
@ldez ldez merged commit fae73fd into go-acme:master Jul 11, 2025
7 checks passed
@ldez ldez added this to the v4.25 milestone Aug 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants