This belongs to WorldLink Communications (ISP here in Nepal) and I am just 5 hops away from it. So clearly something in middle is hijacking DNS queries and no matter whichever DNS resolver I try to use, the queries actually hit authoritative DNS via 202.79.32.164. Let’s try to verify it using popular “” query. This seems unusual and is the result of basically port 53 DNS hijack. Have a look at these weird DNS replies: dig. I found that many of the servers appear to be DNS resolvers which is unusual. This means, basically, that you have to trust at least one of the servers used.Writing this post from my hotel room in Kathmandu. There is no option, at least none is in the UI, to add custom resolvers. One downside of the project is that you don't have control over the resolvers. Simple DNSCrypt is an easy to use program for Windows to protect DNS queries against man-in-the-middle attacks. Uninstallation worked without issues on several test systems. There is also an option to Force TCP, and to uninstall the Windows service. Simply put, if caching is enabled, Simple DNSCrypt tries to find the information in the cache before resolvers are used to look-up the information. You can disable DNS caching there for instance. The advanced settings give you more control over the service's functionality. This may take a bit of testing to make sure performance is fine. You can switch that off under resolvers by selecting one or multiple resolvers from the list. The service picks the fastest resolver from the list of available servers and uses it. Simple DNSCrypt runs in automatic mode by default. You can uncheck these options as well if you want but it is recommended that you don't unless you run into issues. The program retries resolvers that support DNSSEC and don't log or filter traffic by default.

Opendns dnscrypt check