Windows doesn't resolve LAN hostnames

[ghiki]

With dnscrypt enabled, Windows can't goto LAN resources (local shared folders/files, my NAS..., error is "Windows cant access to %NETWORKNAME%"). I tried disabling dnscrypt-proxy and the resources are available at the moment.

Current forwarding rules are:
*.lan 192.168.1.1
*.local 192.168.1.1
10.in-addr.arpa 192.168.1.1
192.in-addr.arpa 192.168.1.1
254.169.in-addr.arpa 192.168.1.1
lan 192.168.1.1
local 192.168.1.1

And of course, the network router is in 192.168.1.1

[ben-page]

I use forwarding rules for this exact purpose and it works for me. One thing that jumps out at me is that wildcard aren't supported by DNSCrypt (or necessary).

https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Forwarding

[ghiki]

I know (I only tried with It for discarding all the options), anyway the same rule without wildcards are at the bottom. I also tried without It and in other PCs (Windows 10 x64) with same result.
I noticed if I click in a network device, primarily the popup error appears, but if I click on It for 8-10 times, finally It founds and connects

[ghiki]

I tried now, and also, sometimes, my NAS doesn't appear in network shares if DNSCrypt is running (maybe due the other network share is resolved through WINS instead DNS)

[ben-page]

But have you tried it without the wildcards? They may be causing dnscrypt-proxy to fail to parse the entire forwarding-rules.txt.

Like I said, it works for me. Also, you may have more luck asking for help on the dnscrypt-proxy repo. This is just a front end. Here is my forwarding-rules.txt. Maybe that will be helpful to you. It forwards my local domains to my domain controllers/dns servers.

168.192.in-addr.arpa  192.168.1.7, 192.168.1.6
mydomain.com          192.168.1.7, 192.168.1.6
mydomain.local        192.168.1.7, 192.168.1.6
mydomain.net          192.168.1.7, 192.168.1.6

[ghiki]

Yep, now I tried like this:

[ghiki]

Really...very strange, if I disable DNSCrypt, my NAS appears in Network, if I enable, then, it disappears:

[ghiki]

Solved! It was because this option blocking IPv6

I thought that blocking IPv6 would be resolved through IPv4