letsencrypt / letsencrypt/boulder
VAs should be marked unhealthy if they can't reach their DNS resolvers
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Similar to how SA instances are marked unhealthy if they can't talk to the database.
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
Start by locating the existing SA health check for database connectivity and the VA code that reaches DNS resolvers. Compare their failure-handling paths and identify where health status is recorded. Done means a VA that cannot reach its DNS resolvers is marked unhealthy, with coverage analogous to the SA behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100