Hacker News Reader

Comment by ams6110 | Hacker News Reader

I have this in my /etc/hosts:

  127.0.0.1  www.facebook.com
  127.0.0.1  facebook.com
  127.0.0.1  connect.facebook.net
  127.0.0.1  facebook.net
  127.0.0.1  ads.facebook.com
  127.0.0.1  ads.ak.facebook.com

Anyone know of any others?

View on HN

Run your own resolver on 127.0.0.1, and your own authoritative nameserver on 127.0.53.1, and configure the resolver to ask the nameserver (returning NXDOMAIN) for

  * facebook.com
  * doubleclick.net
  * google-analytics.com
  * su (abuse)
  * 2o7.net
  * any others you want; get ideas from the MVPS hosts file

Since facebook domains (fbcdn.net, facebook.net, etc.) are all serviced by facebook.com nameservers, returning NXDOMAIN for *.facebook.com will thereby sabotage all facebook related queries. This way you won't have to play whack-a-mole with future facebook tracking hosts, so long as they use facebook.com nameservers.

Or hell, just create a list of prefixes announced & owned by AS32934, Facebook, and block all. Just to be sure.

From this file: http://winhelp2002.mvps.org/hosts.txt

127.0.0.1 ads.ak.facebook.com

127.0.0.1 creative.ak.facebook.com

127.0.0.1 creative.ak.fbcdn.net #[textads]

If you are ok with losing FB content, I also have

    127.0.0.1 static.ak.fbcdn.net
    127.0.0.1 www.static.ak.fbcdn.net
    127.0.0.1 login.facebook.com
    127.0.0.1 www.login.facebook.com
    127.0.0.1 fbcdn.net
    127.0.0.1 www.fbcdn.net
    127.0.0.1 fbcdn.com
    127.0.0.1 www.fbcdn.com
    127.0.0.1 static.ak.connect.facebook.com
    127.0.0.1 www.static.ak.connect.facebook.com

Reply on news.ycombinator.com