Hacker News Reader

Comment by ISL | Hacker News Reader

Thanks for the catalyst to re-enable my /etc/hosts approach to simplifying my life.

I'm surprised to see that adding:

  127.0.0.1 youtube.com www.youtube.com

to /etc/hosts doesn't seem to block youtube, but every other line I added blocked/routed as expected. Is there something special about youtube and chromium?

View on HN

IPV6 can cause some issues around this because browsers will typically do an IPV4 and IPV6 lookup in parallel. Try adding a

    ::1 youtube.com www.youtube.com

also.

Yes, some sites are more resilient somehow. I experience the same thing with twitter. You could try flushing your dns cache but IIRC that didn't even work for me.

It has now started blocking correctly. Must have needed something to get flushed.

Back to it.

  $ noprocrast.sh

Reply on news.ycombinator.com