DNS Client overloaded when using biggest host file, causing "permanent" internet connection loss about hosts HOT 5 CLOSED

I'm busy today so I just dropped in to point you in the right direction with an actual solution: compress the hosts file. The DNS Cache service can not handle that many line entries (and contrary to popular belief it's not the file size that's the issue, but the number of lines to process). I actually have a tool to do so as suggested in the 'Interesting Applications' section of Steven's README (I have both the script version and an actual command line program; I recommend the latter at it is exponentially faster and has more options). See 'Hosts Compress' - Windows version in the aforementioned section of the README of this repository. I'll be back with more information later if necessary. With this method there's no need to disable DNS caching and the hosts file will still block all redirected Urls.

from hosts.

Thank you for this @Master-64.

Have you read Warning: Using this hosts file in Windows may require disabling DNS Cache service in our readme file?

As far as I can tell, this is all documented, yes?

You are correct, this is my mistake for looking past. I figured it was an issue with the operating system itself, and it having issues with processing that many lines. As I believe there is nothing else to comment on since a solution to this issue has already been addressed with two different methods, I'll be closing this issue.

from hosts.

Hello! Thank you for opening your first issue in this repo. It’s people like you who make these host files better!

from hosts.

Thank you for this @Master-64.

Have you read Warning: Using this hosts file in Windows may require disabling DNS Cache service in our readme file?

As far as I can tell, this is all documented, yes?

from hosts.

@Master-64 Fair warning that if you use the disabling DNS cache method then things like WSL will not be accessible.

from hosts.