DNS verification fails on local machine due to local DNS server
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I verified my domain by adding a DNS TXT record. When I visit keybase.io and login, I see that my domain is properly claimed. Running the macOS app, however, the domain shows as unreachable. I chalk this up the fact that I run a local DNS server for my LAN, which is the first DNS server in the list of such servers to be used locally. Since my local DNS server gives clients several DNS servers from which to resolve host names, I suggest that keybase use all the available DNS servers to verify domains.
my log id: 38353a0ab04c084e4fddd91c
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 with the macOS app's domain-verification path and the DNS lookup behavior described in the report; use log ID 38353a0ab04c084e4fddd91c while reproducing the local-DNS setup. Done means domain verification no longer reports the claimed domain as unreachable when the first configured DNS server cannot resolve it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100