Jump to content

pzi123

Members
  • Posts

    6
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I don't think anything changed. Still the whole DNS lookup is going through Malwarebytes proxy at 127.42.x.x. If your destination is on the black list like all DDNS domains. etc. and it is not on the exception list that is centrally maintained your connection will fail. Your domains status on the exception list may be unstable and you see that failures. I just did the dns lookup for my zapto.org and it returns local proxy but the ping still works since proxy finally return the right address: Peter@pzi-s3:~$ nslookup > pzi.zapto.org Server: 192.168.77.3 Address: 192.168.77.3#53 Non-authoritative answer: Name: pzi.zapto.org Address: 127.42.0.1 > exit Peter@pzi-s3:~$ ping pzi.zapto.org Pinging pzi.zapto.org [127.42.0.0] with 32 bytes of data: Reply from 67.190.20.39: bytes=32 time=1ms TTL=63 Reply from 67.190.20.39: bytes=32 time=2ms TTL=63 Reply from 67.190.20.39: bytes=32 time=1ms TTL=63 Reply from 67.190.20.39: bytes=32 time=1ms TTL=63
  2. As malwarebytes provides us with such an indispensable service we techies should help them in implementing the right solutions. Here the idea to take over the DNS resolution on windows and point it to invalid local address is maybe the first thing you could think of. Unfortunately it is not ideal - the user of malwarebytes gets stunned and has no idea what just happened. What I would suggest is: 1. instead of using that 127.42.0.0/? use a valid malwarebytes IP that points to a URL with explanation. 2. change the logic in malwarebytes software to allow the user to add exclusion that would allow to connect to the black-listed URL anyway
  3. thanks Devin - it works fine now. I still think that users should be able to add exclusions and that should take precedence over the white list you maintain.
  4. We have 'exclusions' setting to do that - unfortunately that exclusion does not change malwarebytes behavior. We can't start posting sites to that list every time we want to exclude/allow a URL.
  5. hi Firefox! Do you have a business version running somewhere? Can you quickly run this from the cmd prompt: nslookup pzi.zapto.org
  6. As soon as I start malwarebytes (3.0.6) the DNS resolution on my windows 10 or windows 2012r2 stops working for DNS names in DDNS domains like *.zapto.org. The IPs returned from nslookups for my pzi.zapto.org show bogus values of 127.42.0.1. As soon as I stop malwerbytes the nslookup returns correct external IPs. This looks like malwarebytes is trying to protect client from connecting to DDNS IPs. This breaks number of things. Any ideas? Tried to work with malwarebytes support but without luck.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.