mandatoryprogrammer / mandatoryprogrammer/TLD-Health-Report
Why using DNScheck?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- No language data
- Stars
- 18
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
DNScheck is no longer maintained. Why not its successor, [Zonemaster](https://zonemaster.net/)?
Contributor guide
No contributing guide indexed for this repository
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 reviewing how the daily report uses RIPE's DNSCheck, then compare the current integration with Zonemaster's documented interface. Done means the report can use Zonemaster in place of the unmaintained DNSCheck while preserving its existing TLD health reporting behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100