Jump to content

dcam

Members
  • Posts

    2
  • 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've uninstalled MalwareBytes because with this defect (and a router whose primary DNS address is IPV6, secondary IPV4), all lookups computer DNS lookups take ages to failover from IPV6 to IPV4, the result is absolutely intolerable. For me, IPCONFIG /ALL shows: DNS Servers . . . . . . . . . . . : fda5:7a90:47f9::1 192.168.16.1 fda5:7a90:47f9::1 With MalwareBytes installed, this doesn't work, here I am invoking my router's IPV6 address for resolution: $ nslookup www.google.com fda5:7a90:47f9::1 Server: UnKnown Address: fda5:7a90:47f9::1 Non-authoritative answer: Name: www.google.com Addresses: 2404:6800:4006:805::2004 142.250.66.196 But with MalwareBytes installed, the IPV4 lookup works fine: $ nslookup www.google.com 192.168.16.1 Server: openwrt.lan Address: 192.168.16.1 Non-authoritative answer: Name: www.google.com Addresses: 2404:6800:4006:805::2004 216.58.196.132
  2. I have similar issues with MalwareBytes recently installed. My router's local DNS proxy advertises an IPV6 and IPV4 address, but when running MalwareBytes, all DNS resolution is horribly slow because it Windows is trying to connect IPV6 first, which fails, and then the DNS resolution fails over to IPV4 which works fine, so every single DNS resolution has a wait time to fail over to IPV4. I notice that when running MalwareBytes, I cannot ping my router's IPV6 address either. I've uninstalled MalwareBytes to get around the problem.
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.