Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipconfig /flushdns run over 24 hours #577

Closed
StefanStrauss83 opened this issue Apr 20, 2020 · 7 comments
Closed

ipconfig /flushdns run over 24 hours #577

StefanStrauss83 opened this issue Apr 20, 2020 · 7 comments
Assignees
Labels
false positive all false positive review requests

Comments

@StefanStrauss83
Copy link

Hello,
Sorry, for my bad english.

I Use the Update Batch.
ipconfig /flushdns run more than 24 hours with many CPU usage. In this Time the PC is offline.
He build the local DNS Database in this Time?
The PC has a SSD and 2,5GHz Processor und 8GB RAM.
Whats the problem?

@StefanStrauss83 StefanStrauss83 added the false positive all false positive review requests label Apr 20, 2020
@StefanStrauss83 StefanStrauss83 changed the title flushdns flushdns run over 24 hours Apr 20, 2020
@StefanStrauss83 StefanStrauss83 changed the title flushdns run over 24 hours ipconfig /flushdns run over 24 hours Apr 20, 2020
@mitchellkrogza
Copy link
Member

Windows seems to really struggle with a very large hosts file. I'm really not sure why flushdns is hanging for so long though. Have you tried running update straight after reboot and not after the machine has been running for a long time?

@StefanStrauss83
Copy link
Author

After each restart, the laptop was offline for 1 hour and the DNS client service had CPU load. I have emptied the hosts again.

@stale
Copy link

stale bot commented Jul 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 1, 2020
@spirillen
Copy link
Contributor

spirillen commented Jul 3, 2020

Hey @StefanStrauss83 you should take a look at the unbound for windows.... That is the right tool to manage this, hosts files are so 90's and for some weird reasons still a live.

You can find unbound at https://nlnetlabs.nl/projects/unbound/download/ and I have a small quick start config here https://www.mypdns.org/w/rpzunbound/ and here https://gitlab.com/my-privacy-dns/rpz-dns-firewall-tools/unbound and here https://gitlab.com/rpz-zones/toolbox/-/tree/master/unbound. Chose should be able to get you started, not to use hosts files as sources but partial RPZ. (Response Policy Zones are still not fully supported in unbound) but I have a lot of converted hosts files to RPZ here https://gitlab.com/my-privacy-dns/rpz-dns-firewall-tools/unbound/-/tree/master/nxdomain

Tell us what you think after trying it.

PS: Here is a short and dirty speed comparisons between hosts files vs a real recursor https://www.mypdns.org/w/performance_test_of_hosts_file_vs_dns-recursors/

NLnet Labs
GitLab
The zone files to be used with [Unbound](https://nlnetlabs.nl/projects/unbound/about/) From NLNetLabs
GitLab
The toolbox is for various collections of scripts to help improve and complete the mission
GitLab
The zone files to be used with [Unbound](https://nlnetlabs.nl/projects/unbound/about/) From NLNetLabs

@stale stale bot removed the wontfix label Jul 3, 2020
@georgengelmann
Copy link

georgengelmann commented Jul 16, 2020

Hello

I tried using the .bat file on Windows 10 - then DNS client CPU usage jumped to 10-20%, network was blocked

I rebooted in safe-mode - copy the hosts.original to hosts (I could not change the hosts file in normal boot mode, because the DNS client was using it and it's not possible to stop the DNS client in normal mode)

The line-breaks are not Windows line-breaks, but that's not the issue here (I tried changing them): Windows can't handle large hosts files. Some added hosts are fine: SpyBot immunization adds 500kB - 10MB is too big for DNS

You should probably remove the Windows .bat file or add a warning.

@spirillen
Copy link
Contributor

Hey @georgengelmann In case you just won't try to install the better, faster and safer approach of installing a DNS recursor like the unbound for windows, I would recommend you to have a look it @ScriptTiger's script ScriptTiger/Unified-Hosts-AutoUpdate#23

For your note about the size of this hostfile will brake most microsoft product, I agree with you.

@funilrys could you point me to a good line in the README.md where to put a note on this, and I will try to find the time for it while my bad disk is restoring 😒

@funilrys
Copy link
Member

funilrys commented Sep 6, 2020

Please prefer our DNS Server (#590).

Closing.

@funilrys funilrys closed this as completed Sep 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
false positive all false positive review requests
Projects
None yet
Development

No branches or pull requests

5 participants