Hacker News new | ask | show | jobs
by ised 3891 days ago
Use own root and cache DNS instead of HOSTS. Then use wildcards, e.g.,

  *.doubleclick.net
1 comments
jakeogh 3891 days ago
Tool to automate that: https://github.com/jakeogh/dnsmasq-blacklist
link
ised 3890 days ago
The question is: what is listening on 127.0.0.1?

For example, do you have an httpd listening on 127.0.0.1? Do you bind any other daemons to 127.0.0.1 or the broadcast address?

If you operate your own root you can reassign the authoritative nameservers for doubleclick.net to nameservers you control. You may or may not choose to return "A" records.

link
jakeogh 3889 days ago
Hopefully nothing is on 127.0.0.1:80/443, that way webkit gets a RST back, which I assume is faster (and less error prone) than serving a dummy page. I'll add a note to the README.

Edit: Added a --dest-ip option

link
ised 3888 days ago
"...serving a dummy page."

It could also be less than a page. It could be a dummy resource. For example, in the case of an ad server and a smartphone app that has some screen space reserved for ads. You might want your own resource to appear in that space instead.

Another example is reverse engineering API's and protocols for popular web services, social media, storage, etc. In that case you might want a "dummy server" that serves certain responses.

link
jakeogh 3888 days ago
Interesting. Does --dest-ip[1] solve this?

[1] https://github.com/jakeogh/dnsmasq-blacklist/commit/554e20a3...

link