Can't block websites using Terminal

Do you have VPN or Private Relay on? I had the same issue and found out that Private Relay was bypassing it - I turned off private relay and works like a charm.....now if someone can figure out how to make both of them work!

I tries this putting this into hosts:

127.0.0.1 instagram.com

127.0.0.1 www.instagram.com

127.0.0.1 https://instagram.com

127.0.0.1 https://www.instagram.com

and then:

sudo killall -HUP mDNSResponder

and:

sudo dscacheutil -flushcache 

and it worked as promised.

I wouldn't really call this "blocking," you're just routing the URL to a new IP address. I guess the end result is the same, but you're not really "blocking" the domains. `Don't want to use Screen Time because it's easy to workaround.` - There is an easy workaround for this method as well.

I don't know your end goal here.. If you have children and are trying to block certain sites set up Parent Controls that will affectively block these sites.

I would also say it's more efficient blocking these sites at the router / modem level as it will persist over your Wi-Fi and all devices connected cannot access the website. Blocking this on each device individually is a hassle and obviously only works on Macs, as this will not prevent iPhone and iPad from reaching the website.

Set up your network with a Pi-hole or similar for DNS, and block all outbound DNS queries from your network at your firewall except for those originating from the Pi-hole host, and set the Pi-hole as the DNS server within your DHCP server configuration.

PS: that last entry in /etc/hosts shown above is incorrectly formatted, and—once corrected—a duplicate.

yokevinnn wrote:

Thanks for the response! For your note on the last entry, do you mean the line with https? (Wonder if an incorrectly formatted entry has any effect on it functioning?)

This file is for domains only, is decades older than URLs and HTTPS and related, and is older than DNS itself.

Best case, the error here gets ignored.

Worst case, the error causes something (else) to tip over.

This text file is a very ancient and low-level and central part of IP networking.

The directions you're following are amusing, too. This part of the directions isn't going to work at all well: "For example, to block YouTube, I would enter the following in Terminal: 127.0.0.1 www.instagram.com".

And the cache flush command shown s also incorrect. It's more properly this:

sudo dscacheutil -flushcache

If you try to use the command listed, you'll get an error:

% sudo dscacheutil -flushcach
Password:
Usage: dscacheutil -h
       dscacheutil -q category [-a key value]
       dscacheutil -cachedump [-buckets] [-entries [category]]
       dscacheutil -configuration
       dscacheutil -flushcache
       dscacheutil -statistics
% 

I didn't look for other errors or issues with the directions.

I'd use Screen Time here, or would use Pi-hole or something else here, or a DNS-blocking service, and would generally discourage using the /etc/hosts file for this and such. It'll work for what you're trying yes, if you're careful, and if the directions are correct. Or that Rescue Time app mentioned earlier, if that works for you. For some folks, I've also removed the problem apps. Forcing a new download slows down the habit.

ericm007 wrote:

Do you have VPN or Private Relay on? I had the same issue and found out that Private Relay was bypassing it - I turned off private relay and works like a charm.....now if someone can figure out how to make both of them work!

The purpose and design of Private Relay is in conflict with the centralized data collection purpose of the first-few-hops VPN.

If you want privacy and security, consider using end-to-end TLS and Private Relay.

If you want your data to be centralized, personally identified, and quite possibly he metadata collected and logged, use end-to-end TLS as is usual, and wrap that im the first-few-hops VPN.

If you do need a first-few-hops VPN for geolocation shifting or testing CDN content or such, and still want some modicum of privacy, have a look at running your own Algo server.

Hey, I was having the exact same problem as you specifically with Instagram, and what it took was blocking all the other domains Instagram uses, a list of which I found here https://cleanbrowsing.org/2021/10/how-to-block-instagram/. I'm also using this system for productivity reasons, best of luck.

That's not what the hosts file is for.

I would definitely use Screen Time and/or use your router/modem. The /etc/hosts file isn't for blocking domains like you're doing. I'd recommend against it as it can cause other errors.

If you're willing to pay money for a subscription, you might want to look at Rescue Time. I've used it during times when I felt the need to get better control over my time and found it quite helpful.