Compatibility with dnscrypt

[RichardJohnson]

Hello there @pbust

I am using malwarebytes anti malware and Dnscrypt-proxy

Here's my config:

When dnscrypt-proxy is turned on mbam- website blocking does not work....I turn off dnscrypt>flush dns cache>mbam ip test site>working

I have noticed that there is a proxy settings on mbam....If possible what should I enter in proxy address and port to make it work?

I tried 127.0.0.1 port 53 not working

Any workarounds?(or is this the whole point of encrypting dns queries?)

Thanks

[RichardJohnson]

Bumping this post!!!

[exile360]

Greetings

My apologies that no one responded to you sooner.  I just saw this post when I was looking through threads without replies and I think I might be able to help, or at least help troubleshoot.

I'm using DNSCrypt on my own system (like you, I'm currently using Simple DNSCrypt) and have been for well over a year now, and while I did have issues with Malicious Website Blocking compatibility early on during the MBAM 2.0 alpha/beta test phase, I haven't had any issues since then as I worked with the Developers directly on tracking down the cause of the issue so that they could find a solution and get it fixed, which they did before 2.0 was released.  Likewise, since it was fixed in 2.0, I also have no problems between the two now running Malwarebytes 3.0 so I'm not certain why it's causing issues with your system.

So to be clear, when DNSCrypte is enabled, if you visit iptest.malwarebytes.org in your browser you are able to reach the page and it says:

If you are able to reach this page it means that IP protection is disabled on your machine.

But if you disable DNSCrypt and flush your DNS cache, the page is blocked so that you are unable to reach that domain, is that correct?  If so, then I'd also suggest perhaps checking your HOSTS file to verify that it hasn't been altered in some way, and also perhaps try disabling the DNS Client service (it's used for DNS caching by Windows) to see if that helps or not.  The only reason I suggest disabling that service is because I myself am using a large HOSTS file (managed via HostsMan; currently containing over 500,000 entries) which requires disabling that service, so it's possible that due to the fact that I have that service disabled because of my use of a large HOSTS file, that I have not seen this problem as a result.  It shouldn't have any effect, but I'd simply like to eliminate the service as a variable since it's one difference I know likely exists between our two setups.

By the way, what version of Windows are you running this on?  I'm using Windows 7 x64 Ultimate SP1 fully patched myself.  I have not tested this setup on any other Windows versions.

Edited December 16, 2016 by exile360

[RichardJohnson]

Dear @exile360

Thanks for the reply.

Disabling DNS client service did the trick. Its working smoothly now.

I am using windows 8.1 pro x64 (November 2016 update)

Best Regards

[exile360]

Excellent, I'm glad that it worked for you

Now that said, I'm going to report this to the Malwarebytes 3.0 team anyway as disabling that service should not be required in order to make the two get along with each other, so hopefully they'll be able to fix the issue in a future release.

Thanks again for reporting this to us and testing my workaround