11–20 of 63 posts
If tunneled DNS becomes prevalent, these hostname/domain approaches won't work. So it'll come down to blocking at IP level. And that will likely be harder.
If tunneled DNS becomes prevalent, these hostname/domain approaches won't work. So it'll come down to blocking at IP level. And that will likely be harder.
That doesn't really have anything to do with the tunneling of DNS. Authentication + ignoring the local resolver do.
The bit that will prevent me from pulling this trick in the future is the fact that it’s encrypted.
I've been using privoxy forever, along with 255.255.255.255 entries in /etc/hosts for domains I want to block. Not sure what using dnsmasq would buy me over this setup.
Earlier quoted context omitted.
That doesn't really have anything to do with the tunneling of DNS. Authentication + ignoring the local resolver do.
I mean it’s not really the fact that it’s hard coded. On my network I redirect all DNS traffic to my local resolver. Doesn’t matter if an app tries to hit 8.8.8.8 or whatever. The bit that will prevent me from pulling this trick in the future is the fact that it’s encrypted.
Encryption is technically the hard wall of "technically infeasible" but I say authentication because at that point you start getting massive delays in things being operationally feasible since you're waiting for things to give up on resolving rather than signaling it's unresolvable/a bogus location.
dnsmasq simply isn’t very good.
What’s the difference to pihole?
I've been using privoxy forever, along with 255.255.255.255 entries in /etc/hosts for domains I want to block. Not sure what using dnsmasq would buy me over this setup.
I've been using privoxy forever, along with 255.255.255.255 entries in /etc/hosts for domains I want to block. Not sure what using dnsmasq would buy me over this setup.
Works on all devices, including mobile phones and tablets.
* * If device do not use public (like 1.1.1.1) or custom DNS
Why not unbound/bind/etc?