Simple Dnscrypt Need to stay open?

Open
#536 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
desktop, networking

Research direction

Start by reproducing the reported behavior in Simple DNSCrypt: close the application after enabling the service, then check whether DNS resolution continues and whether automatic selection remains limited to two resolvers. Review the system-tray behavior and automatic resolver setting; done means documenting the expected lifecycle or confirming and fixing the resolver-selection problem.

Written by the indexing model from the issue text.

Description

Does Simple DNSCrypt need to stay open on the system tray? Or is it more for editing, enabling the service and closing the application?

I ask because I noticed that I only seem to connect to the same two resolvers for a while now, even though it's set to automatic.

Dominant language
C#
Stars
2.5k
Forks
249
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DNSCrypt/SimpleDnsCrypt

All issues in DNSCrypt/SimpleDnsCrypt

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.