keybase / keybase/keybase-issues
DNS proof failure
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Using Amazon Route 53 DNS.
I already had a 'zepherin.com' TXT entry, so had to use the '@'.
$ dig -t TXT -q @.zepherin.com
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.3 <<>> -t TXT -q @.zepherin.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48029
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;\@.zepherin.com. IN TXT
;; ANSWER SECTION:
\@.zepherin.com. 300 IN TXT "keybase-site-verification=3zxC8wX4BLYRljecwhuUAUieO2EprG9p6qBrfsIw8VY"
;; Query time: 52 sec
;; SERVER: 72.3.128.241#53(72.3.128.241)
;; WHEN: Thu Jul 28 23:12:08 2016
;; MSG SIZE rcvd: 114
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
Reproduce the reported Route 53 TXT lookup with the provided dig command and compare its result with the DNS proof verification behavior. Trace how the verifier handles the @ record; done means the existing keybase-site-verification TXT record is accepted or the required record format is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100