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

Respond case insensitively to A and SOA requests #152

Merged
merged 2 commits into from
Feb 7, 2019

Conversation

cure
Copy link
Contributor

@cure cure commented Feb 6, 2019

Respond case-insensitively to A and SOA requests. Add corresponding tests.

This fixes the autocert feature with Let's Encrypt, because Let's Encrypt does a lookup for the A record with a deliberately mangled case.

… to go in

the Authoritative section, not the Answer section.

This fixes the acme-dns validation for the lego Let's Encrypt client.
…ests.

This fixes the autocert feature with Let's Encrypt, because Let's Encrypt does
a lookup for the A record with a deliberately mangled case.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.676% when pulling 145dcee on cure:respond-case-insensitively into 4f5fad0 on joohoi:master.

@joohoi
Copy link
Owner

joohoi commented Feb 7, 2019

This is a regression that happened in #144

Thanks for fixing it and adding tests to prevent another regression in the future!

@joohoi joohoi merged commit 37db83e into joohoi:master Feb 7, 2019
jacobmyers-codeninja pushed a commit to jacobmyers-codeninja/acme-dns that referenced this pull request Sep 30, 2020
* When appending the SOA for authoritative NXDOMAIN responses, it needs to go in
the Authoritative section, not the Answer section.

This fixes the acme-dns validation for the lego Let's Encrypt client.

* Respond case-insensitively to A and SOA requests. Add corresponding tests.

This fixes the autocert feature with Let's Encrypt, because Let's Encrypt does
a lookup for the A record with a deliberately mangled case.
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.

None yet

3 participants