In case your DNS server is listening on 0.0.0.0:53, you had to try limiting this to a specific IP address, the one of your server, e.g. There is no reason not to do it unless this address is one of the DNS servers defined in the active network connection's IPv4 properties. You may also try dnscrypt-proxy with local address 127.0.0.1, the normal "localhost" loopback address. " I also tried using a different local address 127.0.0.70 and the same error message came up." To test this out, you had to temporarily change the DNS server forwarders to something different again, e.g. The first results in a binding error, and the second leads to an endless loop with no DNS responses. Your DNS server may be listening there as 0.0.0.0:53, and you cannot use it again for listening by the dnscrypt-proxy and as forwarders in the DNS server. What happens if you use your localhost address for DNS queries? Then there are no issues with the DNS connection to OpenDNS.
" The nslookup test for both TCP and UDP passed." 0.0.0.0 which would include the localhost IP address range as a whole, see below. Then this address 127.0.0.7 is not explicitly being used, but may be implicitly used as e.g. " I ran netstat -nao | findstr /i "foreign 127.0.0.7" it shows no results."
0 kommentar(er)
