Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CNAME chasing for TXT records #1120

Closed
wants to merge 1 commit into from
Closed

Conversation

hslatman
Copy link
Member

A potential fix for resolving TXT records that are behind CNAME records, as used by e.g. https://github.com/joohoi/acme-dns.

@hslatman
Copy link
Member Author

User who reported the issue on Discord reported this fix doesn't work (yet). Unsure if it's a (local) DNS issue, or if something else is up. Am going to try to replicate this with an acme-dns setup.

@hslatman
Copy link
Member Author

hslatman commented Oct 25, 2022

The issue turned out to be DNS 😝

When running step-ca in a container, with dnsmasq as a DNS server, the TXT query would result in a SERVFAIL if a CNAME had to be resolved. With bind9, there was no issue and the CNAME was resolved correctly to the TXT, without explicitly doing net.LookupCNAME. So, no changes required in how step-ca resolves queries now. Some additional diagnostics might help, though, for example in the form of a clearer error.

@hslatman hslatman closed this Oct 25, 2022
@Ziphone
Copy link

Ziphone commented Nov 30, 2023

The drafted fix did the trick for me. I'm also using the ACME-DNS. As it appears to me, net.LookupTXT does not follow CNAME(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants