Closed Wabuo closed 8 years ago
1) Regarding dnsmasq you might find useful info here: https://gaenserich.github.io/hostsblock
2) The hostsblock script performs a system-wide blocking of domains listed in /etc/hosts.block
(or /etc/hosts
as you might prefer) so you don't need to make anything else in any web browser settings.
@Sadi58 In case of Chrome/Chromium you need to disable the intern DNS stuff, because it will bypass the system settings if you don't. I think this superuser.com answer answers it quite god.
And thx for the link, but I think this should be in a config section in the README.md
Thanks a lot!
I agree that a DNS config section in README.md file would be helpful indeed.
I think I didn't know this internal DNS setting in Chrome but I have it disabled (default setting maybe?).
It's called "Use a prediction service to load pages more quickly" in version 50.x now.
So chrome://dns/
tells me "DNS pre-resolution and TCP pre-connection is disabled."
I'm missing a section about how to use it together with dnsmasq. And how to configure dnsmasq correct
Bay the way I think a link to a tutorial about how to make Chrome/Chromium use the system dns/hostfile would also be appreciated.