Before you start
- Finish the built-in setup in Guardrails first.
- Pick one resolver or filter and use it consistently.
- Know which account is admin and which one is daily use.
- Plan to test every change before you stop.
iPhone / Mac
Use a DNS layer so the device is not depending on built-in controls alone.
Add a family-safe DNS layer
- On iPhone or iPad, open Settings → Wi-Fi.
- Tap the blue i next to your network.
- Tap Configure DNS.
- Switch to Manual.
- Delete old DNS servers if they are listed.
- Tap Add Server and enter a family-safe resolver such as
208.67.222.222or208.67.220.220. - Tap Save.
- On Mac, open System Settings → Network → Wi-Fi → Details → DNS.
- Add the same resolver there too.
- Test a known blocked site in Safari and in any other browser still installed.
If you want provider-side rules or account controls, sign up for the DNS service’s dashboard and set those limits there too.
Tighten the browser path
- Keep only one browser if you can.
- Remove the browsers you do not need.
- In Screen Time, keep the adult-site block from Guardrails active.
- Use Allowed Websites Only if you need the stricter version.
- Turn off app installs that make it easy to add another browser.
- Test from a second browser before you stop.
Android
This is for the people who still want one more layer after Family Link.
Use Private DNS
- Open Settings → Network & internet.
- Tap Private DNS.
- Choose Private DNS provider hostname.
- Enter a family-safe hostname from your DNS provider.
- Tap Save.
- Open Chrome and test a blocked site.
- Test any other browser you left on the phone.
- If one browser still works, remove it.
Clean up app bypasses
- Keep Family Link in place from Guardrails.
- Remove browsers you do not need.
- Keep SafeSearch on.
- Keep Restricted Mode on in YouTube.
- Set Google Play approval so new browsers need permission.
- Keep the parent account password off the device.
Windows
This is where the details matter. Put daily use on a standard user. Put the admin password somewhere else. Then block the hosts file and the obvious escapes.
Create separate accounts
- Open Settings → Accounts → Family & other users.
- Under Other users, click Add account.
- Choose I don’t have this person’s sign-in information.
- Choose Add a user without a Microsoft account.
- Create the daily account first.
- Click that account and choose Change account type.
- Leave it as Standard User.
- Create a second account for admin recovery.
- Make that one Administrator.
- Give the admin password to a trusted person.
- Use the standard account for everything day to day.
If the same person owns both accounts, it is not a lockout. It is just a delay.
Add DNS and hosts blocking
- Sign in to the standard account.
- Open Settings → Network & Internet.
- Set a family-safe DNS resolver if your adapter settings allow it.
- Open Notepad as Administrator.
- Open
C:\Windows\System32\drivers\etc\hosts. - Add blocked domains one per line, mapped to
127.0.0.1. - Save the file.
- Open Command Prompt and run
ipconfig /flushdns. - Test the block in Edge.
- Test the block in any other browser still installed.
Lock the hosts file down
- Sign into the admin account.
- Right-click the hosts file and open Properties.
- Go to Security → Advanced.
- Select the standard account entry.
- Remove write access.
- Leave write access only for the admin account.
- Apply the changes.
- Sign back into the standard account.
- Confirm the file is readable but not editable.
- Keep the admin password with the trusted person.
This is the part that makes the setup stick. If the standard user can edit hosts, the lock is weak.
Reduce browser and policy bypasses
- Keep Microsoft Family Safety active if you are using it.
- Use Edge for the managed account if you depend on Family Safety filtering.
- Remove or block browsers you do not need.
- Block portable browser installs if you can.
- Use AppLocker or Group Policy if your edition supports it.
- Do one test after each change.
Linux
Linux gives you more control, which means more places to harden. Do not stop at one block.
Use host and DNS blocks
- Open a terminal.
- Run
sudo nano /etc/hosts. - Add blocked domains, one per line, mapped to
127.0.0.1. - Save with Ctrl+O, press Enter, then exit with Ctrl+X.
- Set a family-safe DNS server at the system level.
- Keep one browser for daily use.
- Test the site in your browser and again after a reboot.
Harden the file and account path
- Use a standard user for daily work.
- Keep root or sudo access separate.
- Change the hosts file owner to
root:rootif needed. - Make the daily user read-only on that file.
- If your distro supports it, make the hosts file immutable after you finish.
- Use
ufw,firewalld, oriptablesto block DNS to anything except your chosen resolver. - Remove extra browsers and browser profiles you do not need.
For strong lockout, the machine and the network should both block the same thing.
Use allowlists when you need the hardest setup
- List the sites you actually need.
- Block everything else at the router, proxy, or firewall.
- Keep the allowlist small.
- Have the trusted person hold the override credentials.
- Review the list before you add anything new.
Router / gateway
This is the strongest place to enforce the rule across the whole home network.
Set family-safe DNS on the router
- Open a browser on a device connected to the router.
- Type the router address into the address bar. Common ones are
192.168.0.1and192.168.1.1. - Log into the router admin page.
- If you do not know the login, stop and get it from the trusted person or the ISP paperwork.
- Find the WAN, Internet, DNS, or Advanced section.
- Set the primary DNS to a family-safe resolver or your own filter.
- Set the secondary DNS too.
- Save the settings.
- Reboot the router if it asks.
- Test a blocked site from a device on the Wi-Fi network.
Close bypass paths
- Change the router admin password if you have not already.
- Give that password to the trusted person.
- Disable guest-network tricks if the router offers them.
- Block outbound DNS to anything except the chosen resolver if the router supports it.
- Turn off DNS-over-HTTPS override options if the router exposes them.
- Test from a guest network too.
- If the router has device allowlists, use them only if you really need the hardest setup.
When to stop here
Stop when bypassing is annoying enough that you do not casually do it. If you still can, move to Lockout.