New beta mbam3 web protection dns error

[mightaswell]

Using the new beta 3.06 if  I visit  http://iptest.malwarebytes.org/  using either IE or Chrome I get a DNS error.  Visiting  http://52.21.84.70 via IE or Chrome, I see "Malwarebytes has blocked a potentially malicious website."  

All protection layers are reported as on.  

logs.zip

MB-CheckResult.txt

FRST.txt

Addition.txt

[Robertiy]

Same here!  SOLVE the problem...

Why can't you resolve the IP address to a Domain name sever, so as, MB 3 alerts the user?

At least you (R&D) released it as a BETA update, which 3.0.xxxx is anyway!  Well, maybe RC1 or 2 at most.

Robert

P.S. I am not beta testing; that is your job.  Pay me/us and then fine!

Edited February 17, 2017 by Robertiy

[Norwian]

Same problem here MB 3.0.6.1469 CU3.

Using MB 3.0.5.1299 web protection worked ok. On both http://iptest.malwarebytes.org/  and http://52.21.84.70   receiving

 

            

 

But with MB 3.0.6.1469 and CU3 on http://iptest.malwarebytes.org/  receiving

 

 

And with http://52.21.84.70 web protection works ok receiving

 

 

 

Wait for a tech comments.

[Norwian]

Same problem here MB 3.0.6.1469 CU3.

Using MB 3.0.5.1299 web protection worked ok. On both http://iptest.malwarebytes.org/  and http://52.21.84.70 showing

 

 

But with MB 3.0.6.1469 and CU3 on http://iptest.malwarebytes.org/  receiving

 

And with http://52.21.84.70 web protection works ok receiving

 

Wait for a tech comments.

[Robertiy]

4 hours ago, mightaswell said:

Using the new beta 3.06 if  I visit  http://iptest.malwarebytes.org/  using either IE or Chrome I get a DNS error.  Visiting  http://52.21.84.70 via IE or Chrome, I see "Malwarebytes has blocked a potentially malicious website."  

All protection layers are reported as on.  

logs.zip

MB-CheckResult.txt

FRST.txt

Addition.txt

Now Firefox (51.0.1 64 bit) Unable to connect error. Thank GOD, you do not work for me OR with ne...FIRED!  Why?  Inefficient.

 

[Robertiy]

Sorry, user error.  Firewall blocked all access to Fiirefox.

Robert

[bdubrow]

Thanks mightaswell for the logs!

And thanks to the others on the thread for confirming you're also seeing this.  We are currently investigating. 

[Robertiy]

4 minutes ago, bdubrow said:

And thanks to the others on the thread for confirming you're also seeing this.  We are currently investigating. 

22nd?  Do not care of the timetable, just FIX  it!

 

[Telos]

2 hours ago, Robertiy said:

Sorry, user error.  Firewall blocked all access to Fiirefox.

Robert

Thank GOD, you do not work for me OR with ne...FIRED!  Why?  Inefficient.

[Super Dave]

Same for me also on the new beta. There is a 6 page thread about this issue prior to the new beta. D Collins stated Mbam was aware of the DNS issue.

[Robertiy]

Now, since the Beta update, Exploit Protection does not start. Reboot, does not solve the issue...it just says, "Starting..." And, the systray remainder, stays visible.

I give up!!!!!!

Robert

[mightaswell]

The same issue with DNS  error also occurs when visiting http://iptest.malwarebytes.org/    on a  laptop running Win 7 X64. 

                                                          

When visiting http://52.21.84.70 MBAM gives correct warning message.

Edited February 18, 2017 by mightaswell
add image