Keybase Client not able to read DNS
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Twice keybase Client failed to read DNS verification text place on my website host server. The information is correctly in place as it is the same process used for other verifications done in the past. Maybe the client need to try after 48 hours, as the server did indicates that it can take up to 48 hours
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
The report names no files, tests, or entry points. Start by reproducing the Keybase client’s DNS verification lookup for the website, then trace the client path that reads the verification text and compare it with the expected DNS record. Done means the reported verification succeeds or the failure is narrowed to a reproducible cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100