DNSCrypt / DNSCrypt/SimpleDnsCrypt

Name resolution for "_ldap._tcp.dc._msdcs.fios-router.home" & "wpad" BLOCKED by dnscrypt-proxy! How to fix?

Open
#410 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2.5k
Forks
249
PR merge metrics
No merged PRs in 30d

Description

Love Simple DNSCrypt 64-bit, but maybe there's a problem. I have Simple DNSCrypt 0.6.4 (64-bit) pushing dnscrypt-proxy 2.0.22.
**On every reboot** of Win 10 Pro 64-bit version 1803 (home PC wired to 1Gbps FIOS gateway), **I get two or three Warnings in Event Viewer with "Event 1014 DNS Client Events"**:
- "Name resolution for the name wpad timed out after none of the configured DNS servers responded."
- "Name resolution for the name _ldap._tcp.dc._msdcs.fios-router.home. timed out after none of the configured DNS servers responded."

One suggested fix is to turn off "Automatically detect settings" in Proxy in Network & Internet in Control Panel. But would that interfere with dnscrypt-proxy?? Or is there a way to add needed info to "the configured DNS Servers"?

What do you suggest? Thanks.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.