letsencrypt / letsencrypt/boulder
Log DNSSEC status for CAA queries
Open
Nobody has claimed this yet.
area/va
kind/enhancement
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Simplest solution is just to check if the resolver set the AD bit in the response in our LookupCAA function.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the LookupCAA function in the Boulder codebase and inspect how resolver responses are handled. Determine where the DNSSEC AD-bit status should be logged, then add coverage for a response with that bit set and verify the status appears in the logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100