keybase / keybase/keybase-issues
DNS proof fails when multiple TXT records are present
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
On keybase.io my DNS proofs are succeeding for maxlaumeister.com but failing for bitlisten.com. I have a feeling that this is due to bitlisten.com already having a TXT record (an SPF record, to be exact). I added the proof as a second TXT record and as of now the proof is still live if you do a dig bitlisten.com TXT. The DNS proof verifies in the client (running keybase id maxlaumeister correctly verifies me as the bitlisten.com DNS admin), but at the same time the keybase.io website says the DNS proof has failed.
Guess as to the problem: Keybase.io code is only looking at the first TXT record for verification.
Likely user workaround for this issue: Put the TXT record on the _keybase subdomain instead of apex.
Sort-of-related (Closed) Issue: https://github.com/keybase/keybase-issues/issues/750
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
No files, tests, or entry points are identified. Start by reproducing the discrepancy with dig bitlisten.com TXT, then compare the client and keybase.io website verification behavior when multiple TXT records exist. Done means the DNS proof succeeds when the proof record is not the first TXT record.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100