letsencrypt / letsencrypt/boulder
Differentiate errors when the DNS resolver is unreachable versus a DNS error during validation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
During a recent outage, the DNS resolver was unreachable.
In boulder's metrics, it isn't possible to distinguish an error reaching the resolver versus one caused by validation.
I'd like to be able to distinguish those cases, as it's an important split between an internal and external problem.
I'll open an LLM PR which implements what I'd like, though I haven't put much effort into it, so please feel free to just close it and handle differently if desired.
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
No files, tests, or entry points are named. Start by tracing the DNS validation path and its metrics, then identify where resolver reachability errors and validation errors are recorded; done means the metrics clearly distinguish those two cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100