microsoft / microsoft/vscode-documentdb
Investigate: Potential DNS resolver issue
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 22
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 21
Description
Some setups can't be properly discovered. We were hinted to look into DNS resolvers. Creating this issue to track progress.
Azure DocumentDB account, DNS, "connection refused"
Contributor guide
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 reproducing the setup-discovery failure with an Azure DocumentDB account and a DNS resolver that returns “connection refused.” Trace the discovery flow to identify where DNS resolution fails; done means the affected setup can be discovered successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100