Manually assigned 127.0.0.1 ::1 as DNS shows interface as still deactivated in SimpleDNSCrypt

Open
#569 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Start by reproducing the issue in SimpleDNSCrypt with 127.0.0.1 and ::1 assigned manually, then compare the interface status with the DNS traffic observed in Wireshark. Trace how SimpleDNSCrypt determines whether an interface is activated and verify the result against the running dnscrypt-proxy service; done means the status reflects the working DNSCrypt configuration after reloading.

Written by the indexing model from the issue text.

Description

If 127.0.0.1 and ::1 are manually assigned as DNS on the interface, DNSCrypt shows the interface as not activated.

I'm using a PS script to switch manually between using / not using DNSCrypt.
And it does work from what I'm seeing in wireshark though.
Not using DNSCrypt by manually assigning e.g. 8.8.8.8 on the interface's DNS works.
Switching back by manually assigning 127.0.0.1 and ::1 still makes SimpleDNSCrypt showing the interface as deactivated from DNSCrypt, even after reloading SimpleDNSCrypt.

I was not able to figure out what else SimpleDNSCrypt ist changing on the interface by activating it.
I'm not touching the service, it's configured and running.

It should be that simple, because as stated here that's all:
"Open the network settings, and in the TCP/IP panel, if it's automatically, change it to manually, if it's manually, remove all existing DNS IP addresses (backup first), and then set it to 127.0.0.1."

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.